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.


CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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 BFD Association

Configuring BFD Association

Association between BFD and other protocols improves protocol switching performance and reduces service traffic loss.

Applications Associated with BFD

Configuring Association Between the BFD Session and the Interface Status

Pre-configuration Tasks

Before associating the BFD session with interface status, complete the following task:

  • Connecting interfaces properly

Configuration Process
Figure 11-21 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, BFD binding is not created.

  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.

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

  8. Run:


    The BFD session status is associated with the bound 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.


    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-09

Document ID: EDOC1000041694

Views: 57911

Downloads: 3621

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