bfd bind peer-ip source-ip auto

Function

The bfd bind peer-ip source-ip auto command creates a static BFD session with automatically negotiated discriminators.

The undo bfd session-name command deletes a specified BFD session.

By default, no static BFD session with automatically negotiated discriminators is established.

Format

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

undo bfd session-name

Parameters

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 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-type interface-number	Specifies the type and number of the interface bound to the BFD session. interface-type specifies the type of the interface. interface-number specifies the number of the interface.	-
source-ip ip-address	Indicates the source IP address carried in BFD packets, that is, IP address of the outbound interface.	-
auto	Enables automatic negotiation of local and remote discriminators.	-

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The local device where a BFD session with automatically negotiated parameters is configured can negotiate with the remote device where a dynamic BFD session is configured; however, the local device enabled with static BFD can establish a BFD session with the remote device enabled with static BFD only. When configuring a BFD session with automatically negotiated parameters or a static BFD session, you can specify the BFD session name. The name of a dynamic BFD session is generated dynamically. When the network changes, the name of the dynamic BFD session may change.

When the remote end is configured with dynamic BFD and the local end needs to be configured with association between BFD and static route (BFD session name needs to be specified during association configuration), a BFD session with automatically negotiated parameters can be configured on the local end. Then the local end can establish a BFD session with the remote end enabled with dynamic BFD and association between BFD and static route can be implemented.

When creating a static BFD session with automatically negotiated discriminators, 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.
Ensure that the source IP address is correct. The system only checks whether the source IP address is valid (for example, it cannot be a multicast or broadcast address) without checking correctness.
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.
If the peer IP address, VPN instance, and local interface are specified, BFD is configured to detect the single-hop link in the VPN instance.

Prerequisites

Global BFD has been enabled by using the bfd command in the system view.

Precautions

When creating a BFD session, bind the BFD session to the peer IP address and the local 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.

Unlike common static BFD sessions, static BFD sessions with automatically negotiated discriminators have separate characteristics:

The bfd bind peer-ip source-ip auto command can be run and immediately create a static BFD session with automatically negotiated discriminators, without the commit command executed.
Parameters of a static BFD session with automatically negotiated discriminators take effect immediately after being modified, without the commit command executed. The parameters include the minimum interval at which BFD packets are sent and received and the detection multiplier.
The commit command can be run for a static BFD session with automatically negotiated discriminators to support the forward version compatibility.

Example

# Create a static BFD session with automatically negotiated discriminators.

<HUAWEI> system-view
[HUAWEI] bfd
[HUAWEI-bfd] quit
[HUAWEI] bfd atob bind peer-ip 10.1.1.2 interface vlanif 100 source-ip 10.1.1.1 auto