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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
OSPF Neighbor Relationships Cannot Be Established

OSPF Neighbor Relationships Cannot Be Established

Common Causes

Fault Symptom

This fault is commonly caused by the following:

  • The OSPF neighbor status cannot be displayed.
  • The OSPF neighbor status remains Init.
  • The OSPF neighbor status remains 2-way.
  • The OSPF neighbor status remains Exstart.
  • The OSPF neighbor status remains Exchange.
  • The OSPF neighbor status remains Loading.

Common Causes

This fault is commonly caused by the following:

  • The link fails.
  • Configurations are incorrect.

Troubleshooting Flowchart

If OSPF neighbor relationships cannot be established, rectify the fault according to Figure 6-5.

Figure 6-5 Troubleshooting flowchart for a failure to establish an OSPF relationship

Troubleshooting Procedure

Procedure

  1. Troubleshoot the fault according to the OSPF neighbor status.

    Run the display ospf peer command in the user view and rectify the fault according to the State field.

    <HUAWEI> display ospf peer
    
             OSPF Process 1 with Router ID 192.168.2.200                                                                                         
     Area 0.0.0.0 interface 10.0.0.2 (Vlanif4000)'s neighbors                                                                           
      Router ID: 10.1.1.3            Address : 10.0.0.1                                                                                  
          : Full        Mode    : Nbr is Slave       Priority: 1                                                            
      DR       : 10.0.0.2           BDR     : 10.0.0.1           MTU     : 0                                                            
      Dead timer due (in seconds) : 40                                                                                                  
      Retrans timer interval      : 5                                                                                                   
      Neighbor up time            : 02h26m53s                                                                                           
      Authentication Sequence     : 0
    • The OSPF neighbor status cannot be displayed.

      Check whether the configurations in the OSPF view of devices on both ends are the same. If the configurations such as the OSPF area ID or area type (NSSA, stub area, or common area) are different, the two devices cannot establish an OSPF neighbor relationship. Run the display ospf interface command in the user view to check whether the specified OSPF process is enabled on the interface according to the Interface field.

      <HUAWEI> display ospf 1 interface
      
              OSPF Process 1 with Router ID 192.168.2.200                                                                                         
                                                                                                                                          
       Area: 0.0.0.0          MPLS TE not enabled                                                                                         
                                                                                                                                          
             IP Address      Type         State    Cost    Pri                                                            
       Eth-Trunk255          192.168.0.101   Broadcast    Down     65535   1                                                              
       Loop0                 192.168.2.200   P2P          P-2-P    0       1                                                              
      • If the OSPF process is not enabled on the related interface, run the network network-address wildcard-mask command in the OSPF process view to specify the OSPF interface and area to which the interface belongs (an OSPF process is used as an example).

        [~HUAWEI] ospf 1
        [~HUAWEI-ospf-1] area 0
        [~HUAWEI-ospf-1-area-0.0.0.0] network 192.168.2.0 0.0.0.255
        [*HUAWEI-ospf-1-area-0.0.0.0] commit
      • If the OSPF process has been enabled on the related interface, run the display ospf error command in the user view to check whether OSPF authentication information on the two devices is the same according to the Bad authentication type and Bad authentication key fields.

        <HUAWEI> display ospf 1 error
        
                  OSPF Process 1 with Router ID 192.168.2.200                                                                               
                          OSPF error statistics                                                                                             
                                                                                                                                            
        General packet errors:                                                                                                              
         6360        : IP: received my own packet     25645       : Bad packet                                                              
         0           : Bad version                    0           : Bad checksum                                                            
         0           : Bad area id                    0           : Drop on unnumbered interface                                            
         0           : Bad virtual link               0           :                                                  
         0           :         0           : Packet too small                                                        
         0           : Packet size > ip length        0           : Transmit error                                                          
         4           : Interface down                 0           : Unknown neighbor
        • If the value of the Bad authentication type or Bad authentication key field keeps increasing, OSPF authentication information on the two devices is different. To configure the same authentication information for the two devices, run the ospf authentication-mode command in the OSPF process view.

          [~HUAWEI] ospf 1
          [~HUAWEI-ospf-1] area 0
          [~HUAWEI-ospf-1-area-0.0.0.0] authentication-mode simple cipher 123
          [*HUAWEI-ospf-1-area-0.0.0.0] commit
        • If OSPF authentication information on the two devices is the same and the display ospf peer command sometimes does not display the OSPF neighbor status, OSPF neighbor flapping may occur. Rectify the fault according to OSPF Neighbor Flapping Occurs.

    • The OSPF neighbor status remains Init.

      Two possible causes exist:

      • The peer device cannot receive Hello packets from the local device. Rectify link faults and device faults.

        1. Check whether the local device sends Hello packets.

          Run the debugging ospf packet hello interface interface-type interface-number command in the user view to enable OSPF debugging to check whether the OSPF module sends Hello packets.

          <HUAWEI> debugging ospf packet hello interface Vlanif200
          <HUAWEI> terminal monitor
          Info: Current terminal monitor is on.
          <HUAWEI> terminal debugging
          Info: Current terminal debugging is on.
          <HUAWEI>
          Jul 15 2015 14:42:37.221 128_14.60 %%01OSPF/6/OSPF_DEBUG(d):CID=0x808204d5;                                                         
          FileID: 0x13 Line: 1012 Level: 0x5                                                                                                  
            OSPFv2 1  Packet, Interface: Vlanif4000                                                                                       
            ...

          If SEND information is displayed, the OSPF module has sent Hello packets. If SEND information is not displayed, the OSPF module does not send Hello packets. Go to step 2.

        2. If the OSPF module has sent Hello packets, enable LDM debugging to check whether the LDM module sends packets.
          [~HUAWEI-diagnose] debugging ldm packet send ipv4 protocol ospf number 1
          [~HUAWEI-diagnose]                                                                                                          
          ...
          3 2015 09:47:59.288 PE2 %%01LDM/6/LDM_PKT(d):CID=0x8078275b; ret=0   
          ...

          If LDM send pkt to FE is displayed, the LDM module has sent packets. If it is not displayed, go to step 2.

        3. If the local device sends Hello packets, log in the remote device, run the debugging ospf packet hello interface interface-type interface-number command in the user view to enable Hello debugging to check whether the OSPF module by the remote device sends Hello packets.
          <HUAWEI> debugging ospf packet hello interface Vlanif200
          <HUAWEI> terminal monitor
          Info: Current terminal monitor is on.
          <HUAWEI> terminal debugging
          Info: Current terminal debugging is on.
          <HUAWEI>
          15 2015 14:41:01.203 128_14.60 %%01OSPF/6/OSPF_DEBUG(d):CID=0x808204d5;                                                         
          FileID: 0x1d Line: 1085 Level: 0x5                                                                                                  
            OSPFv2 1  Packet, Interface: Vlanif4000                                                                                       
          ...

          If RECV is displayed, the OSPF module has received packets. If the Hello packets were not sent out, check whether congestion occurs on the intermediate link. If the fault persists, go to step 2.

      • The interface type is configured incorrectly. Run the ospf network-type command on the OSPF interface to reconfigure the interface type.
    • The OSPF neighbor status remains 2-way.

      If the neighbor status remains 2-way, run the display ospf interface command to check whether Pri(dr-priority) configured for the OSPF-enabled interface is 0.

      <HUAWEI> display ospf interface
                OSPF Process 1 with Router ID 192.168.2.200                       
      
      Area: 0.0.0.0          MPLS TE not enabled                                                                                         
                                                                                                                                          
       Interface             IP Address      Type         State    Cost                                       
       Eth-Trunk255          192.168.0.101   Broadcast    Down     65535   1                                                              
       Loop0                 192.168.2.200   P2P          P-2-P    0       1      
      • If dr-priority of the OSPF-enabled interface is 0, the neighbor status 2-way is normal.
      • If dr-priority of the OSPF-enabled interface is not 0, run the display ospf peer command in the user view to check whether both the peer and local devices are DROthers.
        <HUAWEI> display ospf peer
        
                  OSPF Process 1 with Router ID 192.168.2.200                                                                                         
         Area 0.0.0.0 interface 10.0.0.2 (Vlanif4000)'s neighbors                                                                           
          Router ID: 10.1.1.3            Address : 10.0.0.1                                                                                  
          State    : Full               Mode    : Nbr is Slave       Priority: 1                                                            
                 : 10.0.0.2               : 10.0.0.1           MTU     : 0               
          Dead timer due (in seconds) : 30                                                                                                  
          Retrans timer interval      : 5                                                                                                   
          Neighbor up time            : 02h39m32s                                                                                           
          Authentication Sequence     : 0

        If both the local interface address and neighbor address (specified by the Address field) are different from the DR field or BDR field value, both the peer and local devices are DROthers. In this situation, it is normal that the neighbor status remains 2-way.

    • The OSPF neighbor status remains Exstart.

      If the neighbor status remains Exstart, the two devices remain in DD negotiation and cannot synchronize their DDs. Two possible causes exist:

      • Oversized packets cannot be received and sent.

        Run the ping -s 1500 neighbor-address command to check oversized packet transmission. If the ping operation fails, rectify the link fault.

      • The two devices have different OSPF MTUs configured.

        Huawei devices check the MTU of DD packets only when the ospf mtu-enable command is configured on OSPF interfaces. Non-Huawei devices check the MTU of DD packets by default.

        Check whether the local OSPF interface has the ospf mtu-enable command configured and whether the interfaces on both ends use the same OSPF MTU. If the two interfaces use different MTUs, ensure that the two interfaces use the same MTU.

      If the fault persists, go to step 2.

    • The OSPF neighbor status remains Exchange.

      If the neighbor status remains Exchange, the two devices are exchanging DD packets. Rectify the fault according to the procedure performed when the neighbor status remains Exstart. If the fault persists, go to step 2.

    • The OSPF neighbor status remains Loading.

      If the peer device has a large number of LSAs, the neighbor status may remain Loading for a long time. Wait for a period of time. If the neighbor status remains Loading, go to step 2.

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

    • Results of the preceding troubleshooting procedure
    • Configuration file, logs, and alarms of the device

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 612183

Downloads: 2956

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next