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).
BFD Session Cannot Go Up

BFD Session Cannot Go Up

Common Causes

This fault is commonly caused by one of the following:
  • The discriminators of the two devices are inconsistent.

  • The link detected by the BFD session fails. As a result, BFD packets cannot be exchanged between the two ends of the BFD session.

  • The BFD session status flaps.

Troubleshooting Flowchart

Figure 23-3 Troubleshooting flowchart for the fault that a BFD session cannot go Up

Troubleshooting Procedure

Context

NOTE:

Save the results of each troubleshooting step. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.

Procedure

  1. Run the display current-configuration command to check that the configuration of the BFD session is committed.

    • If the commit command is displayed, the configuration of the BFD session has been committed. Then, go to Step 2.

    • If the commit command is not displayed, the configuration of the BFD session has not been committed. In this case, run the commit command to commit the configurations. After doing so, run the display bfd session all command to check the State field.
      • If the State field is Up, the BFD session is successfully established.

      • If the State field is not Up, go to Step 2.

  2. Run the display current-configuration command to check whether the discriminators of the two devices are consistent.

    • If they are inconsistent, run the undo bfd command to delete the existing bfd session, and then run the bfd bind peer-ip command to create a new bfd session. At last run the discriminator { local discr-value | remote discr-value } command to configure the local and remote discriminators. Ensure that the local discriminator on the local end is the same as the remote discriminator on the remote end and the remote discriminator on the local end is the same as the local discriminator on the remote end. Then, go to Step 3.

    • If they are consistent, go to Step 4.

  3. Run the display bfd session all command to check the State field.

    • If the State field is Up, the BFD session is successfully established.

    • If the State field is not Up, go to Step 4.

  4. Run the display bfd statistics session all command several times to view statistics about the BFD packets of the BFD session.

    • If the value of the Received Packets field does not increase, go to Step 5.

    • If the value of the Send Packets field does not increase, go to Step 6.

    • If the values of Received Packets and Send Packets fields increase, go to Step 9.

    • If none of the values of the Received Packets, Send Packets, Received Bad Packets, and Send Bad Packets fields increase, go to Step 7.

    • If the value of the Down Count field increases, the BFD session flaps. Then, go to Step 7.

  5. Run the display bfd statistics session all command several times to check the Received Bad Packets field.

    • If the value of this field increases, the BFD packets have been received and discarded. Then, go to Step 9.

    • If the value of this field does not increase, the BFD packets have not been received. Then, go to Step 7.

  6. Run the display bfd statistics session all command several times to check the Send Bad Packets field.

    • If the value of this field increases, the BFD packets sent by the BFD session have been discarded. Then, go to Step 9.

    • If the value of this field does not increase, the BFD packets failed to be sent. Then, go to Step 7.

  7. Run the display bfd statistics session all command several times. If the BFD session still does not go Up, run the ping command on one end to ping the other end of the BFD session.

    • If the ping fails, it indicates that the link fails. See the section The Ping Operation Fails to rectify the fault on the link.

    • If the ping is successful, it indicates that the link is reachable. Then, go to Step 8.

  8. Run the display current-configuration command to view the min-tx-interval and min-rx-interval fields to check that the BFD detection period is longer than the delay on the link.

    • If the BFD detection period is shorter than the delay on the link, run the detect-multiplier, min-rx-interval, and min-tx-interval commands to adjust the values to make it longer than the delay on the link.

    • If the BFD detection time is longer than the delay time on the link, go to Step 9.

  9. If the fault persists, collect the following information and contact technical support personnel.

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

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000079719

Views: 495105

Downloads: 4530

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