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.


Configuration Guide - Reliability

S1720, S2700, S5700, and S6720 V200R010C00

This document describes the configuration of BFD, DLDP, VRRP, SmartLink, CFM, EFM, Y.1731 and MAC swap loopback to ensure reliability on the device.
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 Association Between the BFD Session and the Interface Status

Configuring Association Between the BFD Session and the Interface Status

Pre-configuration Tasks

Before associating the BFD session with interface status, connect interfaces properly.

Configuration Process

Figure 3-19  Association between the BFD session and the interface status


If a transmission device exists on a direct link, BFD detects a link fault faster than a link protocol on an interface. The link protocol status of a trunk or VLANIF interface depends on the link protocol status of member interfaces.

To help BFD rapidly report the detection result to the application, a BFD status attribute is added to the interface management module of each interface. This attribute indicates the status of the BFD session that is bound to the interface. The system obtains the interface status based on the link status, protocol status, and BFD status on the interface, and then reports the interface status to the application.

This function is only used on the single-hop BFD session that is bound to an outbound interface and uses the default multicast address.


  1. Run:


    The system view is displayed.

  2. Run:


    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:


    Return to the system view.

  5. Run:

    bfd session-name bind peer-ip default-ip interface interface-type interface-number [ source-ip ip-address ]

    A BFD session is created.

    By default, no BFD binding for monitoring physical status of a link is configured.


    When creating a multicast BFD session, ring protocols cannot be configured on the interface bound to the multicast BFD session. Otherwise, MAC address flapping may occur.

  6. Run:

    discriminator local discr-value

    The local discriminator of the BFD session is configured.

  7. Run:

    discriminator remote discr-value

    The remote discriminator of the BFD session is configured.

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

    process-interface-status [ reboot-no-impact ]

    The BFD session status is associated with the interface status.

    By default, the BFD session status is not associated with the interface status. That is, the change of the BFD session status does not affect the interface status.

  9. Run:


    The configuration is committed.

    • The BFD session does not report the BFD status to the bound interface immediately after the commit command is executed because the BFD session may not be set up or not Up. This prevents the BFD session from reporting an incorrect state to the interface. When the BFD status changes, the BFD session reports the BFD status to the interface to trigger the interface status change.

    • If the process-interface-status command has been saved in the configuration file, the initial interface status must be Down after the device restarts; therefore, the BFD session reports a Down state to the interface.

Updated: 2019-08-21

Document ID: EDOC1000141941

Views: 89839

Downloads: 510

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