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


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


CLI-based Configuration Guide - Reliability

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides guidance for configuring reliability services, including interface backup, BFD, VRRP, and EFM.

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).
Configuring Multi-Hop BFD

Configuring Multi-Hop BFD

Pre-configuration Tasks

Multi-hop BFD fast detects faults on the indirectly connected link.

Before configuring multi-hop BFD, complete the following task:

  • Configure a routing protocol to ensure reachability at the network layer.

Configuration Process

Figure 6-16  Multi-hop BFD configuration process


  1. Run system-view

    The system view is displayed.

  2. Run bfd

    BFD is enabled globally and the BFD view is displayed.

    By default, BFD is disabled globally.

  3. (Optional) Run multi-hop destination-port{ 3784 | 4784 }

    The destination port number for a multi-hop BFD session is configured.

    By default, destination port 3784 is used in multi-hop BFD control packets.

  4. Run quit

    Return to the system view.

  5. Select the step based on the type of the link detected by BFD:

    • For an IPv4 link:

      Run bfd session-name bind peer-ip ip-address [ vpn-instance vpn-name ] [ source-ip ip-address ]

      A BFD session is created and the peer IP address is specified.

      By default, BFD binding is not created.

      • When creating a multi-hop BFD session, you must bind the BFD session to the peer IP address.

      • When the BFD configuration items are created, the system checks only the format of the IP address. The BFD session cannot be established if an incorrect peer IP address or source IP address is bound.

      • When BFD and URPF are used together, UPRF checks the source IP address of the received BFD packets. You must bind the correct source IP address to the BFD session to prevent BFD packets from being discarded incorrectly.

      • When a multi-hop BFD session is configured and the peer IP address is the same as the 32-bit destination IP address of an LDP or static LSP, the BFD session is associated with the LSP. That is, if the BFD session detects a fault, an LSP switchover is performed.

    • For an IPv6 link:

      Run the bfd session-name bind peer-ipv6 peer-ipv6 [ vpn-instance vpn-instance-name ] [ source-ipv6 ipv6-address ] command to configure a BFD for IPv6 session.

      By default, no BFD IPv6 session to monitor an IPv6 link is created.

      • When setting up a BFD for IPv6 session for the first time, you need to bind the peer IPv6 address to the session. The binding cannot be modified once the BFD for IPv6 session is set up.
      • If the specified peer IPv6 address is a link-local address, the outbound interface should also be specified, that is, only the single-hop BFD for IPv6 session can be set up; otherwise, an error prompt is displayed.
      • When configuring the BFD for IPv6 session, the system checks only the validity of the format of the IPv6 address rather than the correctness of the IPv6 address. The BFD for IPv6 session cannot be set up if incorrect peer IPv6 address or source IPv6 address is bound.

  6. Run discriminator local discr-value

    The local discriminator is set.

  7. Run discriminator remote discr-value

    The remote discriminator is set.


    The local discriminator of the local system must be the same as the remote discriminator of the remote system; the remote discriminator of the local system must be the same as the local discriminator of the remote system. Otherwise, BFD sessions cannot be established. After the local discriminator and the remote discriminator are configured, you cannot modify them.

  8. Run commit

    The configuration is committed.

Updated: 2019-08-12

Document ID: EDOC1100034076

Views: 65062

Downloads: 114

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next