The OSPF Neighbor Relationship Cannot Reach the Full State

Created Sep 20, 2017 09:46:09Latest reply Sep 20, 2017 17:04:20 1426 1 0 0

1.Common Causes

This fault is commonly caused by one of the following:

l   The link is faulty and the OSPF packets are dropped.

l   The configuration of the dr-priority on the interfaces is incorrect.

l   The OSPF MTUs of the local device and its neighbor are different.

2.Troubleshooting Flowchart

Figure 1-1 shows the troubleshooting flowchart.

Figure 1-1 Troubleshoot flowchart for the fault that the OSPF neighbor relationship cannot reach the Full state

20170920094604523001.png

 

 

3.Troubleshooting Procedure

Context

note

Saving the results of each troubleshooting step is recommended. If you are unable to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.

Procedure

                      Step 1    Troubleshoot the fault based on the status of the OSPF neighbor relationship.

l   The status of the OSPF neighbor relationship cannot be displayed.

If the status of the OSPF neighbor relationship cannot be displayed, see The OSPF Neighbor Relationship Is Down to rectify the fault.

l   The neighbor relationship is always in the Down state.

Run the display interface [ interface-type [ interface-number ] ] command to check the physical status of the interface. If the physical status of the interface is Down, troubleshoot the interface fault.

If the physical status of the interface is Up, run the display ospf interface command to check whether the OSPF status of the interface is Up (such as DR, BDR, DR Other, or P2P).

<Huawei> display  ospf interface
             OSPF Process 1 with Router ID 1.1.1.1
                     Interfaces
 Area: 0.0.0.0          
 IP Address      Type         State    Cost    Pri   DR              BDR
 192.168.1.1     Broadcast    DR       1       1     192.168.1.1     0.0.0.0

        If the OSPF status of the interface is Up, go to Step 2.

        If the OSPF status of the interface is Down, run the display ospf cumulative command to check whether the number of interfaces with OSPF enabled in the OSPF process exceeds the upper threshold. If so, reduce the number of interfaces with OSPF enabled.

<Huawei> display ospf cumulative
          OSPF Process 1 with Router ID 1.1.1.1
                  Cumulations
  IO Statistics
             Type        Input     Output
            Hello            0         86
   DB Description            0          0
   Link-State Req            0          0
Link-State Update            0          0
   Link-State Ack            0          0
  SendPacket Peak-Control: (Disabled)
  ASE: (Disabled)
  LSAs originated by this router
  Router: 1
  Network: 0
  Sum-Net: 0
  Sum-Asbr: 0
  External: 0
  NSSA: 0
  Opq-Link: 0
  Opq-Area: 0
  Opq-As: 0
  LSAs Originated: 1  LSAs Received: 0
  Routing Table:
    Intra Area: 1  Inter Area: 0  ASE: 0
  Up Interface Cumulate: 1

l   The neighbor relationship is always in the Init state.

If the status of the neighbor relationship is always displayed as Init, the remote device cannot receive Hello packets from the local device. In this case, check whether the link or the remote device is faulty.

l   The neighbor relationship is always in the 2-way state.

If the status of the neighbor relationship is always displayed as 2-way, run the display ospf interface command to check whether the DR priorities of the interfaces with OSPF enabled are 0.

<Huawei> display ospf interface
          OSPF Process 1 with Router ID 1.1.1.1
                  Interfaces
 
   Area: 0.0.0.0          
   IP Address      Type         State    Cost  Pri   DR              BDR
   1.1.1.1         Broadcast    DROther  1     0     1.1.1.2        . 0.0.0.0

        If the DR priorities of the interfaces with OSPF enabled are 0 and the state is DROther, both the local device and its neighbor are not the DR or BDR and they do not need to exchange LSAs. In this case, no action is required.

        If the DR priorities of the interfaces enabled with OSPF are not 0, go to Step 2.

l   The neighbor relationship is always in the Exstart state.

If the status of the neighbor relationship is always displayed as Exstart, it indicates that the devices are exchanging DD packets but fail to synchronize LSDBs, which occurs in the following cases:

        Packets that are too long cannot be normally sent and received.

Run the ping -s 1500 neighbor-address command to check the sending and receiving of packets that are too long. If the two devices fail to ping each other, solve the link problem first.

        The OSPF MTUs of the two devices are different.

If the ospf mtu-enable command is run on the OSPF interfaces, check whether the OSPF MTUs on the two interfaces are the same. If they are not the same, change the MTUs of the interfaces to ensure that the MTUs of the interfaces are the same.

If the fault persists, go to Step 2.

l   The neighbor relationship is always in the Exchange state.

If the status of the neighbor relationship is always displayed as Exchange, the two devices are exchanging DD packets. In this case, follow the troubleshooting procedure provided for when the neighbor relationship is in the Init state. If the fault persists, go to Step 2.

l   The neighbor relationship is always in the Loading state.

 

Notice

Restarting OSPF causes the re-establishment of all neighbor relationships in the OSPF process and the temporary interruption of services.

If the neighbor relationship is always in the Loading state, run the reset ospf process-id process command to restart the OSPF process.

If the fault persists, go to Step 2.

                      Step 2    Step 2            Collect the following information and contact contact technical support personnel.

l   Results of the preceding troubleshooting procedure

l   Configuration files, log files, and alarm files of the devices

----End

4.Relevant Alarms and Logs

Relevant Alarms

OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange

OSPF_1.3.6.1.2.1.14.16.2.8 ospfIfRxBadPacket

OSPF_1.3.6.1.2.1.14.16.2.16 ospfIfStateChange

Relevant Logs

None.

 

 


  • x
  • convention:

gululu  Admin   Created Sep 20, 2017 17:04:20 Helpful(0) Helpful(0)

thanks
  • x
  • convention:

Come on!

Responses

Reply
You need to log in to reply to the post Login | Register

Notice:To ensure the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but not limited to politically sensitive content, content concerning pornography, gambling, drug abuse and trafficking, content that may disclose or infringe upon others' intellectual properties, including commercial secrets, trade marks, copyrights, and patents, and personal privacy. Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see“ Privacy Policy.”
If the attachment button is not available, update the Adobe Flash Player to the latest version!
Fast reply Scroll to top