Administrator Guide

Example Configuration and Verification
The following example contains static routes for both default and nondefault VRFs.
Dell#sh run | grep bfd
bfd enable
ip route bfd prefix-list p4_le
ip route bfd vrf vrf1
ip route bfd vrf vrf2
ip route bfd vrf vrf1 prefix-list p4_le
The following example shows that sessions are created for static routes for the default VRF.
The following example shows that sessions are created for static routes for the nondefault VRFs.
Establishing Static Route Sessions on Specific Neighbors
You can selectively enable BFD sessions on specific neighbors based on a destination prefix-list.
When you establish a BFD session using the ip route bfd command, all the next-hop neighbors in the static route become
part of the BFD session. Starting with Dell Networking OS release 9.11.0.0, you can enable BFD sessions on specific next-hop
neighbors. You can specify the next-hop neighbors to be part of a BFD session by including them in a prefix-list.
Prefix lists are used in route maps and route filtering operations. You can use prefix lists as an alternative to existing access lists
(ACLs). A prefix is a portion of the IP address. Prefix lists constitute any number of bits in an IP address starting from the far
left bit of the far left octet. By specifying the exactly number of bits in an IP address that belong to a prefix list, the prefix list
can be used to aggregate addresses and perform some functions; for example, redistribution.
You can use the following options to enable or disable the BFD session:
● Permit – The permit option enables creation of a BFD session on the specified prefix list or prefix list range. The no permit
option enables tear down of the BFD session if and only if the ACL has no permit entry that shares the same neighbor.
● Deny – The deny option prevents BFD sessions from getting created for the specified prefix list or prefix list range.
For more information on prefix lists, see IP Prefix Lists.
To enable BFD sessions on specific neighbors, perform the following steps:
Enter the following command to enable BFD session on specific next-hop neighbors:
CONFIGURATION
ip route bfd prefix-list prefix-list-name
The BFD session is established for the next-hop neighbors that are specified in the prefix-list.
● The absence of a prefix-list causes BFD sessions to be enabled on all the eligible next-hop neighbors.
● You can use only valid IPv4 unicast address prefixes in the BFD prefix list. An erroneous IP prefix in a prefix-list causes the
entire prefix-list to be rejected.
● A BFD session is enabled for the directly connected next-hop neighbor specified in the configured destination prefix list.
● If you attach an empty prefix-list, all the existing established BFD sessions are teared down. If a destination prefix or prefix
range is not present in the prefix-list, then it is considered as an implicit deny.
●
When a destination prefix is deleted from the prefix-list using the no permit option, the corresponding BFD session is torn
down immediately. In this scenario, the BFD session tear down occurs only if the other destination prefixes in the prefix-list
are not pointing to the same neighbor.
● The permit option enables creation of a BFD session for the specified static destination prefix or prefix range. The system
prevents creation of BFD sessions for all other destination prefixes that are explicitly specified as Deny in the prefix list.
● If other destination prefixes in the prefix-list are pointing to the same neighbor, then the no permit or the deny option
on a particular destination prefix neither creates a BFD session on a neighbor nor removes the static routes from the unicast
database.
● BFD sessions created using any one IP prefix list are active at any given point in time. If a new prefix list is assigned, then
BFD sessions corresponding to the older (existing) prefix list are replaced with the newer ones.
● Each time a prefix list is modified, only addition or deletion of new entries in that prefix list are processed for BFD session
establishment or tear down.
Bidirectional Forwarding Detection (BFD)
145