The static route BFD feature enables association of static routes with a BFD session to monitor the static route reachability. Depending on the status of the BFD session, the static routes are added to or deleted from the Routing Information Base (RIB). When you configure BFD, next-hop reachability depends on the BFD state of the BFD session corresponding to the specified next hop. If the BFD session of the configured next hop is down, the static route is not installed in the RIB.
The BFD session must be up for the static route. You must configure BFD on both the peers pointing to its neighbor as the next hop. There is no dependency on the configuration order of the static route and BFD configuration.
You can configure BFD for all static routes or for none of the static routes. OS10 supports BFD for both IPv4 and IPv6 static routes.
NOTE You can configure BFD for all the static routes. Meaning, there is no provision for configuring BFD only for some of the existing static routes.
Enable BFD for all static routes
Configuring BFD for static routes is a three-step process:
Enable BFD globally.
Configure static routes on both routers on the system (either local or remote). Configure the static route in such a way that the next-hop interfaces point to each other.
Configure BFD for static route using the
ip route bfd command.
