No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
The OSPF Neighbor Relationship Cannot Reach the Full State

The OSPF Neighbor Relationship Cannot Reach the Full State

Common Causes

This fault is commonly caused by one of the following:

  • The link is faulty and the OSPF packets are dropped.
  • The configuration of the dr-priority on the interfaces is incorrect.
  • The OSPF MTUs of the local device and its neighbor are different.

Troubleshooting Flowchart

Figure 19-4 shows the troubleshooting flowchart.

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

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

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

    • 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.

    • 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
        
    • 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.

    • 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.
    • 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.

    • 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.

    • The neighbor relationship is always in the Loading state.

      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.

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

    • Results of the preceding troubleshooting procedure
    • Configuration files, log files, and alarm files of the devices

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 448893

Downloads: 4305

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next