bfd bind peer-ip track-interface

Function

The bfd bind peer-ip track-interface command creates the binding between a BFD session and a peer IP address and displays the BFD session view.

By default, no binding between a BFD session and a peer IP address is created.

Format

bfd session-name bind peer-ip peer-ip [ vpn-instance vpn-name ] [ source-ip source-ip ] track-interface interface { interface-name | interface-type interface-number }

bfd session-name bind peer-ip peer-ip [ vpn-instance vpn-name ] [ source-ip source-ip ] track-interface controller { interface-name | interface-type interface-number }

Parameters

Parameter	Description	Value
session-name	Specifies the name of a BFD session.	The value is a string of 1 to 64 case-insensitive characters, spaces not supported.
peer-ip	Specifies the peer IP address bound to a BFD session.	The value is in dotted decimal notation.
vpn-instance vpn-name	Specifies the name of a VPN instance bound to a BFD session.	The value is a string of 1 to 31 case-sensitive characters, spaces not supported. In addition, the VPN instance name must not be _public_. When double quotation marks are used around the string, spaces are allowed in the string.
source-ip source-ip	Specifies the source IP address in a BFD packet. If no source IP address is specified, a device uses a source IP address in either of the following modes before sending BFD packets: During negotiation on BFD session parameters, the device searches for the IP address of an outbound interface connected to the remote end in the local routing table as the source IP address before sending BFD packets. During BFD detection, the device sets the source IP address to a fixed value. This parameter is manually configured only when BFD works with Unicast Reverse Path Forwarding (URPF). This is because URPF checks the source IP address in received packets. For URPF configuration details, see the chapter "URPF Configuration" in VRP Router Configuration Guide - Security.	The value is in dotted decimal notation.
track-interface	Specifies the interface traced by the BFD session.	-
interface interface-type interface-number	Specifies the type and number of the interface monitored by a BFD session.	-
controller	Specify controller.	-

Views

System view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
bfd	write

Usage Guidelines

Prerequisites

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

Configuration Impact

You can run the bfd bind peer-ip command to create the binding between a static BFD session and a peer IP address.

Follow-up Procedure

After the binding is created, you must perform the following operations to create the BFD session:

Run the discriminator command to set the local and remote discriminators for the BFD session.
Run the commit command to commit the configuration.
After the binding is created, the following optional configurations can be performed in the BFD session view:
Run the description command to configure a description for the BFD session.
Run the min-tx-interval command to set a desired minimum interval at which BFD packets are sent.
Run the min-rx-interval command to set a desired minimum interval at which BFD packets are received.
Run the detect-multiplier command to set a local detection multiplier for the BFD session.
Run the process-pst command to enable BFD to modify the PST if BFD detects a fault.
Run the wtr command to set a WTR time for the BFD session.

Precautions

If the source IP address is configured for the interface whose physical status is to be monitored by BFD, BFD packets are correctly forwarded after URPF has been enabled. The source-ip parameter must be configured correctly because the system checks only the validity of the source IP address. A multicast or broadcast address is an invalid source IP address.

The bfd bind peer-ip command must be run on both ends of a link because BFD detects faults in a bidirectional link.

If the IP address of the outbound interface is changed after a BFD session has been created, either of the following situations occurs:

During negotiation, the source IP address to be carried in BFD packets is updated.
During detection, the source IP address carried in BFD packets is not updated.
You can run the undo bfd session-name command to delete a specified BFD session and its binding information.

Example

# Create a BFD session named atob so that BFD can detect faults in the single-hop link from the local interface GE 0/1/28 to the peer interface whose IP address is 1.1.1.2.

<HUAWEI> system-view
[~HUAWEI] bfd
[*HUAWEI-bfd] quit
[*HUAWEI] bfd atob bind peer-ip 1.1.1.2 track-interface interface GigabitEthernet 0/1/28
[*HUAWEI-bfd-session-atob]

# Create a BFD session named session so that BFD can detect faults in the multi-hop link to the IP address 10.10.20.2.

<HUAWEI> system-view
[~HUAWEI] bfd
[*HUAWEI-bfd] quit
[*HUAWEI] bfd session bind peer-ip 10.10.20.2
[*HUAWEI-bfd-session-session]