BFD for Static Routes

A static route is associated with a static BFD when the next-hop for the static route matches the neighbor address of the static BFD neighbor and BFD monitoring is enabled for the static route.

To use BFD for static routes, configure static routes (IPv4 or IPv6) and the corresponding static BFD separately. When static BFD is configured, the static route manager checks the routing table (RIBMGR) for a route to the BFD neighbor.

When the BFD session is up, a corresponding static route is added to RIBMGR. When the BFD session that monitors the static route goes down because the BFD neighbor is not reachable, static routes are removed from RIBMGR. These removed routes are replaced in RIBMGR when the BFD neighbor is reachable.

Single-hop BFD sessions use timeout values that are configured on the outgoing interface from which the BFD neighbor is reachable. Timeout values for multi-hop BFD sessions are specified with the static BFD neighbor. Multiple static routes with the same BFD neighbor use the same BFD session and timeout values.

Considerations for BFD for static routes

BFD for IPv6 static routes

If the BFD neighbor is link-local, the source IPv6 address must also be link-local.

If an IPv6 BFD session is running for a link-local BFD neighbor, the interface-type and interface-name parameters (for the ipv6 route static bfd command) are mandatory because the link-local address can be the same on multiple interfaces.

Supported Platforms

BFD for static routes is supported on SLX 9150, SLX 9250, and SLX 9740.