Configuring BFD-DHCP Interworking

This section describes the procedure and precautions for configuring BFD-DHCP interworking.

Prerequisites

Before you configure BFD-DHCP interworking, complete the following tasks:

Configuring the device as the DHCP client and enable the device to obtain the IP address from the DHCP server. For details, see Configuring a DHCP Client.
Manually configuring static BFD sessions on devices at both ends. For details, see Creating a Static BFD Session.

The neighbor relationship can be successfully negotiated only if static BFD sessions (excluding auto-negotiated static sessions), must be specified with local and remote discriminators.

When one end of the BFD session is the DHCP client, the next hop of the static BFD session needs to be specified as nexthop dhcp. That is, when the device acts as the DHCP client, the obtained gateway address serves as the next-hop IP address for forwarding BFD packets.

For the peer DHCP client for BFD interworking, you need to specify the peer IP address in the static BFD session as the IP address of the DHCP client. If the IP address obtained by the DHCP client changes, you need to re-create a BFD session.

Context

In dual-uplink networking, if active/standby switchover between links is required, the active link must be assigned a high-priority route. The smaller the value, the higher the priority.

When the device acts as the DHCP client, the priority of the unr route obtained from the DHCP server is 60. In dual-uplink networking, if the active link is in DHCP mode and the standby link is in other mode, the route priority of the standby link must be larger than 60. Thereby, in DHCP-BFD interworking, the system disconnects the DHCP link upon identifying its fault. In this way, traffic is switched to the standby link.

To implement DHCP-BFD interworking, you need to only configure the device serving as the DHCP client.

Procedure

Access the system view.
```
system-view
```

Access the interface view.

interface interface-type interface-number

Associate DHCP with a BFD session.
```
dhcp client track bfd-session bfd-session-name
```
During DHCP-BFD interworking, the bound local-id value is the local discriminator of the monitored BFD session, not the BFD configuration name.