To provide IP-link for public IPv4 static routes by using BFD sessions, you can bind static routes to BFD sessions. One static route can be bound to only one session.
Before you configure interworking between BFD and static routes, perform the following on devices at both ends:
Manually configuring the static BFD session. For details, see Creating a Static BFD Session.
The static BFD session can be one-hop or multi-hop.
system-view
BFD for IPv4 static route.
ip route-static [ vpn-instance vpn-instance-name ] ip-address { mask | mask-length } { nexthop-address [ public ] | interface-type interface-number [ nexthop-address ] | vpn-instance vpn-instance-name nexthop-address } [ preference preference ] track bfd-session cfg-name [ description description ]
BFD for IPv6 static route.
ipv6 route-static [ vpn-instance vpn-instance-name ] dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | vpn-instance vpn-instance-name nexthop-ipv6-address | nexthop-ipv6-address [ public ] } [ preference preference | tag tag ] * track bfd-session cfg-name [ description text ]
Both association between IPv4 static routes and BFDv6 and association between IPv6 static routes and BFDv4 are supported.
bfd
undo bfd session nonexistent-config-check disable
To check whether an associated BFD session is deleted, run the undo bfd session nonexistent-config-check disable command. After a static route is associated with a static BFD session, deleting the static BFD session causes the association to become invalid. After a device is enabled to check whether an associated BFD session is deleted, the device checks whether the BFD session is associated when deleting a BFD session.