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.


Fat AP and Cloud AP V200R008C00 CLI-based Configuration Guide

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


This section describes the implementation of BFD.

BFD Implementation

Two network devices establish a BFD session to detect the forwarding path between them and serve upper-layer applications. BFD does not provide neighbor discovery. Instead, BFD obtains neighbor information from the upper-layer application BFD serves to establish a BFD session. After the BFD session is set up, the local device periodically sends BFD packets. If the local device does not receive a response from the peer system within the detection time, it considers the forwarding path faulty. BFD then notifies the upper-layer application for processing. The following uses association between OSPF and BFD as an example to describe the BFD session setup process.

Figure 24-1  BFD session setup

As shown in Figure 24-1, OSPF and BFD are configured on SwitchA and SwitchB. The BFD session setup process is as follows:

  1. OSPF uses the Hello mechanism to discover neighbors and establishes a neighbor relationship.

  2. OSPF notifies BFD of neighbor information including source and destination addresses.

  3. BFD sets up a BFD session based on received neighbor information.

  4. After the BFD session is set up, BFD starts to detect link faults and rapidly responds to link faults.

Figure 24-2  BFD detecting link faults

As shown in Figure 24-2:

  1. The detected link is faulty.

  2. BFD rapidly detects the link fault and the BFD session becomes Down.

  3. BFD notifies the local OSPF process that the neighbor is unreachable.

  4. The local OSPF process ends the OSPF neighbor relationship.

BFD Session Establishment Modes

BFD sessions can be set up statically and dynamically. Static and dynamic BFD sessions differ in that local and remote discriminators are configured in different modes. BFD uses local and remote discriminators in control packets to differentiate BFD sessions.

  • Statically establishing a BFD session

    BFD session parameters, including the local and remote discriminators, are specified using commands. Then a request for BFD session establishment is distributed manually.

  • Dynamically establishing a BFD session

    When a BFD session is set up dynamically, the system processes the local and remote discriminators as follows:

    • Dynamically allocated local discriminator

      When an application triggers dynamic setup of a BFD session, the system allocates a value as the local discriminator of the BFD session. Then the local system sends a BFD control packet with Remote Discriminator as 0 to the remote system to negotiate on the BFD session.

    • Self-learned remote discriminator

      When one end of a BFD session receives a BFD control packet with Remote Discriminator as 0, this end checks the BFD control packet. If the packet matches the local BFD session, this end learns the value of Local Discriminator in the received BFD control packet to obtain the remote discriminator.

BFD Detection Mechanism

Two systems set up a BFD session and periodically send BFD control packets along the path between them. If one system does not receive BFD control packets within a specified period, the system considers that a fault has occurred on the path.

BFD provides the Asynchronous mode. In asynchronous mode, two systems periodically send BFD control packets to each other. If one system receives no packets consecutively, the system considers the BFD session Down.

BFD Session Management

The BFD session has the following status: Down, Init, Up, and AdminDown. The State field of a BFD control packet shows the session status. The system changes the session status based on the local session status and the received session status of the peer. The BFD state machine implements a three-way handshake for BFD session setup or deletion to ensure that the two systems detect the status change. The following uses BFD session setup as an example to describe the state machine transition process.

Figure 24-3  BFD session setup
Updated: 2019-01-11

Document ID: EDOC1000176006

Views: 117486

Downloads: 309

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