Table Of Contents
Configuring Bidirectional Forwarding Detection
Information About BFD
Asynchronous Mode
BFD Detection of Failures
Distributed Operation
BFD Echo Function
Security
High Availability
Virtualization Support
Licensing Requirements for BFD
Prerequisites for BFD
Guidelines and Limitations
Default Settings
Configuring BFD
Configuration Hierarchy
Task Flow for Configuring BFD
Enabling the BFD Feature
Configuring Global BFD Parameters
Configuring BFD on an Interface
Configuring BFD on a Port Channel
Configuring BFD Echo Function
Optimizing BFD on Subinterfaces
Configuring BFD Support for Routing Protocols
Configuring BFD on BGP
Configuring BFD on EIGRP
Configuring BFD on OSPF
Configuring BFD on IS-IS
Configuring BFD on HSRP
Configuring BFD on VRRP
Configuring BFD on PIM
Configuring BFD on Static Routes
Configuring BFD on MPLS TE Fast Reroute
Disabling BFD on an Interface
Verifying the BFD Configuration
Monitoring BFD
Configuration Examples for BFD
Additional References
Related Documents
RFCs
Feature History for BFD
Configuring Bidirectional Forwarding Detection
This chapter describes how to configure Bidirectional Forwarding Detection (BFD) on Cisco NX-OS devices.
This chapter includes the following sections:
•
Information About BFD
•Licensing Requirements for BFD
•Prerequisites for BFD
•Guidelines and Limitations
•Default Settings
•Configuring BFD
•Verifying the BFD Configuration
•Monitoring BFD
•Configuration Examples for BFD
•Additional References
•Feature History for BFD
Information About BFD
BFD is a detection protocol designed to provide fast forwarding-path failure detection times for media types, encapsulations, topologies, and routing protocols. You can use BFD to detect forwarding path failures at a uniform rate, rather than the variable rates for different protocol hello mechanisms. BFD makes network profiling and planning easier and reconvergence time consistent and predictable.
BFD provides subsecond failure detection between two adjacent devices and can be less CPU-intensive than protocol hello messages because some of the BFD load can be distributed onto the data plane on supported modules.
This section includes the following topics:
•Asynchronous Mode
•BFD Detection of Failures
•Distributed Operation
•BFD Echo Function
•Security
•High Availability
•Virtualization Support
Asynchronous Mode
Cisco NX-OS supports the BFD asynchronous mode, which sends BFD control packets between two adjacent devices to activate and maintain BFD neighbor sessions between the devices. You configure BFD on both devices (or BFD neighbors). Once BFD has been enabled on the interfaces and on the appropriate protocols, Cisco NX-OS creates a BFD session, negotiates BFD session parameters, and begins to send BFD control packets to each BFD neighbor at the negotiated interval. The BFD session parameters include the following:
•Desired minimum transmit interval—The interval at which this device wants to send BFD hello messages.
•Required minimum receive interval—The minimum interval at which this device can accept BFD hello messages from another BFD device.
•Detect multiplier—The number of missing BFD hello messages from another BFD device before this local device detects a fault in the forwarding path.
Figure 5-1 shows how a BFD session is established. The figure shows a simple network with two routers running OSPF and BFD. When OSPF discovers a neighbor (1), it sends a request to the local BFD process to initiate a BFD neighbor session with the OSPF neighbor router (2). The BFD neighbor session with the OSPF neighbor router is now established (3).
Figure 5-1 Establishing a BFD Neighbor Relationship
BFD Detection of Failures
Once a BFD session has been established and timer negotiations are complete, BFD neighbors send BFD control packets that act in the same manner as an IGP hello protocol to detect liveliness, except at a more accelerated rate. BFD detects a failure, but the protocol must take action to bypass a failed peer.
BFD sends a failure detection notice to the BFD-enabled protocols when it detects a failure in the forwarding path. The local device can then initiate the protocol recalculation process and reduce the overall network convergence time.
Figure 5-2 shows what happens when a failure occurs in the network (1). The BFD neighbor session with the OSPF neighbor router is torn down (2). BFD notifies the local OSPF process that the BFD neighbor is no longer reachable (3). The local OSPF process tears down the OSPF neighbor relationship (4). If an alternative path is available, the routers immediately start converging on it.
Note The BFD failure detection occurs in less than a second, which is much faster than OSPF Hello messages could detect the same failure.
Figure 5-2 Tearing Down an OSPF Neighbor Relationship
Distributed Operation
Cisco NX-OS can distribute the BFD operation to compatible modules that support BFD. This process offloads the CPU load for BFD packet processing to the individual modules that connect to the BFD neighbors. All BFD session traffic occurs on the module CPU. The module informs the supervisor when a BFD failure is detected.
BFD Echo Function
The BFD echo function sends echo packets from the forwarding engine to the remote BFD neighbor. The BFD neighbor forwards the echo packet back along the same path in order to perform detection; the BFD neighbor does not participate in the actual forwarding of the echo packets. The echo function and the forwarding engine are responsible for the detection process. BFD can use the slow timer to slow down the asycnhronous session when the echo function is enabled and reduce the number of BFD control packets that are sent between two BFD neighbors. Also, the forwarding engine tests the forwarding path on the remote (neighbor) system without involving the remote system, so there is less interpacket delay variability and faster failure detection times.
The echo function is without asymmetry when both BFD neighbors are running echo function.
Note Unicast Reverse Path Forwarding check (uRPF) is disabled by default. If you need to enable it on an interface functioning with BFD, the BFD echo function must be disabled.
Security
Cisco NX-OS uses the packet Time to Live (TTL) value to verify that the BFD packets came from an adjacent BFD peer. For all asynchronous and echo request packets, the BFD neighbor sets the TTL value to 255 and the local BFD process verifies the TTL value as 255 before processing the incoming packet. For the echo response packet, BFD sets the TTL value to 254.
Beginning with Cisco NX-OS Release 5.2, you can configure SHA-1 authentication of BFD packets.
High Availability
BFD supports stateless restarts and in-service software upgrades (ISSUs). ISSU allows you to upgrade software without impacting forwarding. After a reboot or supervisor switchover, Cisco NX-OS applies the running configuration and BFD immediately sends control packets to the BFD peers.
Virtualization Support
BFD supports virtual routing and forwarding instances (VRFs). VRFs exist within virtual device contexts (VDCs). By default, Cisco NX-OS places you in the default VDC and default VRF unless you specifically configure another VDC and VRF. For more information, see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 5.x.
Licensing Requirements for BFD
The following table shows the licensing requirements for this feature:
Product
|
License Requirement
|
Cisco NX-OS
|
BFD requires no license. Any feature not included in a license package is bundled with the Cisco NX-OS system images and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide.
|
Prerequisites for BFD
BFD has the following prerequisites:
•You must enable the BFD feature (see the "Enabling the BFD Feature" section).
•For any client protocols that you want to enable BFD on, you enable BFD in that client protocol. See the "Configuring BFD Support for Routing Protocols" section.
•Disable Internet Control Message Protocol (ICMP) redirect messages on a BFD-enabled interfaces.
•Disable the IP packet verification check for identical IP source and destination addresses in the default VDC.
•See other detailed prerequisites that are listed with the configuration tasks.
Guidelines and Limitations
BFD has the following configuration guidelines and limitations:
•BFD supports BFD version 1.
•BFD supports IPv4.
•BFD supports single-hop BFD.
•BFD for BGP supports single-hop EBGP and iBGP peers.
•BFD supports keyed SHA-1 authentication beginning with Cisco NX-OS Release 5.2.
•BFD supports the following Layer 3 interfaces—physical interfaces, port channels, subinterfaces, and VLAN interfaces.
•BFD depends on a Layer 3 adjacency information to discover topology changes, including Layer 2 topology changes. A BFD session on a VLAN interface (SVI) may not be up after the convergence of the Layer 2 topology if there is no Layer 3 adjacency information available.
•Port channel configuration limitations:
–For Layer 3 port channels used by BFD, you must enable LACP on the port channel.
–For Layer 2 port channels used by SVI sessions, you must enable LACP on the port channel.
•SVI limitations:
–An ASIC reset will cause traffic disruption for other ports. This event could possibly cause SVI sessions on other ports to flap. Some triggers for an ASIC reset are port moves between VDCs, reloading a VDC, or if the carrier interface is a virtual port channel (vPC), BFD is not supported over the SVI interface.
–When you change the topology (for example, add or delete a link into a VLAN, delete a member from a Layer 2 port channel, and so on), the SVI session could be affected. It may go down first and then come up after the topology discovery is finished.
Tip If you do not want the SVI sessions to flap and you need to change the topology, you can disable the BFD feature before making the changes and reenable BFD after the changes have been made. You can also configure the BFD timer to be a large value (for example, 5 seconds), and change it back to a fast timer after the above events complete.
•BFD over VLAN interfaces that have member ports only on a N7K-F132XL-15 module are not supported. You should disable BFD over any VLAN with member ports only on a N7K-F132XL-15 module.
Note If you enable BFD at the router level (for example, from OSPF), any BFD sessions over a N7K-F132XL-15 linecard will not come-up. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x for information about OSPF and other routing protocols.
•When you configure the BFD Echo function on the distributed Layer 3 port channels, reloading a member module flaps the BFD session hosted on that module, which results in a packet loss.
If you connect the BFD peers directly without a Layer 2 switch in between, you can use the BFD per-link mode as an alternative solution.
Note Using BFD per-link mode and sub-interface optimization simultaneously on a Layer 3 port channel is not supported.
•HSRP for IPv4 is supported with BFD. HSRP for IPv6 is not supported with BFD.
•BFD packets generated by supported the Cisco NX-OS device linecards are sent with COS 6/DSCP CS6. The DSCP/COS values for BFD packets are not user configurable.
Default Settings
Table 5-1 lists the default settings for BFD parameters.
Table 5-1 Default BFD Parameters
Parameters
|
Default
|
BFD feature
|
Disabled
|
Required minimum receive interval
|
50 milliseconds
|
Desired minimum transmit interval
|
50 milliseconds
|
Detect multiplier
|
3
|
Echo function
|
Enabled
|
Mode
|
Asynchronous
|
Port channel
|
Logical mode (one session per source-destination pair address).
|
Slow timer
|
2000 milliseconds
|
Subinterface optimization
|
Disabled
|
Configuring BFD
This section includes the following topics:
•Configuration Hierarchy
•Task Flow for Configuring BFD
•Enabling the BFD Feature
•Configuring Global BFD Parameters
•Configuring BFD on an Interface
•Configuring BFD on a Port Channel
•Configuring BFD Echo Function
•Optimizing BFD on Subinterfaces
•Configuring BFD Support for Routing Protocols
Configuration Hierarchy
You can configure BFD at the global level and at the interface or subinterface level (for physical interfaces and port channels). The interface or sub-interface configuration overrides global configuration. On supported interfaces, the subinterface-level configuration overrides the interface or port channel configuration unless subinterface optimization is enabled. See the "Optimizing BFD on Subinterfaces" section for more information.
Note Using BFD per-link mode and sub-interface optimization simultaneously on a Layer 3 port channel is not supported.
For physical ports that are members of a port channel, the member port inherits the master port channel BFD configuration. The member port subinterfaces can override the master port channel BFD configuration, unless subinterface optimization is enabled.
Task Flow for Configuring BFD
Follow these steps to configure BFD:
Step 1 Enabling the BFD Feature.
Step 2 Configuring Global BFD Parameters or Configuring BFD on an Interface.
Step 3 Configuring BFD Support for Routing Protocols.
Enabling the BFD Feature
You must enable the BFD feature before you can configure BFD on an interface and protocol within a device (VDC).
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
SUMMARY STEPS
1. configure terminal
2. feature bfd
3. (Optional) show feature | include bfd
4. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
feature bfd
Example:
switch(config)# feature bfd
|
Enables the BFD feature.
|
Step 3
|
show feature | include bfd
Example:
switch(config)# show feature | include
bfd
|
(Optional) Displays enabled and disabled features.
|
Step 4
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Use the no feature bfd command to disable the BFD feature and remove all associated configuration.
Command
|
Purpose
|
no feature bfd
Example:
switch(config)# no feature bfd
|
Disables the BFD feature and removes all associated configuration.
|
Configuring Global BFD Parameters
You can configure the BFD session parameters for all BFD sessions on the device. The BFD session parameters are negotiated between the BFD peers in a three-way handshake.
See the "Configuring BFD on an Interface" section to override these global session parameters on an interface.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
SUMMARY STEPS
1. configure terminal
2. bfd interval mintx min_rx msec multiplier value
3. bfd slow-timer [interval]
4. bfd echo-interface loopback interface number
5. (Optional) show running-config bfd
6. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
bfd interval mintx min_rx msec
multiplier value
Example:
switch(config)# bfd interval 50 min_rx
50 multiplier 3
|
Configures the BFD session parameters for all BFD sessions on the device. You can override these values by configuring the BFD session parameters on an interface. The mintx and msec range is from 50 to 999 milliseconds and the default is 50. The multiplier range is from 1 to 50. The multiplier default is 3.
|
Step 3
|
bfd slow-timer [interval]
Example:
switch(config)# bfd slow-timer 2000.
|
Configures the slow timer used in the echo function.This value determines how fast BFD starts up a new session and at what speed the asynchronous sessions use for BFD control packets when the echo function is enabled. The slow-timer value is used as the new control packet interval, while the echo packets use the configured BFD intervals. The echo packets are used for link failure detection, while the control packets at the slower rate maintain the BFD session. The range is from 1000 to 30000 milliseconds. The default is 2000.
|
Step 4
|
bfd echo-interface loopback interface
number
Example:
switch(config-if)# bfd echo-interface
loopback 1 3
|
Configures the interface used for Bidirectional Forwarding Detection (BFD) echo frames. This command changes the source address for the echo packets to the one configured on the specified loopback interface. The interface number range is from 0 to 1023.
|
Step 5
|
show running-config bfd
Example:
switch(config)# show running-config bfd
|
(Optional) Displays the BFD running configuration.
|
Step 6
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on an Interface
You can configure the BFD session parameters for all BFD sessions on an interface. The BFD session parameters are negotiated between the BFD peers in a three-way handshake.
This configuration overrides the global session parameters for the configured interface.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
SUMMARY STEPS
1. configure terminal
2. interface int-if
3. bfd interval mintx min_rx msec multiplier value
4. (Optional) bfd authentication keyed-sha1 keyid id key ascii_key
5. (Optional) show running-config bfd
6. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
interface int-if
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 3
|
bfd interval mintx min_rx msec
multiplier value
Example:
switch(config-if)# bfd interval 50
min_rx 50 multiplier 3
|
Configures the BFD session parameters for all BFD sessions on the interface. This overrides the global BFD session parameters. The mintx and msec range is from 50 to 999 milliseconds and the default is 50. The multiplier range is from 1 to 50. The multiplier default is 3.
|
Step 4
|
bfd authentication keyed-sha1 keyid id
key ascii_key
Example:
switch(config-if)# bfd authentication
keyed-sha1 keyid 1 ascii_key cisco123
|
(Optional) Configures SHA-1 authentication for all BFD sessions on the interface. The ascii_key string is a secret key shared among BFD peers. The id value, a number between 0 and 255, is assigned to this particular ascii_key. BFD packets specify the key by id, allowing the use of multiple active keys.
To disable SHA-1 authentication on the interface, use the no form of the command.
|
Step 5
|
show running-config bfd
Example:
switch(config-if)# show running-config
bfd
|
(Optional) Displays the BFD running configuration.
|
Step 6
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on a Port Channel
You can configure the BFD session parameters for all BFD sessions on a port channel. If per-link mode is used for Layer 3 port channels, BFD creates a session for each link in the port channel and provides an aggregate result to client protocols. For example, if the BFD session for one link on a port channel is up, BFD informs client protocols, such as OSPF, that the port channel is up. The BFD session parameters are negotiated between the BFD peers in a three-way handshake.
This configuration overrides the global session parameters for the configured port channel. The member ports of the port channel inherit the port channel BFD session parameters, unless you configure subinterface-level BFD parameters on a member port. In that case, the member port subinterface uses the subinterface BFD configuration if subinterface optimization is not enabled. See the "Optimizing BFD on Subinterfaces" section for more information.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Ensure that you enable LACP on the port channel before you enable BFD.
Enable the BFD feature. See the "Enabling the BFD Feature" section.
SUMMARY STEPS
1. configure terminal
2. interface port-channel number
3. bfd per-link
4. (Optional) bfd interval mintx min_rx msec multiplier value
5. (Optional) bfd authentication keyed-sha1 keyid id key ascii_key
6. (Optional) show running-config bfd
7. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
interface port-channel number
Example:
switch(config)# interface port-channel 2
switch(config-if)#
|
Enters port channel configuration mode. Use the ? keyword to display the supported number range.
|
Step 3
|
bfd per-link
Example:
switch(config-if)# bfd per-link
|
Configures the BFD sessions for each link in the port channel.
|
Step 4
|
bfd interval mintx min_rx msec
multiplier value
Example:
switch(config-if)# bfd interval 50
min_rx 50 multiplier 3
|
(Optional) Configures the BFD session parameters for all BFD sessions on the port channel. This overrides the global BFD session parameters. The mintx and msec range is from 50 to 999 milliseconds and the default is 50. The multiplier range is from 1 to 50. The multiplier default is 3.
|
Step 5
|
bfd authentication keyed-sha1 keyid id
key ascii_key
Example:
switch(config-if)# bfd authentication
keyed-sha1 keyid 1 ascii_key cisco123
|
(Optional) Configures SHA-1 authentication for all BFD sessions on the interface. The ascii_key string is a secret key shared among BFD peers. The id value, a number between 0 and 255, is assigned to this particular ascii_key. BFD packets specify the key by id, allowing the use of multiple active keys.
To disable SHA-1 authentication on the interface, use the no form of the command.
|
Step 6
|
show running-config bfd
Example:
switch(config-if)# show running-config
bfd
|
(Optional) Displays the BFD running configuration.
|
Step 7
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD Echo Function
You can configure the BFD echo function on one or both ends of a BFD-monitored link. The echo function slows down the required minimum receive interval, based on the configured slow timer. The RequiredMinEchoRx BFD session parameter is set to zero if the echo function is disabled. The slow timer becomes the required minimum receive interval if the echo function is enabled.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Configure the BFD session parameters. See the "Configuring Global BFD Parameters" section or the "Configuring BFD on an Interface" section.
Ensure that Internet Control Message Protocol (ICMP) redirect messages are disabled on BFD-enabled interfaces. Use the no ip redirects command on the interface.
Ensure that the IP packet verification check for identical IP source and destination addresses is disabled. Use the no hardware ip verify address identical command in the default VDC. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more information on this command.
SUMMARY STEPS
1. configure terminal
2. bfd slow-timer echo-interval
3. interface int-if
4. bfd echo
5. (Optional) show running-config bfd
6. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
bfd slow-timer echo-interval
Example:
switch(config)# bfd slow-timer 2000
|
Configures the slow timer used in the echo function. This value determines how fast BFD starts up a new session and is used to slow down the asynchronous sessions when the BFD echo function is enabled. This value overwrites the required minimum receive interval when the echo function is enabled. The range is from 1000 to 30000 milliseconds. The default is 2000.
|
Step 3
|
interface int-if
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 4
|
bfd echo
Example:
switch(config-if)# bfd echo
|
Enables the echo function. The default is enabled.
|
Step 5
|
show running-config bfd
Example:
switch(config-if)# show running-config
bfd
|
(Optional) Displays the BFD running configuration.
|
Step 6
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Optimizing BFD on Subinterfaces
You can optimize BFD on subinterfaces. BFD creates sessions for all configured subinterfaces. BFD sets the subinterface with the lowest configured VLAN ID as the master subinterface and that subinterface uses the BFD session parameters of the parent interface. The remaining subinterfaces use the slow timer. If the optimized subinterface session detects an error, BFD marks all subinterfaces on that physical interface as down.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Configure the BFD session parameters. See the "Configuring Global BFD Parameters" section or the "Configuring BFD on an Interface" section.
Ensure that these subinterfaces connect to another Cisco NX-OS device. This feature is supported on Cisco NX-OS only.
SUMMARY STEPS
1. configure terminal
2. interface int-if
3. bfd optimize subinterface
4. (Optional) show running-config bfd
5. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
interface int-if
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 3
|
bfd optimize subinterface
Example:
switch(config-if)# bfd optimize
subinterface
|
Optimizes subinterfaces on a BFD-enabled interface. The default is disabled.
|
Step 4
|
show running-config bfd
Example:
switch(config-if)# show running-config
bfd
|
(Optional) Displays the BFD running configuration.
|
Step 5
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD Support for Routing Protocols
This section includes the following topics:
•Configuring BFD on BGP
•Configuring BFD on EIGRP
•Configuring BFD on OSPF
•Configuring BFD on IS-IS
•Configuring BFD on HSRP
•Configuring BFD on VRRP
•Configuring BFD on PIM
•Configuring BFD on Static Routes
•Configuring BFD on MPLS TE Fast Reroute
•Disabling BFD on an Interface
Configuring BFD on BGP
You can configure BFD for the Border Gateway Protocol (BGP).
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Configure the BFD session parameters. See the "Configuring Global BFD Parameters" section or the "Configuring BFD on an Interface" section.
Enable the BGP feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more information.
SUMMARY STEPS
1. configure terminal
2. router bgp as-number
3. neighbor {ip-address | ipv6-address} remote-as as-number
4. bfd
5. (Optional) show running-config bgp
6. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
router bgp as-number
Example:
switch(config)# router bgp 64496
switch(config-router)#
|
Enables BGP and assigns the AS number to the local BGP speaker. The AS number can be a 16-bit integer or a 32-bit integer in the form of a higher 16-bit decimal number and a lower 16-bit decimal number in xx.xx format.
|
Step 3
|
neighbor {ip-address | ipv6-address}
remote-as as-number
Example:
switch(config-router)# neighbor
209.165.201.1 remote-as 64497
switch(config-router-neighbor)#
|
Configures the IPv4 or IPv6 address and AS number for a remote BGP peer. The ip-address format is x.x.x.x. The ipv6-address format is A:B::C:D.
|
Step 4
|
bfd
Example:
switch(config-router-neighbor)# bfd
|
Enables BFD for this BGP peer.
|
Step 5
|
show running-config bgp
Example:
switch(config-router-neighbor)# show
running-config bgp
|
(Optional) Displays the BGP running configuration.
|
Step 6
|
copy running-config startup-config
Example:
switch(config-router-neighbor)# copy
running-config startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on EIGRP
You can configure BFD for the Enhanced Interior Gateway Routing Protocol (EIGRP).
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Configure the BFD session parameters. See the "Configuring Global BFD Parameters" section or the "Configuring BFD on an Interface" section.
Enable the EIGRP feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more information.
SUMMARY STEPS
1. configure terminal
2. router eigrp instance-tag
3. bfd
4. interface int-if
5. (Optional) ip eigrp instance-tag bfd
6. (Optional) show ip eigrp [vrf vrf-name] [interfaces if]
7. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
router eigrp instance-tag
Example:
switch(config)# router eigrp Test1
switch(config-router)#
|
Creates a new EIGRP process with the configured instance tag. The instance tag can be any case-sensitive, alphanumeric string up to 20 characters.
If you configure an instance-tag that does not qualify as an AS number, you must use the autonomous-system command to configure the AS number explicitly or this EIGRP instance will remain in the shutdown state.
|
Step 3
|
bfd
Example:
switch(config-router-neighbor)# bfd
|
(Optional) Enables BFD for all EIGRP interfaces.
|
Step 4
|
interface int-if
Example:
switch(config-router-neighbor)#
interface ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 5
|
ip eigrp instance-tag bfd
Example:
switch(config-if)# ip eigrp Test1 bfd
|
(Optional) Enables or disables BFD on an EIGRP interface. The instance tag can be any case-sensitive, alphanumeric string up to 20 characters.
The default is disabled.
|
Step 6
|
show ip eigrp [vrf vrf-name] [interfaces
if]
Example:
switch(config-if)# show ip eigrp
|
(Optional) Displays information about EIGRP. The vrf-name can be any case-sensitive, alphanumeric string up to 32 characters.
|
Step 7
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on OSPF
You can configure BFD for the Open Shortest Path First version 2 (OSPFv2).
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Configure the BFD session parameters. See the "Configuring Global BFD Parameters" section or the "Configuring BFD on an Interface" section.
Enable the OSPF feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more information.
SUMMARY STEPS
1. configure terminal
2. router ospf instance-tag
3. bfd
4. interface int-if
5. (Optional) if ospf bfd
6. (Optional) show ip ospf [vrf vrf-name] [interface if]
7. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
router ospf instance-tag
Example:
switch(config)# router ospf 201
switch(config-router)#
|
Creates a new OSPFv2 instance with the configured instance tag. The instance tag can be any case-sensitive, alphanumeric string up to 20 characters.
|
Step 3
|
bfd
Example:
switch(config-router)# bfd
|
(Optional) Enables BFD for all OSPFv2 interfaces.
|
Step 4
|
interface int-if
Example:
switch(config-router)# interface
ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 5
|
ip ospf bfd
Example:
switch(config-if)# ip ospf 201 bfd
|
(Optional) Enables or disables BFD on an OSPFv2 interface. The default is disabled.
|
Step 6
|
show ip ospf [vrf vrf-name] [interface
if]
Example:
switch(config-if)# show ip ospf
|
(Optional) Displays information about OSPF. The vrf-name can be any case-sensitive, alphanumeric string up to 32 characters.
|
Step 7
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on IS-IS
You can configure BFD for the Intermediate System-to-Intermediate System (IS-IS) protocol.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Configure the BFD session parameters. See the "Configuring Global BFD Parameters" section or the "Configuring BFD on an Interface" section.
Enable the IS-IS feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more information.
SUMMARY STEPS
1. configure terminal
2. router isis instance-tag
3. bfd
4. interface int-if
5. (Optional) isis bfd
6. (Optional) show isis [vrf vrf-name] [interface if]
7. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
router isis instance-tag
Example:
switch(config)# router isis Enterprise
switch(config-router)#
|
Creates a new IS-IS instance with the configured instance tag.
|
Step 3
|
bfd
Example:
switch(config-router)# bfd
|
(Optional) Enables BFD for all OSPFv2 interfaces.
|
Step 4
|
interface int-if
Example:
switch(config-router)# interface
ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 5
|
isis bfd
Example:
switch(config-if)# isis bfd
|
(Optional) Enables or disables BFD on an IS-IS interface. The default is disabled.
|
Step 6
|
show isis [vrf vrf-name] [interface if]
Example:
switch(config-if)# showisis
|
(Optional) Displays information about IS-IS. The vrf-name can be any case-sensitive, alphanumeric string up to 32 characters.
|
Step 7
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on HSRP
You can configure BFD for the Hot Standby Router Protocol (HSRP). The active and standby HSRP routers track each other through BFD. If BFD on the standby HSRP router detects that the active HSRP router is down, the standby HSRP router treats this event as an active time rexpiry and takes over as the active HSRP router.
The show hsrp detail will show this event as BFD@Act-down or BFD@Sby-down.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Configure the BFD session parameters. See the "Configuring Global BFD Parameters" section or the "Configuring BFD on an Interface" section.
Enable the HSRP feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more information.
SUMMARY STEPS
1. configure terminal
2. hsrp bfd all-interfaces
3. interface int-if
4. (Optional) hsrp bfd
5. (Optional) show running-config hsrp
6. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 1
|
hsrp bfd all-interfaces
Example:
switch# hsrp bfd all-interfaces
|
(Optional) Enables or disables BFD on all HSRP interfaces. The default is disabled.
|
Step 2
|
interface int-if
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 3
|
hsrp bfd
Example:
switch(config-if)# hsrp bfd
|
(Optional) Enables or disables BFD on an HSRP interface. The default is disabled.
|
Step 4
|
show running-config hsrp
Example:
switch(config-if)# show running-config
hsrp
|
(Optional) Displays the HSRP running configuration.
|
Step 5
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on VRRP
You can configure BFD for the Virtual Router Redundancy Protocol (VRRP). The active and standby VRRP routers track each other through BFD. If BFD on the standby VRRP router detects that the active VRRP router is down, the standby VRRP router treats this event as an active time rexpiry and takes over as the active VRRP router.
The show vrrp detail will show this event as BFD@Act-down or BFD@Sby-down.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Configure the BFD session parameters. See the "Configuring Global BFD Parameters" section or the "Configuring BFD on an Interface" section.
Enable the VRRP feature. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more information.
SUMMARY STEPS
1. configure terminal
2. interface int-if
3. vrrp group-no
4. vrrp bfd address
5. (Optional) show running-config vrrp
6. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
interface int-if
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 3
|
vrrp group-no
Example:
switch(config-if)# vrrp group-no
|
Specifies the VRRP group number.
|
Step 4
|
vrrp bfd address
Example:
switch(config-if)# vrrp bfd
|
Enables or disables BFD on an VRRP interface. The default is disabled.
|
Step 5
|
show running-config vrrp
Example:
switch(config-if)# show running-config
vrrp
|
(Optional) Displays the VRRP running configuration.
|
Step 6
|
copy running-config startup-config
Example:
switch(config-if)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on PIM
You can configure BFD for the Protocol Independent Multicast (PIM) protocol.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
Enable the PIM feature. See the Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide, for more information.
SUMMARY STEPS
1. configure terminal
2. ip pim bfd
3. interface if-type
4. (Optional) ip pim bfd-instance [disable]
5. (Optional) show running-config pim
6. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
ip pim bfd
Example:
switch(config)# ip pim bfd
|
Enables BFD for PIM.
|
Step 3
|
interface int-if
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
|
Enters interface configuration mode. Use the ? keyword to display the supported interfaces.
|
Step 4
|
ip pim bfd-instance [disable]
Example:
switch(config-if)# ip pim bfd-instance
|
(Optional) Enables or disables BFD on a PIM interface. The default is disabled.
|
Step 5
|
show running-config pim
Example:
switch(config)# show running-config pim
|
(Optional) Displays the PIM running configuration.
|
Step 6
|
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on Static Routes
You can configure BFD for static routes on an interface. You can optionally configure BFD on a static route within a virtual routing and forwarding (VRF) instance.
BEFORE YOU BEGIN
Ensure that you are in the correct VDC (or use the switchto vdc command).
Enable the BFD feature. See the "Enabling the BFD Feature" section.
SUMMARY STEPS
1. configure terminal
2. (Optional) vrf context vrf-name
3. ip route route interface if {nh-address | nh-prefix}
4. ip route static bfd interface {nh-address | nh-prefix}
5. (Optional) show ip route static [vrf vrf-name]
6. (Optional) copy running-config startup-config
DETAILED STEPS
| |
Command
|
Purpose
|
Step 1
|
configure terminal
Example:
switch# configure terminal
switch(config)#
|
Enters configuration mode.
|
Step 2
|
vrf context vrf-name
Example:
switch(config)# vrf context Red
switch(config-vrf)#
|
(Optional) Enters VRF configuration mode.
|
Step 3
|
ip route route interface {nh-address |
nh-prefix}
Example:
switch(config-vrf)# ip route 192.0.2.1
ethernet 2/1 192.0.2.4
|
Creates a static route Use the ? keyword to display the supported interfaces.
|
Step 4
|
ip route static bfd interface
{nh-address | nh-prefix}
Example:
switch(config-vrf)# ip route static bfd
ethernet 2/1 192.0.2.4
|
Enables BFD for all static routes on an interface. Use the ? keyword to display the supported interfaces.
|
Step 5
|
show ip route static[vrf vrf-name]
Example:
switch(config-vrf)# show ip route static
vrf Red
|
(Optional) Displays the static routes.
|
Step 6
|
copy running-config startup-config
Example:
switch(config-vrf)# copy running-config
startup-config
|
(Optional) Saves this configuration change.
|
Configuring BFD on MPLS TE Fast Reroute
MPLS Traffic Engineering (TE) uses BFD accelerate the detection of node failures and to provide fast forwarding path failure detection times. BFD for MPLS TE fast reroute is configured automatically when you enable the fast reroute on a tunnel. "See the Configuring MPLS TE Fast Reroute Link and Node Protection" chapter in the Cisco Nexus 7000 Series NX-OS MPLS Configuration Guide for more information.
Disabling BFD on an Interface
You can selectively disable BFD on an interface for a routing protocol that has BFD enabled at the global or VRF level.
To disable BFD on an interface, use one of the following commands in interface configuration mode:
Command
|
Purpose
|
ip eigrp instance-tag bfd disable
Example:
switch(config-if)# ip eigrp Test1 bfd
disable
|
Disables BFD on an EIGRP interface. The instance tag can be any case-sensitive, alphanumeric string up to 20 characters.
|
ip ospf bfd disable
Example:
switch(config-if)# ip ospf 201 bfd disable
|
Disables BFD on an OSPFv2 interface.
|
isis bfd disable
Example:
switch(config-if)# isis bfd disable
|
Disables BFD on an IS-IS interface.
|
Verifying the BFD Configuration
To display BFD configuration information, perform one of the following tasks:
Command
|
Purpose
|
show running-config bfd
|
Displays the running BFD configuration.
|
show startup-config bfd
|
Displays the BFD configuration that will be applied on the next system startup.
|
For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Interfaces Command Reference.
Monitoring BFD
Use the following commands to display BFD:
Command
|
Purpose
|
show bfd neighbors [application name] [details]
|
Displays information about BFD for a supported application, such as BGP or OSPFv2.
|
show bfd neighbors [interface int-if] [details]
|
Displays information about BGP sessions on an interface.
|
show bfd neighbors [dest-ip ip-address] [src-ip ip-address][details]
|
Displays information about the specified BGP session on an interface.
|
show bfd neighbors [vrf vrf-name] [details]
|
Displays information about BFD for a VRF.
|
For detailed information about the fields in the output from these commands, see the Cisco Nexus 7000 Series NX-OS Interfaces Command Reference.
Configuration Examples for BFD
The following example shows how to configure BFD for OSPFv2 on Ethernet 2/1, using the default BFD session parameters:
The following example shows how to configure BFD for all EIGRP interfaces, using the default BFD session parameters:
bfd interval 100 min_rx 100 multiplier 4
Additional References
For additional information related to implementing BFD, see the following sections:
•Related Documents
•RFCs
•Feature History for BFD
Related Documents
Related Topic
|
Document Title
|
BFD commands
|
See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x, for more information.
|
RFCs
RFC
|
Title
|
RFC 5880
|
Bidirectional Forwarding Detection (BFD)
|
RFC 5881
|
BFD for IPv4 and IPv6 (Single Hop)
|
Feature History for BFD
Table 5-2 lists the release history for this feature.
Table 5-2 Feature History for BFD
Feature Name
|
Releases
|
Feature Information
|
BFD
|
5.0(2)
|
This feature was introduced.
|
BFD Authentication
|
5.2(1)
|
Keyed SHA-1 authentication is supported on BFD packets.
|
BFD for VRRP
|
5.2(1)
|
Added support for BFD in VRRP.
|
BFD on M2 and F2 modules
|
6.1(1)
|
Added a note on M2 and F2 module support
|
Feedback
