bfd bind peer-ip source-ip auto

Function

The bfd bind peer-ip source-ip auto command establishes the static BFD session with automatically negotiated discriminators, and accesses the BFD session view.

The undo bfd cfg-name command deletes the specified BFD session and the BFD binding.

Format

bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ] [ interface interface-type interface-number] source-ip source-ip auto

undo bfd cfg-name

Parameters

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.
source-ip source-ip	Specifies the source IP address of the BFD packet.	It is in dotted decimal notation.
auto	Enables the function of automatically negotiating the discriminator.	-

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When static routes are bound to BFD sessions but the peer device supports dynamic BFD sessions rather than static BFD sessions, configure static BFD sessions with automatically negotiated discriminators so that the local device can interwork with the peer device and dynamically update the status of static routes bound to the BFD sessions.

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:

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.
You must configure the source IP address when configuring the auto-negotiation function of the local discriminator.

If the discriminators of the static BFD session are automatically negotiated, you cannot configure the local and the remote discriminators.

Differences between the configurations of static BFD sessions with automatically negotiated discriminators and those of common static BFD sessions are as follows:

After running the bfd bind peer-ip source-ip auto command to configure the static BFD session with automatically negotiated discriminators, you can create corresponding BFD sessions without running the commit command.
After the parameters (such as the BFD control packet sending interval, receiving interval, and local detection multiple) of the auto-negotiated static BFD session are changed, they take effect without the commit command executed.

Example

# Configure the static BFD session with automatically negotiated discriminators.

<sysname> system-view
[sysname] bfd
[sysname-bfd] quit
[sysname] bfd single bind peer 10.0.0.2 interface GigabitEthernet 0/0/1 source-ip 10.0.0.1 auto
[sysname-bfd-session-single]