The bfd bind peer-ip command creates a static BFD session (by specifying the peer IP address) and accesses the BFD session view.
The undo bfd cfg-name command deletes the specified BFD session and BFD binding.
bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ] [ interface interface-type interface-number [ nexthop { nexthop-address | dhcp } ] ] [ source-ip source-ip ]
undo bfd cfg-name
| Parameter | Description | Value |
|---|---|---|
| cfg-name | Specifies the configuration name of BFD. | It is a string of 1 to 15 characters without spaces. |
| peer-ip peer-ip | Specifies the peer IP address bound to a BFD session. | It is in dotted decimal notation. |
| vpn-instance vpn-instance-name | Specifies the name of the VPN instance bound with the BFD session. If no VPN instance is specified, the peer IP address is considered as the public network address. | It must be the name of the existing VPN instance configured with the RD. |
| interface interface-type interface-number | Specifies the local Layer-3 interface bound to the BFD session. | It can be either a Layer-3 physical interface or a logical interface. |
| nexthop nexthop-address | Specifies the IP address of the next hop for forwarding BFD packets. | It is in dotted decimal notation. |
| nexthop dhcp | Specifies the next-hop IP address, which is also the obtained gateway address for forwarding BFD packets, when the device acts as the DHCP client. | - |
| source-ip source-ip | Specifies the source IP address of the BFD packet. | It is in dotted decimal notation. |
Prerequisites
Global BFD must have been enabled using the bfd command before BFD sessions are configured.
Configuration Impact
When you create BFD binding:
If only the peer IP address is specified, the system detects multi-hop routes.
If both the peer IP address and the local interface are specified, the system detects the one-hop link, that is, a fixed route with the local interface as the outbound interface and peer-ip as the next-hop IP address.
The configuration of the source IP address is as follows:
If source-ip is specified, the device uses this source-ip as the source IP address of the BFD packet. You must ensure that this source-ip parameter is correct. The system only checks whether this parameter is a valid source IP address (for example, it cannot be a multicast or broadcast address) without checking the correctness.
If the IP address of an outgoing interface is modified after a BFD session is configured, the source IP address in the BFD packet is not updated.
Follow-up Procedure
Run the discriminator { local discr-value | remote discr-value } command to correctly configure local and peer discriminators. Otherwise, BFD sessions cannot be established.
Run the commit command to commit the BFD configuration so that the configuration takes effect.
# Configure a BFD session named test, detecting the one-hop link between the local interface GE 1/0/1 to 1.1.1.2.
<sysname> system-view
[sysname] bfd
[sysname-bfd] quit
[sysname] bfd test bind peer-ip 1.1.1.2 interface GigabitEthernet 0/0/1 nexthop 10.1.1.1
[sysname-bfd-session-test]
# Create a BFD session named test to detect the multi-hop link destined for the IP address 1.1.2.2.
<sysname> system-view [sysname] bfd [sysname-bfd] quit [sysname] bfd test bind peer-ip 1.1.2.2 [sysname-bfd-session-test]