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).
Troubleshooting Procedure

Troubleshooting Procedure

After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the two-phase validation mode.

  • In immediate validation mode, the configuration takes effect immediately after you run a command and press Enter.
  • In two-phase validation mode, you must run the commit command after commands are configured to commit the configuration.

Save the results of each troubleshooting step, so you can provide related information to Huawei technical support if your troubleshooting fails.

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 for help on rectifying the fault.

    • 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 enabled with OSPF are 0.

      <HUAWEI> display ospf interface
                OSPF Process 1 with Router ID 10.1.1.1
                        Interfaces
      
       Area: 0.0.0.0          (MPLS TE not enabled)
       Interface          IP Address      Type         State     Cost    
       Vlanif50           192.168.5.1     Broadcast    DROther   1       
      • If the DR priorities of the interfaces enabled with OSPF are 0, the status of the neighbor relationship is normal.
      • If the DR priorities 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, the devices are exchanging DD packets but fail to synchronize LSDBs, which occurs in the following cases:

      • Excessively long packets cannot be normally sent and received.

        Run the ping -s 1500 neighbor-address command to check the sending and receiving of long packets. 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 not, change the MTUs to ensure they 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, perform troubleshooting as has been described 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 the neighbor relationships in the OSPF process and temporary service interruptions.

      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. Collect the following information and contact technical support personnel.

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

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 607239

Downloads: 2948

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next