The bfd bind peer-ip command creates a BFD session, specifies the peer IP address, and displays the BFD session view.
The undo bfd session-name command deletes a specified BFD session and cancels the peer IP address.
By default, BFD binding is not created.
bfd session-name bind peer-ip ip-address [ vpn-instance vpn-name ] [ interface interface-type interface-number ] [ source-ip ip-address ]
undo bfd session-name
Parameter |
Description |
Value |
|---|---|---|
session-name |
Specifies the name of a BFD session. |
The value is a string of 1 to 15 case-sensitive characters without spaces.
NOTE:
When double quotation marks are used around the string, spaces are allowed in the string. |
peer-ip ip-address |
Specifies the peer IP address bound to the BFD session. |
- |
vpn-instance vpn-name |
Specifies the name of a Virtual Private Network (VPN) instance that is bound to a BFD session. |
The value must be an existing VPN instance name. |
interface interface-type interface-number |
Specifies the type and number of the interface bound to the BFD session.
|
- |
source-ip ip-address |
Indicates the source IP address carried in BFD packets.
When BFD is used with the Unicast Reverse Path Forwarding (URPF) function, you must manually configure the source IP address in BFD packets because the URPF function checks the source IP address in received packets. NOTE:
For details about URPF, see URPF Configuration in the S2720, S5700, and S6700 V200R019C10 Configuration Guide - Security. |
- |
Usage Scenario
To fast detect and monitor links, create BFD sessions.
To create a BFD binding, pay attention to the following points:
If only the peer IP address is specified, BFD is configured to detect the multi-hop link.
If the peer IP address and local interface are specified, BFD is configured to detect the single-hop link, that is, a specific route with this interface as the outbound interface and with the peer IP address as the next-hop address.
If both the peer IP address and the VPN instance are specified, BFD is configured to detect the multi-hop link in the VPN instance.
The single-hop link in the VPN instance is detected if both the peer IP address, VPN instance, and local interface are specified.
Prerequisites
Global BFD has been enabled by using the bfd command in the system view.
Follow-up Procedure
Run the discriminator command to set the local and remote discriminators for the current BFD session.
Precautions
When creating a single-hop BFD session, bind the single-hop BFD session to the peer IP address and the local address. You only need to bind a multi-hop BFD session to the peer IP address.
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 a multi-hop BFD session is configured, the value of peer-ip or source-ip cannot be the IP address of a GRE tunnel interface.
When a multi-hop BFD session is configured and the peer IP address is the same as the 32-bit destination IP address of an LDP or static LSP, the BFD session is associated with the LSP. That is, if the BFD session detects a fault, an LSP switchover is performed.
# Create a BFD session named atob to detect the single-hop link from VLANIF100 to the peer IP address at 10.10.10.2.
<HUAWEI> system-view [HUAWEI] bfd [HUAWEI-bfd] quit [HUAWEI] bfd atob bind peer-ip 10.10.10.2 interface vlanif 100
# Create a BFD session named atoc to detect the multi-hop link to the peer IP address 10.10.20.2.
<HUAWEI> system-view [HUAWEI] bfd [HUAWEI-bfd] quit [HUAWEI] bfd atoc bind peer-ip 10.10.20.2