Users Guide

Changing OSPFv3 session parameters
Configure BFD sessions with default intervals and a default role.
The parameters that you can configure are: desired tx interval, required min rx interval, detection multiplier, and system role.
Configure these parameters for all OSPFv3 sessions or all OSPFv3 sessions on a particular interface. If you change a parameter
globally, the change affects all OSPFv3 neighbors sessions. If you change a parameter at the interface level, the change affects
all OSPF sessions on that interface.
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 configured 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 final 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 routes
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 specific static routes. OS10 supports BFD for both IPv4 and IPv6 static routes.
Enable BFD for all static routes
Configuring BFD for static routes is a three-step process:
1. Enable BFD globally.
2. 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.
774
Layer 3