This is achieved by using the next-hop of the static route as the peer IP address for the BFD session. The static route is either installed or removed based on the status of the underlying BFD session. A static route whose next-hop is configured to be tracked by BFD is referred to as a ‘BFD tracked static route’ in the context of this document. This feature is supported for both IPv4 and IPv6 static routes.

BFD VXLAN Static Route EOS 4.30.2F

This feature adds support for specifying Resolution Rib Profile as system-connected per-via (next-hop) for static routes. System-connected means that a static route is only resolved if the next-hop is reachable over a connected route. If system-connected is not specified, it means that the static route is resolved if the next-hop is reachable over any kind of route in the routing FIB, including a connected route as well as a tunnel rib.

When a static route is configured with a nexthop group, by default the static route is eligible for FIB insertion

This feature introduces a metric for static routes so that the user can configure both administrative distance and

METRIC Multi Agent 4.24.1F Static Route

This feature adds support for Static Route UCMP local forwarding in the multi-agent routing protocol model. Unequal Cost Multi Path (UCMP) for Static Route is a mechanism for forwarding traffic from a device for an ECMP route in the ratio of the weights with which the next hops of that route are programmed in the FIB.

UCMP Static Route EOS 4.32.1F

EOS supports configuring and associating communities on static routes. These are carried into BGP on redistribution. 

BGP Static Route EOS 4.31.0F Community