BFD Timers for Router BGP BFD and Static Route BFD Sessions

On the SLX, you can provide the Bidirectional Forwarding Detection (BFD) timer configurations per static-route, per BGP peer and per BGP peer-group.
In SLX versions prior to 20.3.2:
1. The timer values provided per static-route, per BGP peer, and per BGP peer-group are not effective for the single-hop static route BFD sessions and single-hop router BGP BFD sessions.
2. For the timer values to be effective for the single-hop sessions, you must additionally configure the BFD timers also on the source interface (the interface acting as the BFD source).
But this restriction is removed from 20.3.2 onwards.
On the SLX, you can provide the BFD timer values directly at the “router bgp” level.
1. In SLX versions prior to 20.3.2:
  The timer values provided directly at the “router bgp” level are effective only for the multi-hop BFD sessions of both default and non-default VRF BGP peers.
2. In SLX versions 20.3.2 or above:
  The timer values provided directly at the “router bgp” level are effective for both multi-hop and single-hop BFD sessions of both default and non-default VRF BGP peers.

Note

Prior to upgrade of SLX-OS, ensure that you enable the maintenance mode on reboot using the efa inventory device setting update --maint-mode-enable-on-reboot Yes –ip <IP address of SLX> command. If you have upgraded SLX-OS without enabling the maintenance mode, trigger a manual drift and reconcile (DRC) using the command efa inventory drift-reconcile execute --ip <IP address of SLX>” –reconcile.
If you have not triggered the manual DRC, the efa fabric show --name <fabric name> command shows devices in cfg-refreshed state, and the intended BFD configuration does not get configured on the devices.
For the static-route and router-bgp BFD enhancement to be effective, you must upgrade SLX to 20.3.2 or later.