Tag :: Static Route

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.

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

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