Configuring BFD Parameters on the Ingress Node of the Tunnel

Procedure

1. Run system-view

   The system view is displayed.

2. Run bfd cfg-name bind mpls-te interface tunnel interface-number te-lsp [ backup ]

   BFD is configured to detect the primary or backup CR-LSP bound to a specified tunnel.

   The parameter backup means that backup CR-LSPs are to be checked.

3. Run discriminator local discr-value

   The local discriminator is set.

4. Run discriminator remote discr-value

   The remote discriminator is set.

5. (Optional) Run min-tx-interval interval

   The local interval at which BFD packets are sent is set.

6. (Optional) Run min-rx-interval interval

   The local interval at which BFD packets are received is set.

7. (Optional) Run detect-multiplier multiplier

   The local detection multiplier is adjusted.

   By default, the local detection multiplier is 3.

   Actual local sending interval = MAX { Configured local sending interval, Configured remote receiving interval }

   Actual local receiving interval = MAX { Configured remote sending interval, Configured local receiving interval }

   Actual local detection interval = Actual local receiving interval x Configured remote detection multiplier

   For example:

   • The local sending and receiving intervals are set to 200 ms and 300 ms respectively and the detection multiplier is set to 4.

   • The remote sending and receiving intervals are set to 100 ms and 600 ms respectively and the detection multiplier is set to 5.

   Then,

   • Actual local sending interval = MAX {200 ms, 600 ms} = 600 ms; Actual local receiving interval = MAX {100 ms, 300 ms} = 300 ms; Actual local detection interval is 300 ms x 5 = 1500 ms.

   • Actual remote sending interval = MAX {100 ms, 300 ms} = 300 ms; Actual remote receiving interval = MAX {200 ms, 600 ms} = 600 ms; Actual remote detection interval is 600 ms x 4 = 2400 ms.

8. Run process-pst

   The system is enabled to modify the port status table (PST) when the BFD session status changes.

   When the BFD status changes, BFD notifies the application of the change, triggering a fast switchover between the primary and backup CR-LSPs.

9. Run notify neighbor-down

   A BFD session is configured to notify the upper layer protocol when the BFD session detects a neighbor Down event.

   In most cases, when you use a BFD session to detect link faults, the BFD session notifies the upper layer protocol of a link fault in the following scenarios:

   • When the BFD detection time expires, the BFD session notifies the upper layer protocol. BFD sessions must be configured on both ends. If the BFD session on the local end does not receive any BFD packets from the remote end within the detection time, the BFD session on the local end concludes that the link fails and notifies the upper layer protocol of the link fault.
   • When a BFD session detects a neighbor Down event, the BFD session notifies the upper layer protocol. If the BFD session on the local end detects a neighbor Down event within the detection time, the BFD session on the local end directly notifies the upper layer protocol of the neighbor Down event.

   When you use a BFD session to detect faults on an LSP, you need only be concerned about whether a fault occurs on the link from the local end to remote end. In this situation, run the notify neighbor-down command to configure the BFD session to notify the upper layer protocol only when the BFD session detects a neighbor Down event. This configuration prevents the BFD session from notifying the upper layer protocol when the BFD detection time expires and ensures that services are not interrupted.

10. Run commit

    The current configuration is committed.