NOTE:
A maximum of 64 BFD sessions (shared between OSPF, VRRP, and STATIC) are supported.
A maximum of 16 static route BFD sessions is supported. All other BFD parameters (like detect
multiplier, transmit/receive intervals, authentication) are automatically obtained from the associated
VLAN interface of the
bfd source-ip
.
Parameters
destination network A.B.C.D
IP address mask of the destination network.
subnet mask A.B.C.D
IP address of the subnet mask.
prefix length
Network mask length for the destination.
NOTE:
The length parameter must be preceded by / (forward slash).
next hop A.B.C.D
IP address of the next hop.
vlan vlan-id
Specifies the destination VLAN for this route.
bfd source-ip IP address A.B.C.D
Specifies the local router source IP, which sends BFD packets to the next hop destination in order to monitor
connectivity with it. This option is required when the next hop IP is specified in the IP route command.
bfd destination-ip IP address A.B.C.D
Specifies the next hop destination IP to which BFD packets are sent from the local source IP configured on a
specified VLAN. This option is required when the destination VLAN is specified in the IP route command.
Restrictions
• A maximum of 16 unique (src/dst combinations) static route BFD sessions is supported.
• A single Static Route BFD session can be shared with multiple static routes having the same next-hop IP and
BFD source IP. It is recommended that you keep the total number of static routes, whose next-hop shares the
same physical link, under 64.
• BFD is supported on single-hop ipv4 static routes. Multi-hop functionality is not supported. BFD neighbors
must be no more than one IP hop away for Echo mode.
• BFD for Static Route is not supported over management VLAN. BFD source IP address should not be DHCP
learned.
• BFD authentication mismatches can cause the registered applications (OSPF and STATIC) to flap.
• BFD is resource intensive protocol. Setting aggressive control timers for static routes further impacts the
system, which could lead to session flaps. It is recommended that a transmit interval be a minimum of 2.
Instead, use Echo mode to achieve faster failure detection.
• BFD is only a failure detection protocol. As the number of routes increases, there can be a slight increase in
the route convergence times, even though the failure detection times do not change.
• If BFD Echo enters the disabled state on any session, it remains there. After fixing the connectivity issues, the
administrative state must be toggled to re-enable it.
• Once a static route BFD session is UP, any change in BFD authentication causing mismatch for the static
route BFD session results in a complete removal of the static route from the RIB until the BFD authentication
mismatch is resolved. If a mismatch exists before the session is established, the session remains DOWN. The
424
Aruba 3810 / 5400R Multicast and Routing Guide for ArubaOS-
Switch 16.08
