Method used to configure interworking between BFD Sessions and the DHCP client on the USG firewall

When serving as a DHCP client, an egress gateway cannot sensitize the accessibility of a link where it resides. If the link is faulty, service traffic cannot be rapidly switched over to a standby link, resulting in service interruption.
The interworking between the DHCP client and BFD sessions can address this issue. According to this function, the DHCP client is associated with BFD sessions, so that the firewall can dynamically determine the DHCP link accessibility based on the BFD session state.

Key configurations for the interworking between BFD sessions and the DHCP client on the USG firewall are as follows:
# Configure BFD session 1, and set the peer IP address to , local identifier to 10 , and remote identifier to 20 .
[USG_A] bfd
[USG_A-bfd] quit
[USG_A] bfd 1 bind peer-ip interface GigabitEthernet 0/0/1 nexthop dhcp
[USG_A-bfd-session-1] discriminator local 10
[USG_A-bfd-session-1] discriminator remote 20
[USG_A-bfd-session-1] commit
[USG_A-bfd-session-1] quit
Configure the interworking between the DHCP client and the BFD session.
# Associate the DHCP client with BFD sessions.
[USG_A] dhcp enable
[USG_A] interface GigabitEthernet 0/0/1
[USG_A-GigabitEthernet0/0/1] dhcp client enable track bfd-session 10
[USG_A-GigabitEthernet0/0/1] quit

Note: The USG6000 configuration must be consistent with the key configuration of the USG2000&5000. This case takes the USG2000&5000 as an example to describe the configuration. You can learn the USG6000 configuration in other configurations.

Scroll to top