Table Of Contents
Bidirectional Forwarding Detection
Prerequisites for Bidirectional Forwarding Detection
Restrictions for Bidirectional Forwarding Detection
Information About Bidirectional Forwarding Detection
BFD Support on Cisco 12000 Routers
Benefits of Using BFD for Failure Detection
How to Configure Bidirectional Forwarding Detection
Configuring BFD Session Parameters on the Interface
Configuring BFD Support for Routing Protocols
Configuring BFD Support for BGP
Configuring BFD Support for EIGRP
Configuring BFD Support for IS-IS
Configuring BFD Support for OSPF
Configuring BFD Support for HSRP
Configuring the BFD Slow Timer
Disabling BFD Echo Mode Without Asymmetry
Monitoring and Troubleshooting BFD
Monitoring and Troubleshooting BFD for Cisco 7600 Series Routers
Monitoring and Troubleshooting BFD for Cisco 12000 Series Routers
Monitoring and Troubleshooting BFD for Cisco 10720 Internet Routers
Configuration Examples for Bidirectional Forwarding Detection
Configuring BFD in an EIGRP Network with Echo Mode Enabled by Default: Example
Configuring BFD in an OSPF Network: Example
Configuring BFD in a BGP Network: Example
Configuring BFD in an IS-IS Network: Example
Configuring BFD in an HSRP Network: Example
Feature Information for Bidirectional Forwarding Detection
Bidirectional Forwarding Detection
This document describes how to enable the Bidirectional Forwarding Detection (BFD) protocol. BFD is a detection protocol designed to provide fast forwarding path failure detection times for all media types, encapsulations, topologies, and routing protocols. In addition to fast forwarding path failure detection, BFD provides a consistent failure detection method for network administrators. Because the network administrator can use BFD to detect forwarding path failures at a uniform rate, rather than the variable rates for different routing protocol hello mechanisms, network profiling and planning will be easier, and reconvergence time will be consistent and predictable.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Bidirectional Forwarding Detection" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•Prerequisites for Bidirectional Forwarding Detection
•Restrictions for Bidirectional Forwarding Detection
•Information About Bidirectional Forwarding Detection
•How to Configure Bidirectional Forwarding Detection
•Configuration Examples for Bidirectional Forwarding Detection
•Feature Information for Bidirectional Forwarding Detection
Prerequisites for Bidirectional Forwarding Detection
•Cisco Express Forwarding (CEF) and IP routing must be enabled on all participating routers.
•You must enable Cisco Parallel eXpress Forwarding (PXF) on the Cisco 10720 Internet router in order for BFD to operate properly. PXF is enabled by default and is generally not turned off.
•One of the IP routing protocols supported by BFD must be configured on the routers before BFD is deployed. You should implement fast convergence for the routing protocol that you are using. See the IP routing documentation for your version of Cisco IOS software for information on configuring fast convergence. See the "Restrictions for Bidirectional Forwarding Detection" section for more information on BFD routing protocol support in Cisco IOS software.
Restrictions for Bidirectional Forwarding Detection
•For the current Cisco implementation of BFD for Cisco IOS Releases 12.2(18)SXE, 12.0(31)S, 12.4(4)T, 12.0(32)S, 12.2(33)SRA, and 12.2(33)SRB, only asynchronous mode is supported. In asynchronous mode, either BFD peer can initiate a BFD session.
•For the current Cisco implementation of BFD for Cisco IOS Releases 12.2(18)SXE, 12.0(31)S, 12.4(4)T, 12.0(32)S, 12.2(33)SRA, and 12.2(33)SRB, BFD is supported only for IPv4 networks.
•For Cisco IOS Release 12.2(33)SRB, the Cisco implementation of BFD supports only the following routing protocols: BGP, EIGRP, IS-IS, and OSPF.
•For Cisco IOS Release 12.2(33)SRA, the Cisco implementation of BFD supports only the following routing protocols: BGP, IS-IS, and OSPF.
•For Cisco IOS Release 12.4(4)T, the Cisco implementation of BFD supports only the following routing protocols: Border Gateway Protocol (BGP), Enhanced Interior Gateway Routing Protocol (EIGRP), Intermediate System-to-Intermediate System (IS-IS), and Open Shortest Path First (OSPF).
•For Cisco IOS Release 12.4(11)T, the Cisco implementation of BFD introduced support for the Hot Standby Router Protocol (HSRP). BFD support is not available for all platforms and interfaces. In Cisco IOS Release 12.4(11)T, this feature was introduced on Cisco 7200 series, Cisco 7600 series, and Cisco 12000 series routers.
•For Cisco IOS Releases 12.0(31)S and 12.0(32)S, the Cisco implementation of BFD supports only the following routing protocols: BGP, IS-IS, and OSPF.
•For Cisco IOS Release 12.2(18)SXE, the Cisco implementation of BFD supports only the following routing protocols: EIGRP, IS-IS, and OSPF
•For Cisco IOS Release 12.2(18)SXH, the Cisco implementation of BFD supports the following routing protocols: BGP, EIGRP, IS-IS, and OSPF.
•BFD works only for directly connected neighbors. BFD neighbors must be no more than one IP hop away. Multihop configurations are not supported.
•BFD support is not available for all platforms and interfaces. To confirm BFD support for a specific platform or interface and obtain the most accurate platform and hardware restrictions, see the Cisco IOS software release notes for your software version.
•For the following Cisco IOS Releases, BFD on PortChannel is not a supported configuration: 12.2 SXH, 12.2 SXF, 12.2 SRC, and 12.2 SRB.
•On the Cisco 10720 Internet router, BFD is supported only on Fast Ethernet, Gigabit Ethernet, and RPR-IEEE interfaces. BFD is not supported on Spatial Reuse Protocol (SRP) and Packet-over-SONET (POS) interfaces.
•When you configure the BFD session parameters on a Cisco 10720 interface using the bfd command (in interface configuration mode), the minimum configurable time period supported for the milliseconds argument in both the interval milliseconds and min_rx milliseconds parameters is 50 milliseconds.
•A maximum of 100 BFD sessions are supported on the Cisco 10720 Internet router. When BFD tries to set up a connection between routing protocols and establish a 101th session between a Cisco 10720 Internet router and adjacent routers, the following error message is displayed:
00:01:24: %OSPF-5-ADJCHG: Process 100, Nbr 10.0.0.0 on RPR-IEEE1/1 from LOADING to FULL, Loading Done 00:01:24: %BFD-5-SESSIONLIMIT: Attempt to exceed session limit of 100 neighbors.•The Cisco 10720 Internet router does not support the following BFD features:
–Demand mode
–Echo packets
–BFD over IP Version 6
•On the Cisco 12000 series router, asymmetrical routing between peer devices may cause a BFD control packet to be received on a line card other than the line card that initiated the session. In this special case, the BFD session between the routing peers will not be established.
•A maximum 100 sessions per line card are supported for the distributed Cisco 12000 series Internet router. The minimum hello interval is 50 ms with up to three Max retries for a BFD control packet to be received from a remote system before a session with a neighbor is declared down.
Note For the most accurate platform and hardware restrictions, see the Cisco IOS software release notes for your software version.
Information About Bidirectional Forwarding Detection
Before you configure BFD, you should become familiar with the information in the following sections:
•Benefits of Using BFD for Failure Detection
BFD Operation
BFD provides a low-overhead, short-duration method of detecting failures in the forwarding path between two adjacent routers, including the interfaces, data links, and forwarding planes. BFD is a detection protocol that you enable at the interface and routing protocol levels. Cisco supports the BFD asynchronous mode, which depends on the sending of BFD control packets between two systems to activate and maintain BFD neighbor sessions between routers. Therefore, in order for a BFD session to be created, you must configure BFD on both systems (or BFD peers). Once BFD has been enabled on the interfaces and at the router level for the appropriate routing protocols, a BFD session is created, BFD timers are negotiated, and the BFD peers will begin to send BFD control packets to each other at the negotiated interval.
BFD provides fast BFD peer failure detection times independently of all media types, encapsulations, topologies, and routing protocols BGP, EIGRP, IS-IS, and OSPF. By sending rapid failure detection notices to the routing protocols in the local router to initiate the routing table recalculation process, BFD contributes to greatly reduced overall network convergence time. Figure 1 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 established (3).
Figure 1 Establishing a BFD Neighbor Relationship
Figure 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 will immediately start converging on it.
Figure 2 Tearing Down an OSPF Neighbor Relationship
BFD Detection of Failures
Once a BFD session has been established and timer negations are complete, BFD peers send BFD control packets that act in the same manner as an IGP hello protocol to detect liveliness, except at a more accelerated rate. The following information should be noted:
•BFD is a forwarding path failure detection protocol. BFD detects a failure, but the routing protocol must take action to bypass a failed peer.
•Typically, BFD can be used at any protocol layer. However, the Cisco implementation of BFD for Cisco IOS Releases 12.2(18)SXE, 12.0(31)S, and 12.4(4)T supports only Layer 3 clients, in particular, the BGP, EIGRP, IS-IS, and OSPF routing protocols.
•Cisco devices will use one BFD session for multiple client protocols in the Cisco implementation of BFD for Cisco IOS Releases 12.2(18)SXE, 12.0(31)S, and 12.4(4)T. For example, if a network is running OSPF and EIGRP across the same link to the same peer, only one BFD session will be established, and BFD will share session information with both routing protocols.
BFD Version Interoperability
Cisco IOS Release 12.4(9)T supports BFD Version 1 as well as BFD Version 0. All BFD sessions come up as Version 1 by default and will be interoperable with Version 0. The system automatically performs BFD version detection, and BFD sessions between neighbors will run in the highest common BFD version between neighbors. For example, of one BFD neighbor is running BFD Version 0 and the other BFD neighbor is running Version 1, the session will run BFD Version 0. The output from the show bfd neighbors [details] command will verify which BFD version a BFD neighbor is running.
See the "Configuring BFD in an EIGRP Network with Echo Mode Enabled by Default: Example" section for an example of BFD version detection.
BFD Support on Cisco 12000 Routers
The Cisco 12000 series routers support distributed BFD to take advantage of its distributed Route Processor (RP) and line card (LC) architecture. The BFD tasks will be divided and assigned to the BFD process on RP and LC as described in the following sections:
BFD Process on the RP
Client Interaction
The BFD process on the RP will handle the interaction with clients, which create and delete BFD sessions.
Session Management for BFD Process on the RP
The BFD RP process will primarily own all BFD sessions on the router. It will pass the session creation and deletion requests to the BFD processes on all LCs. BFD LC sessions will have no knowledge of sessions being added or deleted by the clients. Only the BFD RP process will send session addition and deletion commands to the BFD LC process.
Session Database Management
The BFD RP process will maintain a database of all the BFD sessions on the router. This database will contain only the minimum required information.
Process EXEC Commands
The BFD RP process services the BFD show commands.
BFD Process on the LC
Session Management for BFD Process on the LC
The BFD LC process manages sessions, adds and deletes commands from the BFD RP process, and creates and deletes new sessions based on the commands. In the event of transmit failure, receive failure, or session down detection, the LC BFD instance will immediately notify the BFD RP process. It will also update transmit and receive counters. The BFD session is maintained completely on the LC. BFD control packets are received and processed, as well as sent, from the LC itself.
Database Management
The BFD LC process maintains a database of all the BFD sessions hosted on the LC.
Receive and Transmit
The BFD LC process is responsible for transmitting and receiving BFD packets for the sessions on the LC.
Benefits of Using BFD for Failure Detection
When you deploy any feature, it is important to consider all the alternatives and be aware of any trade-offs being made.
The closest alternative to BFD in conventional EIGRP, IS-IS, and OSPF deployments is the use of modified failure detection mechanisms for EIGRP, IS-IS, and OSPF routing protocols.
If you set EIGRP hello and hold timers to their absolute minimums, the failure detection rate for EIGRP falls to within a one- to two-second range.
If you use fast hellos for either IS-IS or OSPF, these Interior Gateway Protocol (IGP) protocols reduce their failure detection mechanisms to a minimum of one second.
There are several advantages to implementing BFD over reduced timer mechanisms for routing protocols:
•Although reducing the EIGRP, IS-IS, and OSPF timers can result in minimum detection timer of one to two seconds, BFD can provide failure detection in less than one second.
•Because BFD is not tied to any particular routing protocol, it can be used as a generic and consistent failure detection mechanism for EIGRP, IS-IS, and OSPF.
•Because some parts of BFD can be distributed to the data plane, it can be less CPU-intensive than the reduced EIGRP, IS-IS, and OSPF timers, which exist wholly at the control plane.
How to Configure Bidirectional Forwarding Detection
You start a BFD process by configuring BFD on the interface. When the BFD process is started, no entries are created in the adjacency database, in other words, no BFD control packets are sent or received. BFD echo mode, which is supported in BFD Version 1 for Cisco IOS 12.4(9)T, is enabled by default. BFD echo packets are sent and received in addition to BFD control packets. The adjacency creation takes places once you have configured BFD support for the applicable routing protocols. This section contains the following procedures:
•Configuring BFD Session Parameters on the Interface (required)
•Configuring BFD Support for Routing Protocols (required)
•Configuring BFD Echo Mode (optional)
•Monitoring and Troubleshooting BFD (optional)
Configuring BFD Session Parameters on the Interface
The steps in this procedure show how to configure BFD on the interface by setting the baseline BFD session parameters on an interface. Repeat the steps in this procedure for each interface over which you want to run BFD sessions to BFD neighbors.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. bfd interval milliseconds min_rx milliseconds multiplier interval-multiplier
5. end
DETAILED STEPS
Configuring BFD Support for Routing Protocols
You can enable BFD support for routing protocols at the router level to enable BFD support globally for all interfaces or you can configure BFD on a per-interface basis at the interface level.
For Cisco IOS Release 12.2(18)SXE, you must configure BFD support for one or more of the following routing protocols: EIGRP, IS-IS, and OSPF.
For Cisco IOS Releases 12.2(33)SRA, you must configure BFD support for one or more of the following routing protocols: EIGRP, IS-IS, and OSPF.
For Cisco IOS Releases 12.2(33)SRB, you must configure BFD support for one or more of the following routing protocols: BGP, EIGRP, IS-IS, and OSPF.
For Cisco IOS Releases 12.0(31)S and 12.4(4)T, you must configure BFD support for one or more of the following routing protocols: BGP, IS-IS, and OSPF.
For Cisco IOS Release 12.0(32)S, for the Cisco 10720 platform, you must configure BFD for one or more of the following routing protocols: BGP, IS-IS, and OSPF.
For Cisco IOS Release 12.4(11)T, BFD support for HSRP was introduced.
This section describes the following procedures:
•Configuring BFD Support for BGP (optional)
•Configuring BFD Support for EIGRP (optional)
•Configuring BFD Support for IS-IS (optional)
•Configuring BFD Support for OSPF (optional)
•Configuring BFD Support for HSRP (optional)
Configuring BFD Support for BGP
This section describes the procedure for configuring BFD support for BGP, so that BGP is a registered protocol with BFD and will receive forwarding path detection failure messages from BFD.
Prerequisites
BGP must be running on all participating routers.
The baseline parameters for BFD sessions on the interfaces over which you want to run BFD sessions to BFD neighbors must be configured. See the "Configuring BFD Session Parameters on the Interface" section for more information.
SUMMARY STEPS
1. enable
2. configure terminal
3. router bgp as-tag
4. neighbor ip-address fall-over bfd
5. end
6. show bfd neighbors [details]
7. show ip bgp neighbor
DETAILED STEPS
What to Do Next
See the "Monitoring and Troubleshooting BFD" section for more information on monitoring and troubleshooting BFD. If you want to configure BFD support for another routing protocol, see the following sections:
•Configuring BFD Support for EIGRP
•Configuring BFD Support for IS-IS
•Configuring BFD Support for OSPF
•Configuring BFD Support for HSRP
Configuring BFD Support for EIGRP
This section describes the procedure for configuring BFD support for EIGRP, so that EIGRP is a registered protocol with BFD and will receive forwarding path detection failure messages from BFD. There are two methods for enabling BFD support for EIGRP:
•You can enable BFD for all of the interfaces for which EIGRP is routing by using the bfd all-interfaces command in router configuration mode.
•You can enable BFD for a subset of the interfaces for which EIGRP is routing by using the bfd interface type number command in router configuration mode.
Prerequisites
EIGRP must be running on all participating routers.
The baseline parameters for BFD sessions on the interfaces over which you want to run BFD sessions to BFD neighbors must be configured. See the "Configuring BFD Session Parameters on the Interface" section for more information.
Restrictions
BFD for EIGRP is not supported on the Cisco 12000 series routers for Cisco IOS Releases 12.0(31)S, 12.0(32)S, 12.4(4)T, and 12.2(33)SRA.
SUMMARY STEPS
1. enable
2. configure terminal
3. router eigrp as-number
4. log-adjacency-changes [detail]
5. bfd all-interfaces
or
bfd interface type number6. end
7. show bfd neighbors [details]
8. show ip eigrp interfaces [type number] [as-number] [detail]
DETAILED STEPS
What to Do Next
See the "Monitoring and Troubleshooting BFD" section for more information on monitoring and troubleshooting BFD. If you want to configure BFD support for another routing protocol, see the following sections:
•Configuring BFD Support for BGP
•Configuring BFD Support for IS-IS
•Configuring BFD Support for OSPF
•Configuring BFD Support for HSRP
Configuring BFD Support for IS-IS
This section describes the procedures for configuring BFD support for IS-IS, so that IS-IS is a registered protocol with BFD and will receive forwarding path detection failure messages from BFD. There are two methods for enabling BFD support for IS-IS:
•You can enable BFD for all of the interfaces for which IS-IS is routing by using the bfd all-interfaces command in router configuration mode. You can then disable BFD for one or more of those interfaces using the isis bfd disable command in interface configuration mode.
•You can enable BFD for a subset of the interfaces for which IS-IS is routing by using the isis bfd command in interface configuration mode.
To configure BFD support for IS-IS, perform the steps in one of the following sections:
•Configuring BFD Support for IS-IS for All Interfaces
•Configuring BFD Support for IS-IS for One or More Interfaces
Prerequisites
IS-IS must be running on all participating routers.
The baseline parameters for BFD sessions on the interfaces that you want to run BFD sessions to BFD neighbors over must be configured. See the "Configuring BFD Session Parameters on the Interface" section for more information.
Configuring BFD Support for IS-IS for All Interfaces
To configure BFD on all IS-IS interfaces, perform the steps in this section.
SUMMARY STEPS
1. enable
2. configure terminal
3. router isis area-tag
4. bfd all-interfaces
5. exit
6. interface type number
7. isis bfd [disable]
8. end
9. show bfd neighbors [details]
10. show clns interface
DETAILED STEPS
What to Do Next
See the "Monitoring and Troubleshooting BFD" section for more information on monitoring and troubleshooting BFD. If you want to configure only for a specific subset of interfaces, perform the tasks in the "Configuring BFD Support for IS-IS for One or More Interfaces" section.
Configuring BFD Support for IS-IS for One or More Interfaces
To configure BFD for only one or more IS-IS interfaces, perform the steps in this section.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. isis bfd [disable]
5. end
6. show bfd neighbors [details]
7. show clns interface
DETAILED STEPS
What to Do Next
See the "Monitoring and Troubleshooting BFD" section for more information on monitoring and maintaining BFD. If you want to configure BFD support for another routing protocol, see one of the following sections:
•Configuring BFD Support for BGP
•Configuring BFD Support for EIGRP
•Configuring BFD Support for OSPF
•Configuring BFD Support for HSRP
Configuring BFD Support for OSPF
This section describes the procedures for configuring BFD support for OSPF, so that OSPF is a registered protocol with BFD and will receive forwarding path detection failure messages from BFD. You can either configure BFD support for OSPF globally on all interfaces or configure it selectively on one or more interfaces.
There are two methods for enabling BFD support for OSPF:
•You can enable BFD for all of the interfaces for which OSPF is routing by using the bfd all-interfaces command in router configuration mode. You can disable BFD support on individual interfaces using the ip ospf bfd [disable] command in interface configuration mode.
•You can enable BFD for a subset of the interfaces for which OSPF is routing by using the ip ospf bfd command in interface configuration mode.
See the following sections for tasks for configuring BFD support for OSPF:
•Configuring BFD Support for OSPF for All Interfaces (optional)
•Configuring BFD Support for OSPF for One or More Interfaces (optional)
Configuring BFD Support for OSPF for All Interfaces
To configure BFD for all OSPF interfaces, perform the steps in this section.
If you do not want to configure BFD on all OSPF interfaces and would rather configure BFD support specifically for one or more interfaces, see the "Configuring BFD Support for OSPF for One or More Interfaces" section.
Prerequisites
OSPF must be running on all participating routers.
The baseline parameters for BFD sessions on the interfaces over which you want to run BFD sessions to BFD neighbors must be configured. See the "Configuring BFD Session Parameters on the Interface" section for more information.
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id
4. bfd all-interfaces
5. exit
6. interface name number
7. ip ospf bfd [disable]
8. end
9. show bfd neighbors [details]
10. show ip ospf
DETAILED STEPS
What to Do Next
See the "Monitoring and Troubleshooting BFD" section for more information on monitoring and troubleshooting BFD. If you want to configure BFD support for another routing protocol, see the following sections:
•Configuring BFD Support for BGP
•Configuring BFD Support for EIGRP
•Configuring BFD Support for IS-IS
•Configuring BFD Support for HSRP
Configuring BFD Support for OSPF for One or More Interfaces
To configure BFD on one or more OSPF interfaces, perform the steps in this section.
Prerequisites
OSPF must be running on all participating routers.
The baseline parameters for BFD sessions on the interfaces over which you want to run BFD sessions to BFD neighbors must be configured. See the "Configuring BFD Session Parameters on the Interface" section for more information.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type number
4. ip ospf bfd [disable]
5. end
6. show bfd neighbors [details]
7. show ip ospf
DETAILED STEPS
What to Do Next
See the "Monitoring and Troubleshooting BFD" section for more information on monitoring and troubleshooting BFD. If you want to configure BFD support for another routing protocol, see the following sections:
•Configuring BFD Support for BGP
•Configuring BFD Support for EIGRP
•Configuring BFD Support for IS-IS
•Configuring BFD Support for HSRP
Configuring BFD Support for HSRP
Perform this task to enable BFD support for Hot Standby Router Protocol (HSRP.) Repeat the steps in this procedure for each interface over which you want to run BFD sessions to HSRP peers.
HSRP supports BFD by default. If HSRP support for BFD has been manually disabled, you can reenable it at the router level to enable BFD support globally for all interfaces or on a per-interface basis at the interface level.
Prerequisites
•HSRP must be running on all participating routers.
•Cisco Express Forwarding (CEF) must be enabled.
SUMMARY STEPS
1. enable
2. configure terminal
3. ip cef [distributed]
4. interface type number
5. ip address ip-address mask
6. standby [group-number] ip [ip-address [secondary]]
7. standby bfd
8. exit
9. standby bfd all-interfaces
10. exit
11. show standby [neighbors]
DETAILED STEPS
What to Do Next
See the "Monitoring and Troubleshooting BFD" section for more information on monitoring and troubleshooting BFD. If you want to configure BFD support for another routing protocol, see the following sections:
•Configuring BFD Support for BGP
•Configuring BFD Support for EIGRP
•Configuring BFD Support for IS-IS
•Configuring BFD Support for OSPF
Configuring BFD Echo Mode
BFD echo mode is enabled by default, but you can disable it such that it can run independently in each direction. Before you configure echo mode you should be familiar with the following concepts:
BFD Echo Mode
Benefits of Running BFD Echo Mode
BFD echo mode works with asynchronous BFD. Echo packets are sent by the forwarding engine and forwarded back along the same path in order to perform detection—the BFD session at the other end does not participate in the actual forwarding of the echo packets. The echo function and the forwarding engine are responsible for the detection process, therefore the number of BFD control packets that are sent out between two BFD neighbors is reduced. And since the forwarding engine is testing the forwarding path on the remote (neighbor) system without involving the remote system, there is an opportunity to improve the interpacket delay variance, thereby achieving quicker failure detection times than when using BFD Version 0 with BFD control packets for the BFD session.
Echo Mode Without Asymmetry
Echo mode is described as without asymmetry when it is running on both sides (both BFD neighbors are running echo mode).
Prerequisites
BFD must be running on all participating routers.
Before using BFD echo mode, you must disable the sending of Internet Control Message Protocol (ICMP) redirect messages by entering the no ip redirects command, in order to avoid high CPU utilization.
The baseline parameters for BFD sessions on the interfaces over which you want to run BFD sessions to BFD neighbors must be configured. See the "Configuring BFD Session Parameters on the Interface" section for more information.
Restrictions
BFD echo mode which is supported in BFD Version 1, is available only in Cisco IOS Releases 12.4(9)T and 12.2(33)SRA.
This section contains the following configuration tasks for BFD echo mode:
•Configuring the BFD Slow Timer
•Disabling BFD Echo Mode Without Asymmetry
Configuring the BFD Slow Timer
The steps in this procedure show how to change the value of the BFD slow timer. Repeat the steps in this procedure for each BFD router.
SUMMARY STEPS
1. enable
2. configure terminal
3. bfd slow-timer milliseconds
4. end
DETAILED STEPS
Disabling BFD Echo Mode Without Asymmetry
The steps in this procedure show how to disable BFD echo mode without asymmetry —no echo packets will be sent by the router, and the router will not forward BFD echo packets that are received from any neighbor routers.
Repeat the steps in this procedure for each BFD router.
SUMMARY STEPS
1. enable
2. configure terminal
3. [no] bfd echo
4. bfd echo
5. end
DETAILED STEPS
Monitoring and Troubleshooting BFD
This section describes how to retrieve BFD information for maintenance and troubleshooting. The commands in these tasks can be entered as needed, in any order desired.
For more information about BFD session initiation and failure, refer to the "BFD Operation" section.
This section contains information for monitoring and troubleshooting BFD for the following Cisco platforms:
•Monitoring and Troubleshooting BFD for Cisco 7600 Series Routers
•Monitoring and Troubleshooting BFD for Cisco 12000 Series Routers
•Monitoring and Troubleshooting BFD for Cisco 10720 Internet Routers
Monitoring and Troubleshooting BFD for Cisco 7600 Series Routers
To monitor or troubleshoot BFD on Cisco 7600 series routers, perform one or more of the steps in this section.
SUMMARY STEPS
1. enable
2. show bfd neighbors [details]
3. debug bfd [packet | event]
DETAILED STEPS
Monitoring and Troubleshooting BFD for Cisco 12000 Series Routers
To monitor or troubleshoot BFD on Cisco 12000 series routers, perform one or more of the steps in this section.
SUMMARY STEPS
1. enable
2. attach slot-number
3. show bfd neighbors [details]
4. show monitor event-trace bfd [all]
5. debug bfd event
6. debug bfd packet
7. debug bfd ipc-error
8. debug bfd ipc-event
9. debug bfd oir-error
10. debug bfd oir-event
DETAILED STEPS
Monitoring and Troubleshooting BFD for Cisco 10720 Internet Routers
To monitor or troubleshoot BFD on Cisco 10720 Internet routers, perform one or more of the steps in this section.
SUMMARY STEPS
1. enable
2. show bfd neighbors [details]
3. debug bfd event
4. debug bfd packet
DETAILED STEPS
Configuration Examples for Bidirectional Forwarding Detection
This section provides the following configuration examples:
•Configuring BFD in an EIGRP Network with Echo Mode Enabled by Default: Example
•Configuring BFD in an OSPF Network: Example
•Configuring BFD in a BGP Network: Example
•Configuring BFD in an IS-IS Network: Example
•Configuring BFD in an HSRP Network: Example
Configuring BFD in an EIGRP Network with Echo Mode Enabled by Default: Example
12.4(9)T Example
In the following example, the EIGRP network contains RouterA, RouterB, and RouterC. Fast Ethernet interface 0/1 on RouterA is connected to the same network as FastEthernet interface 0/1 on Router B. Fast Ethernet interface 0/1 on RouterB is connected to the same network as Fast Ethernet interface 0/1 on RouterC.
RouterA and RouterB are running BFD Version 1 which supports echo mode, and RouterC is running BFD Version 0, which does not support echo mode. The BFD sessions between RouterC and its BFD neighbors are said to be running echo mode with asymmetry because echo mode will run on the forwarding path for RouteA and RouterB, and their echo packets will return along the same path to for BFD sessions and failure detections, while their BFD neighbor RouterC runs BFD Version 0 and uses BFD controls packets for BFD sessions and failure detections.
Figure 3 EIGRP Network with Three BFD Neighbors Running V1 or V0
Figure 3 shows a large EIGRP network with several routers, three of which are BFD neighbors that are running EIGRP as their routing protocol.
The example, starting in global configuration mode, shows the configuration of BFD.
Configuration for RouterA
interface FastEthernet0/0no shutdownip address 10.4.9.14 255.255.255.0duplex autospeed auto!interface FastEthernet0/1ip address 172.16.1.1 255.255.255.0bfd interval 50 min_rx 50 multiplier 3no shutdownduplex autospeed auto!router eigrp 11network 172.16.0.0bfd all-interfacesauto-summary!ip default-gateway 10.4.9.1ip default-network 0.0.0.0ip route 0.0.0.0 0.0.0.0 10.4.9.1ip route 171.16.1.129 255.255.255.255 10.4.9.1!no ip http server!logging alarm informational!control-plane!line con 0exec-timeout 30 0stopbits 1line aux 0stopbits 1line vty 0 4login!!endConfiguration for RouterB
!interface FastEthernet0/0no shutdownip address 10.4.9.34 255.255.255.0duplex autospeed auto!interface FastEthernet0/1ip address 172.16.1.2 255.255.255.0bfd interval 50 min_rx 50 multiplier 3no shtdownduplex autospeed auto!router eigrp 11network 172.16.0.0bfd all-interfacesauto-summary!ip default-gateway 10.4.9.1ip default-network 0.0.0.0ip route 0.0.0.0 0.0.0.0 10.4.9.1ip route 171.16.1.129 255.255.255.255 10.4.9.1!no ip http server!logging alarm informational!control-plane!line con 0exec-timeout 30 0stopbits 1line aux 0stopbits 1line vty 0 4login!!endConfiguration for RouterC
!!interface FastEthernet0/0no shutdownip address 10.4.9.34 255.255.255.0duplex autospeed auto!interface FastEthernet0/1ip address 172.16.1.2 255.255.255.0bfd interval 50 min_rx 50 multiplier 3no shutdownduplex autospeed auto!router eigrp 11network 172.16.0.0bfd all-interfacesauto-summary!ip default-gateway 10.4.9.1ip default-network 0.0.0.0ip route 0.0.0.0 0.0.0.0 10.4.9.1ip route 171.16.1.129 255.255.255.255 10.4.9.1!no ip http server!logging alarm informational!control-plane!line con 0exec-timeout 30 0stopbits 1line aux 0stopbits 1line vty 0 4login!!endThe output from the show bfd neighbors details command from RouterA verifies that BFD sessions have been created among all three routers and that EIGRP is registered for BFD support. The first group of output shows that RouterC with the IP address 172.16.1.3 runs BFD Version 0 and therefore does not use the echo mode. The second group of output shows that RouterB with the IP address 172.16.1.2 does run BFD Version 1, and the 50 millisecond BFD interval parameter had been adopted. The relevant command output is shown in bold in the output.
RouterARouterA# show bfd neighbors details
OurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int172.16.1.1 172.16.1.3 5/3 1(RH) 150 (3 ) Up Fa0/1Session state is UP and not using echo function.Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 50000, MinRxInt: 50000, Multiplier: 3Received MinRxInt: 50000, Received Multiplier: 3Holdown (hits): 150(0), Hello (hits): 50(1364284)Rx Count: 1351813, Rx Interval (ms) min/max/avg: 28/64/49 last: 4 ms agoTx Count: 1364289, Tx Interval (ms) min/max/avg: 40/68/49 last: 32 ms agoRegistered protocols: EIGRPUptime: 18:42:45Last packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 3 - Your Discr.: 5Min tx interval: 50000 - Min rx interval: 50000Min Echo interval: 0OurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int172.16.1.1 172.16.1.2 6/1 Up 0 (3 ) Up Fa0/1Session state is UP and using echo function with 50 ms interval.Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3Received MinRxInt: 1000000, Received Multiplier: 3Holdown (hits): 3000(0), Hello (hits): 1000(317)Rx Count: 305, Rx Interval (ms) min/max/avg: 1/1016/887 last: 448 ms agoTx Count: 319, Tx Interval (ms) min/max/avg: 1/1008/880 last: 532 ms agoRegistered protocols: EIGRPUptime: 00:04:30Last packet: Version: 1 - Diagnostic: 0State bit: Up - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 1 - Your Discr.: 6Min tx interval: 1000000 - Min rx interval: 1000000Min Echo interval: 50000The output from the show bfd neighbors details command on Router B verifies that BFD sessions have been created and that EIGRP is registered for BFD support. As previously noted, RouterA runs BFD Version 1, therefore echo mode is running, and RouterC runs BFD Version 0, so echo mode does not run. The relevant command output is shown in bold in the output.
Router BRouterB# show bfd neighbors details
OurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int172.16.1.2 172.16.1.1 1/6 Up 0 (3 ) Up Fa0/1Session state is UP and using echo function with 50 ms interval.Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3Received MinRxInt: 1000000, Received Multiplier: 3Holdown (hits): 3000(0), Hello (hits): 1000(337)Rx Count: 341, Rx Interval (ms) min/max/avg: 1/1008/882 last: 364 ms agoTx Count: 339, Tx Interval (ms) min/max/avg: 1/1016/886 last: 632 ms agoRegistered protocols: EIGRPUptime: 00:05:00Last packet: Version: 1 - Diagnostic: 0State bit: Up - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 6 - Your Discr.: 1Min tx interval: 1000000 - Min rx interval: 1000000Min Echo interval: 50000OurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int172.16.1.2 172.16.1.3 3/6 1(RH) 118 (3 ) Up Fa0/1Session state is UP and not using echo function.Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 50000, MinRxInt: 50000, Multiplier: 3Received MinRxInt: 50000, Received Multiplier: 3Holdown (hits): 150(0), Hello (hits): 50(5735)Rx Count: 5731, Rx Interval (ms) min/max/avg: 32/72/49 last: 32 ms agoTx Count: 5740, Tx Interval (ms) min/max/avg: 40/64/50 last: 44 ms agoRegistered protocols: EIGRPUptime: 00:04:45Last packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 6 - Your Discr.: 3Min tx interval: 50000 - Min rx interval: 50000Min Echo interval: 0Figure 4
Fast Ethernet interface 0/1 Failure
Figure 4 shows a that Fast Ethernet interface 0/1 on RouterB has failed. Without this neighbor, there is no way to reach the network beyond RouterB.
When Fast Ethernet interface 0/1 on RouterB fails, BFD will no longer detect Router B as a BFD neighbor for RouterA or for RouterC. In this example, Fast Ethernet interface 0/1 has been administratively shut down on RouterB.
The following output from the show bfd neighbors command on RouterA now shows only one BFD neighbor for RouterA in the EIGRP network. The relevant command output is shown in bold in the output.
RouterA# show bfd neighborsOurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int172.16.1.1 172.16.1.3 5/3 1(RH) 134 (3 ) Up Fa0/1The following output from the show bfd neighbors command on RouterC also now shows only one BFD neighbor for RouterC in the EIGRP network. The relevant command output is shown in bold in the output.
RouterC# show bfd neighborsOurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.1.3 172.16.1.1 3/5 1 114 (3 ) Up Fa0/1Configuring BFD in an OSPF Network: Example
12.0(31)S
In the following example, the simple OSPF network consists of Router A and Router B. Fast Ethernet interface 0/1 on Router A is connected to the same network as Fast Ethernet interface 6/0 in Router B. The example, starting in global configuration mode, shows the configuration of BFD. For both Routers A and B, BFD is configured globally for all interfaces associated with the OSPF process.
Configuration for Router A
!interface FastEthernet 0/1ip address 172.16.10.1 255.255.255.0bfd interval 50 min_rx 50 multiplier 3!interface FastEthernet 3/0.1ip address 172.17.0.1 255.255.255.0!router ospf 123log-adjacency-changes detailnetwork 172.16.0.0 0.0.0.255 area 0network 172.17.0.0 0.0.0.255 area 0bfd all-interfacesConfiguration for Router B
!interface FastEthernet 6/0ip address 172.16.10.2 255.255.255.0bfd interval 50 min_rx 50 multiplier 3!interface FastEthernet 6/1ip address 172.18.0.1 255.255.255.0!router ospf 123log-adjacency-changes detailnetwork 172.16.0.0 0.0.255.255 area 0network 172.18.0.0 0.0.255.255 area 0bfd all-interfacesThe output from the show bfd neighbors details command verifies that a BFD session has been created and that OSPF is registered for BFD support. The relevant command output is shown in bold in the output.
Router ARouterA# show bfd neighbors details
OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.1 172.16.10.2 1/2 1 532 (3 ) Up Fa0/1Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 200000, MinRxInt: 200000, Multiplier: 5Received MinRxInt: 1000, Received Multiplier: 3Holdown (hits): 600(22), Hello (hits): 200(84453)Rx Count: 49824, Rx Interval (ms) min/max/avg: 208/440/332 last: 68 ms agoTx Count: 84488, Tx Interval (ms) min/max/avg: 152/248/196 last: 192 ms agoRegistered protocols: OSPF
Uptime: 02:18:49Last packet: Version: 0 - Diagnostic: 0
I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 2 - Your Discr.: 1Min tx interval: 50000 - Min rx interval: 1000Min Echo interval: 0The output from the show bfd neighbors details command from the line card on Router B verifies that a BFD session has been created:
Note Router B is a Cisco 12000 series router. The show bfd neighbors details command must be run on the line cards. The show bfd neighbors details command will not display the registered protocols when it is entered on a line card.
Router BRouterB# attach 6
Entering Console for 8 Port Fast Ethernet in Slot: 6Type "exit" to end this sessionPress RETURN to get started!LC-Slot6> show bfd neighbors details
Cleanup timer hits: 0OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.2 172.16.10.1 8/1 1 1000 (5 ) Up Fa6/0Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 50000, MinRxInt: 1000, Multiplier: 3Received MinRxInt: 200000, Received Multiplier: 5Holdown (hits): 1000(0), Hello (hits): 200(5995)Rx Count: 10126, Rx Interval (ms) min/max/avg: 152/248/196 last: 0 ms agoTx Count: 5998, Tx Interval (ms) min/max/avg: 204/440/332 last: 12 ms agoLast packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 5 - Length: 24My Discr.: 1 - Your Discr.: 8Min tx interval: 200000 - Min rx interval: 200000Min Echo interval: 0Uptime: 00:33:13SSO Cleanup Timer called: 0SSO Cleanup Action Taken: 0Pseudo pre-emptive process count: 239103 min/max/avg: 8/16/8 last: 0 ms agoIPC Tx Failure Count: 0IPC Rx Failure Count: 0Total Adjs Found: 1The output of the show ip ospf command verifies that BFD has been enabled for OSPF. The relevant command output is shown in bold in the output.
Router A
RouterA# show ip ospf
Routing Process "ospf 123" with ID 172.16.10.1Supports only single TOS(TOS0) routesSupports opaque LSASupports Link-local Signaling (LLS)Initial SPF schedule delay 5000 msecsMinimum hold time between two consecutive SPFs 10000 msecsMaximum wait time between two consecutive SPFs 10000 msecsIncremental-SPF disabledMinimum LSA interval 5 secsMinimum LSA arrival 1000 msecsLSA group pacing timer 240 secsInterface flood pacing timer 33 msecsRetransmission pacing timer 66 msecsNumber of external LSA 0. Checksum Sum 0x000000Number of opaque AS LSA 0. Checksum Sum 0x000000Number of DCbitless external and opaque AS LSA 0Number of DoNotAge external and opaque AS LSA 0Number of areas in this router is 1. 1 normal 0 stub 0 nssaExternal flood list length 0BFD is enabled
Area BACKBONE(0)Number of interfaces in this area is 2 (1 loopback)Area has no authenticationSPF algorithm last executed 00:00:08.828 agoSPF algorithm executed 9 timesArea ranges areNumber of LSA 3. Checksum Sum 0x028417Number of opaque link LSA 0. Checksum Sum 0x000000Number of DCbitless LSA 0Number of indication LSA 0Number of DoNotAge LSA 0Flood list length 0Router B
RouterB# show ip ospfRouting Process "ospf 123" with ID 172.18.0.1Supports only single TOS(TOS0) routesSupports opaque LSASupports Link-local Signaling (LLS)Supports area transit capabilityInitial SPF schedule delay 5000 msecsMinimum hold time between two consecutive SPFs 10000 msecsMaximum wait time between two consecutive SPFs 10000 msecsIncremental-SPF disabledMinimum LSA interval 5 secsMinimum LSA arrival 1000 msecsLSA group pacing timer 240 secsInterface flood pacing timer 33 msecsRetransmission pacing timer 66 msecsNumber of external LSA 0. Checksum Sum 0x0Number of opaque AS LSA 0. Checksum Sum 0x0Number of DCbitless external and opaque AS LSA 0Number of DoNotAge external and opaque AS LSA 0Number of areas in this router is 1. 1 normal 0 stub 0 nssaNumber of areas transit capable is 0External flood list length 0BFD is enabled
Area BACKBONE(0)Number of interfaces in this area is 2 (1 loopback)Area has no authenticationSPF algorithm last executed 02:07:30.932 agoSPF algorithm executed 7 timesArea ranges areNumber of LSA 3. Checksum Sum 0x28417Number of opaque link LSA 0. Checksum Sum 0x0Number of DCbitless LSA 0Number of indication LSA 0Number of DoNotAge LSA 0Flood list length 0The output of the show ip ospf interface command verifies that BFD has been enabled for OSPF on the interfaces connecting Router A and Router B. The relevant command output is shown in bold in the output.
Router A
RouterA# show ip ospf interface fastethernet 0/1show ip ospf interface fastethernet 0/1FastEthernet0/1 is up, line protocol is upInternet Address 172.16.10.1/24, Area 0Process ID 123, Router ID 172.16.10.1, Network Type BROADCAST, Cost: 1Transmit Delay is 1 sec, State BDR, Priority 1, BFD enabledDesignated Router (ID) 172.18.0.1, Interface address 172.16.10.2Backup Designated router (ID) 172.16.10.1, Interface address 172.16.10.1Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5oob-resync timeout 40Hello due in 00:00:03Supports Link-local Signaling (LLS)Index 1/1, flood queue length 0Next 0x0(0)/0x0(0)Last flood scan length is 1, maximum is 1Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 1, Adjacent neighbor count is 1Adjacent with neighbor 172.18.0.1 (Designated Router)Suppress hello for 0 neighbor(s)Router B
RouterB# show ip ospf interface fastethernet 6/1
FastEthernet6/1 is up, line protocol is upInternet Address 172.18.0.1/24, Area 0Process ID 123, Router ID 172.18.0.1, Network Type BROADCAST, Cost: 1Transmit Delay is 1 sec, State DR, Priority 1, BFD enabledDesignated Router (ID) 172.18.0.1, Interface address 172.18.0.1No backup designated router on this networkTimer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5oob-resync timeout 40Hello due in 00:00:01Supports Link-local Signaling (LLS)Index 1/1, flood queue length 0Next 0x0(0)/0x0(0)Last flood scan length is 0, maximum is 0Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 0, Adjacent neighbor count is 0Suppress hello for 0 neighbor(s)Configuring BFD in a BGP Network: Example
12.0(31)S
In the following example, the simple BGP network consists of Router A and Router B. Fast Ethernet interface 0/1 on Router A is connected to the same network as Fast Ethernet interface 6/0 in Router B. The example, starting in global configuration mode, shows the configuration of BFD.
Configuration for Router A
!interface FastEthernet 0/1ip address 172.16.10.1 255.255.255.0bfd interval 50 min_rx 50 multiplier 3!interface FastEthernet 3/0.1ip address 172.17.0.1 255.255.255.0!!router bgp 40000bgp log-neighbor-changesneighbor 172.16.10.2 remote-as 45000neighbor 172.16.10.2 fall-over bfd!address-family ipv4neighbor 172.16.10.2 activateno auto-summaryno synchronizationnetwork 172.18.0.0 mask 255.255.255.0exit-address-family!Configuration for Router B
!interface FastEthernet 6/0ip address 172.16.10.2 255.255.255.0bfd interval 50 min_rx 50 multiplier 3!interface FastEthernet 6/1ip address 172.18.0.1 255.255.255.0!router bgp 45000bgp log-neighbor-changesneighbor 172.16.10.1 remote-as 40000neighbor 172.16.10.1 fall-over bfd!address-family ipv4neighbor 172.16.10.1 activateno auto-summaryno synchronizationnetwork 172.17.0.0 mask 255.255.255.0exit-address-family!The output from the show bfd neighbors details command from Router A verifies that a BFD session has been created and that BGP is registered for BFD support. The relevant command output is shown in bold in the output.
Router ARouterA# show bfd neighbors details
OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.1 172.16.10.2 1/8 1 332 (3 ) Up Fa0/1Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 200000, MinRxInt: 200000, Multiplier: 5Received MinRxInt: 1000, Received Multiplier: 3Holdown (hits): 600(0), Hello (hits): 200(15491)Rx Count: 9160, Rx Interval (ms) min/max/avg: 200/440/332 last: 268 ms agoTx Count: 15494, Tx Interval (ms) min/max/avg: 152/248/197 last: 32 ms agoRegistered protocols: BGPUptime: 00:50:45Last packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 8 - Your Discr.: 1Min tx interval: 50000 - Min rx interval: 1000Min Echo interval: 0The output from the show bfd neighbors details command from the line card on Router B verifies that a BFD session has been created:
Note Router B is a Cisco 12000 series router. The show bfd neighbors details command must be run on the line cards. The show bfd neighbors details command will not display the registered protocols when it is entered on a line card.
Router BRouterB# attach 6
Entering Console for 8 Port Fast Ethernet in Slot: 6Type "exit" to end this sessionPress RETURN to get started!LC-Slot6> show bfd neighbors details
Cleanup timer hits: 0OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.2 172.16.10.1 8/1 1 1000 (5 ) Up Fa6/0Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 50000, MinRxInt: 1000, Multiplier: 3Received MinRxInt: 200000, Received Multiplier: 5Holdown (hits): 1000(0), Hello (hits): 200(5995)Rx Count: 10126, Rx Interval (ms) min/max/avg: 152/248/196 last: 0 ms agoTx Count: 5998, Tx Interval (ms) min/max/avg: 204/440/332 last: 12 ms agoLast packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 5 - Length: 24My Discr.: 1 - Your Discr.: 8Min tx interval: 200000 - Min rx interval: 200000Min Echo interval: 0Uptime: 00:33:13SSO Cleanup Timer called: 0SSO Cleanup Action Taken: 0Pseudo pre-emptive process count: 239103 min/max/avg: 8/16/8 last: 0 ms agoIPC Tx Failure Count: 0IPC Rx Failure Count: 0Total Adjs Found: 1The output of the show ip bgp neighbors command verifies that BFD has been enabled for the BGP neighbors:
Router A
RouterA# show ip bgp neighbors
BGP neighbor is 172.16.10.2, remote AS 45000, external linkUsing BFD to detect fast fallover...Router B
RouterB# show ip bgp neighbors
BGP neighbor is 172.16.10.1, remote AS 40000, external linkUsing BFD to detect fast fallover...Configuring BFD in an IS-IS Network: Example
12.0(31)S
In the following example, the simple IS-IS network consists of Router A and Router B. Fast Ethernet interface 0/1 on Router A is connected to the same network as Fast Ethernet interface 6/0 for Router B. The example, starting in global configuration mode, shows the configuration of BFD.
Configuration for Router A
!interface FastEthernet 0/1ip address 172.16.10.1 255.255.255.0ip router isisbfd interval 50 min_rx 50 multiplier 3!interface FastEthernet 3/0.1ip address 172.17.0.1 255.255.255.0ip router isis!router isisnet 49.0001.1720.1600.1001.00bfd all-interfaces!Configuration for Router B
!interface FastEthernet 6/0ip address 172.16.10.2 255.255.255.0ip router isisbfd interval 50 min_rx 50 multiplier 3!interface FastEthernet 6/1ip address 172.18.0.1 255.255.255.0ip router isis!router isisnet 49.0000.0000.0002.00bfd all-interfaces!The output from the show bfd neighbors details command from Router A verifies that a BFD session has been created and that IS-IS is registered for BFD support:
Router ARouterA# show bfd neighbors details
OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.1 172.16.10.2 1/8 1 536 (3 ) Up Fa0/1Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 200000, MinRxInt: 200000, Multiplier: 5Received MinRxInt: 1000, Received Multiplier: 3Holdown (hits): 600(0), Hello (hits): 200(23543)Rx Count: 13877, Rx Interval (ms) min/max/avg: 200/448/335 last: 64 ms agoTx Count: 23546, Tx Interval (ms) min/max/avg: 152/248/196 last: 32 ms agoRegistered protocols: ISISUptime: 01:17:09Last packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 3 - Length: 24My Discr.: 8 - Your Discr.: 1Min tx interval: 50000 - Min rx interval: 1000Min Echo interval: 0The output from the show bfd neighbors details command from the line card on Router B verifies that a BFD session has been created:
Note Router B is a Cisco 12000 series router. The show bfd neighbors details command must be run on the line cards. The show bfd neighbors details command will not display the registered protocols when it is entered on a line card.
Router BRouterB# attach 6
Entering Console for 8 Port Fast Ethernet in Slot: 6Type "exit" to end this sessionPress RETURN to get started!LC-Slot6> show bfd neighbors details
Cleanup timer hits: 0OurAddr NeighAddr LD/RD RH Holdown(mult) State Int172.16.10.2 172.16.10.1 8/1 1 1000 (5 ) Up Fa6/0Local Diag: 0, Demand mode: 0, Poll bit: 0MinTxInt: 50000, MinRxInt: 1000, Multiplier: 3Received MinRxInt: 200000, Received Multiplier: 5Holdown (hits): 1000(0), Hello (hits): 200(5995)Rx Count: 10126, Rx Interval (ms) min/max/avg: 152/248/196 last: 0 ms agoTx Count: 5998, Tx Interval (ms) min/max/avg: 204/440/332 last: 12 ms agoLast packet: Version: 0 - Diagnostic: 0I Hear You bit: 1 - Demand bit: 0Poll bit: 0 - Final bit: 0Multiplier: 5 - Length: 24My Discr.: 1 - Your Discr.: 8Min tx interval: 200000 - Min rx interval: 200000Min Echo interval: 0Uptime: 00:33:13SSO Cleanup Timer called: 0SSO Cleanup Action Taken: 0Pseudo pre-emptive process count: 239103 min/max/avg: 8/16/8 last: 0 ms agoIPC Tx Failure Count: 0IPC Rx Failure Count: 0Total Adjs Found: 1Configuring BFD in an HSRP Network: Example
In the following example, the HSRP network consists of Router A and Router B. Fast Ethernet interface 2/0 on Router A is connected to the same network as Fast Ethernet interface 2/0 on Router B. The example, starting in global configuration mode, shows the configuration of BFD.
Note In the following example, the standby bfd and the standby bfd all-interfaces commands are not displayed. HSRP support for BFD peering is enabled by default when BFD is configured on the router or interface using the bfd interval command. The standby bfd and standby bfd all-interfaces commands are needed only if BFD has been manually disabled on a router or interface.
Router A
ip cefinterface FastEthernet2/0no shutdownip address 10.0.0.2 255.0.0.0ip router-cache cefbfd interval 200 min_rx 200 multiplier 3standby 1 ip 10.0.0.11standby 1 preemptstandby 1 priority 110standby 2 ip 10.0.0.12standby 2 preemptstandby 2 priority 110Router B
interface FastEthernet2/0ip address 10.1.0.22 255.255.0.0no shutdownbfd interval 200 min_rx 200 multiplier 3standby 1 ip 10.0.0.11standby 1 preemptstandby 1 priority 90standby 2 ip 10.0.0.12standby 2 preemptstandby 2 priority 80The output from the show standby neighbors command verifies that a BFD session has been created:
RouterA# show standby neighborsHSRP neighbors on FastEthernet2/010.1.0.22No active groupsStandby groups: 1BFD enabled !RouterB# show standby neighborsHSRP neighbors on FastEthernet2/010.0.0.2Active groups: 1No standby groupsBFD enabled !Additional References
The following sections provide references related to the BFD feature.
Related Documents
Related Topic Document TitleConfiguring and monitoring BGP
"BGP" module of the Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
Configuring and monitoring EIGRP
"EIGRP" module of the Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
Configuring and monitoring IS-IS
"Configuring Integrated IS-IS" module of the Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
Configuring and monitoring OSPF
"OSPF" module of the Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
Configuring and monitoring HSRP
"Configuring HSRP" module of the Cisco IOS IP Application Services Configuration Guide, Release 12.4T
BFD commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
•"IP Routing Protocol-Independent Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.4T
•"IP Routing Protocol-Independent Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SR
•"IP Routing Protocol-Independent Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SX
BGP commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
•"BGP Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.4T
•"BGP Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SR
•"BGP Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SX
EIGRP commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
•"EIGRP Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.4T
•"EIGRP Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SR
•"EIGRP Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SX
IS-IS commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
•"Integrated IS-IS Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.4T
•"Integrated IS-IS Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SR
•"Integrated IS-IS Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SX
OSPF commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
•"OSPF Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.4T
•"OSPF Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SR
•"OSPF Commands" chapter of the Cisco IOS IP Routing Protocols Command Reference, Release 12.2SX
Standards
MIBs
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for Bidirectional Forwarding Detection
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Glossary
BFD—Bidirectional Forwarding Detection. A detection protocol designed to provide fast failure detection times for all media types, encapsulations, topologies, and routing protocols.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2004-2007 Cisco Systems, Inc. All rights reserved.