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 Single-Hop BFD

Configuring Single-Hop BFD

Pre-configuration Tasks

Single-hop BFD fast detects faults on the directly connected link.

Before configuring single-hop BFD, complete the following tasks:

  • Configure link layer protocol parameters for interfaces to ensure that the link layer protocol status on the interfaces is Up.

  • Configure an IP address for the Layer 3 interface.

Configuration Process

Figure 6-15  Single-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 default-ip-address ip-address

    The default multicast IP address for BFD is configured.

    By default, BFD uses the multicast IP address

    If multiple BFD sessions exist on a path, for example, Layer 3 interfaces are connected through Layer 2 switching devices that support BFD, configure different default multicast IP addresses for the devices where different BFD sessions are established. In this manner, BFD packets can be correctly forwarded.

  4. Run quit

    Return to the system view.

  5. Run the following commands as required.

    • To use BFD to detect faults in an IPv4 link, run the following commands as required to configure a BFD session:

      • On a Layer 3 interface that has an IP address configured, run bfd session-name bind peer-ip ip-address [ vpn-instance vpn-name ] interface interface-type interface-number [ source-ip ip-address ]

        A BFD binding is configured.

        By default, BFD binding is not created.

        • When creating a single-hop BFD session for the first time, bind the single-hop BFD session to the peer IP address and the local address. To modify a configured BFD session, delete it and recreate a new one.

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

        • BFD cannot detect route switching. If the bound peer IP address change causes route switching, BFD does not perform re-negotiation unless forwarding fails on the original link.

      • On a Layer 2 interface, Layer 3 interface, run bfd session-name bind peer-ip default-ip interface interface-type interface-number [ source-ip ip-address ]

        Multicast BFD is created.

        By default, BFD binding is not created.


        When creating a multicast BFD session on a Layer 3 interface, configure an IP address for the interface so that the protocol layer becomes Up. Otherwise, the BFD session cannot become Up.

        If the protocol status of the Layer 3 interface to which a multicast BFD session is bound is Down, you can run the unlimited-negotiate command to enable unlimited negotiation for the multicast BFD session so that BFD can be performed.

    • To use BFD to detect faults in an IPv6 link, run the following command to create a BFD6 session:

      bfd bfd-name bind peer-ipv6 peer-ipv6 [ vpn-instance vpn-instance-name ] interface interface-type interface-number [ source-ipv6 source-ipv6 ]

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

      • If a single-hop BFD6 session is to be created for the first time, the peer IPv6 address and local outbound interface need to be bound to the session. The bindings cannot be modified after the BFD6 session is successfully created.
      • When creating a BFD6 session, the system checks only the format, not the correctness, of a peer IPv6 address. An incorrect peer or source IPv6 address leads to a failure in creating a BFD6 session.

  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.

    • If a BFD session is bound to the default multicast address, the local discriminator and the remote discriminator must be different.

  8. Run commit

    The configuration is committed.

Updated: 2019-08-12

Document ID: EDOC1100034076

Views: 60918

Downloads: 109

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