Connectivity Guide

NOTE: By default, OSPF uses the following BFD parameters for it's neighbors: min_tx = 200 msec, min_rx = 200 msec, multiplier
= 3, role = active. If BFD is congured under interface context, that will be given high priority.
To change parameters for all OSPFv3 sessions or for OSPF sessions on a single interface, use the following commands:
1 Change parameters for OSPF sessions.
bfd all-neighbors interval milliseconds min_rx milliseconds multiplier value role [active |
passive]
ROUTER-OSPFv3 Mode
2 Change parameters for all OSPF sessions on an interface.
ipv6 ospf bfd all-neighbors interval milliseconds min_rx milliseconds multiplier value role
[active | passive]
INTERFACE CONFIGURATION Mode
Disabling BFD for OSPFv3
If you disable BFD globally, all sessions are torn down and sessions on the remote system are placed in a Down state. If you disable BFD on
an interface, sessions on the interface are torn down and sessions on the remote system are placed in a Down state. Disabling BFD does
not trigger a change in BFD clients; a nal Admin Down packet is sent before the session is terminated.
To disable BFD sessions, use the following commands:
1 Disable BFD sessions with all OSPF neighbors.
no bfd all-neighbors
ROUTER-OSPFv3 Mode
2 Disable BFD sessions with all OSPF neighbors on an interface.
ipv6 ospf bfd all-neighbors disable
INTERFACE CONFIGURATION Mode
To re-enable BFD, disabled the interface alone using the following commands:
• no ipv6 ospf bfd all-neighbors command
• ipv6 ospf bfd all-neighbors
BFD for Static route
The static Route BFD feature enables association of static routes with a BFD session in order to monitor the static route reachability.
Depending on the status of the BFD session the static routes are added to or removed from the Routing Information Base (RIB). When
BFD is congured, the nexthop reachability is dependent on the BFD state of the BFD session corresponding to the specied next hop. If
the BFD session of the congured nexthop is down the static route will not be installed in the RIB.
The BFD session needs to be established successfully for the static route. BFD must be congured on both the peers pointing to its
neighbor as next hop. There is no dependency on the order of conguration of static route and BFD conguration. The user has provision
to congure BFD for all the static routes congured or for none of the static routes. Both IPv4 and IPv6 static route BFD is supported.
NOTE
: You can congure BFD for all the static routes. Meaning, there is no provision for conguring BFD only for some of the
existing static routes.
Conguring
BFD for static routes is a three-step process:
1 Enable BFD Globally.
2 Congure static routes on both routers on the system (either local or remote). Congure static route in such a way that the next-hop
interfaces point to each other.
312
Layer 3