IP Routing: BGP Configuration Guide
- BGP Support & Downloads for BFD [Cisco ASR 1000 Series Aggregation Services Routers] - Cisco
IP Routing: BGP Configuration Guide
Book Contents
Book Contents
Available Languages
Download Options
Book Title
IP Routing: BGP Configuration Guide
Chapter Title
BGP Support for BFD
View with Adobe Reader on a variety of devices
Chapter: BGP Support for BFD
Chapter Contents
BGP Support for BFD
Bidirectional Forwarding Detection (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. The main benefit of implementing BFD for BGP is a significantly faster reconvergence time.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see
and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
. An account on Cisco.com is not required.
Information About BGP Support for BFDBFD for BGP
Bidirectional Forwarding Detection (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. The main benefit of implementing BFD for BGP is a marked decrease in reconvergence time.
See also the “Configuring BGP Neighbor Session Options” chapter, the section “Configuring BFD for BGP IPv6 Neighbors.”
For more details about BFD, see the
Cisco IOS IP Routing: BFD Configuration Guide.
How to Decrease BGP Convergence Time Using BFDPrerequisites
Cisco Express Forwarding (CEF) and IP routing must be enabled on all participating routers.
BGP 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.
Restrictions
For the Cisco
implementation of BFD Support for BGP in Cisco IOS Release15.1(1)SG, only
asynchronous mode is supported. In asynchronous mode, either BFD peer can
initiate a BFD session.
IPv6 encapsulation
is supported.
BFD multihop is
supported.
Decreasing BGP Convergence Time Using BFD
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. The adjacency creation takes places once you have configured BFD support for the applicable routing protocols. The first two tasks must be configured to implement BFD support for BGP to reduce the BGP convergence time. The third task is an optional task to help monitor or troubleshoot BFD.
See also the “Configuring BFD for BGP IPv6 Neighbors” section in the “Configuring BGP Neighbor Session Options” module.
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 STEPS1.
milliseconds
milliseconds
multiplier
interval-multiplier
DETAILED STEPS Command or ActionPurposeStep 1
Router& enable
Enables privileged EXEC mode.
Enter your password if prompted.
Router# configure terminal
Enters global configuration mode.
Router(config)# interface FastEthernet 6/0
Enters interface configuration mode.
milliseconds
milliseconds
multiplier
interval-multiplier
Router(config-if)# bfd interval 50 min_rx 50 multiplier 5
Enables BFD on the interface.
Router(config-if)# end
Exits interface configuration mode.
Configuring BFD Support for BGP
Perform this task to configure BFD support for BGP, so that BGP is a registered protocol with BFD and will receive forwarding path detection failure messages from BFD.
Before You Begin
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 "Configuring BFD Session Parameters on the Interface" for more information.
SUMMARY STEPS1.
autonomous-system-number
ip-address
[ip-address
[received-routes |
advertised-routes |
paths [regexp] |
dampened-routes |
flap-statistics |
prefix-filter |
policy [detail]]]
DETAILED STEPS Command or ActionPurposeStep 1
Router& enable
Enables privileged EXEC mode.
Enter your password if prompted.
Router# configure terminal
Enters global configuration mode.
autonomous-system-number
Router(config)# router bgp tag1
Specifies a BGP process and enters router configuration mode.
ip-address
Router(config-router)# neighbor 172.16.10.2 fall-over bfd
Enables BFD support for fallover.
Router(config-router)# end
Returns the router to privileged EXEC mode.
Router# show bfd neighbors detail
Verifies that the BFD neighbor is active and displays the routing protocols that BFD has registered.
[ip-address
[received-routes |
advertised-routes |
paths [regexp] |
dampened-routes |
flap-statistics |
prefix-filter |
policy [detail]]]
Router# show ip bgp neighbors
Displays information about BGP and TCP connections to neighbors.
Monitoring and Troubleshooting BFD
To monitor or troubleshoot BFD, perform one or more of the steps in this section.
SUMMARY STEPS1.
ipc-error |
ipc-event |
oir-error |
oir-event]
DETAILED STEPS Command or ActionPurposeStep 1
Router& enable
Enables privileged EXEC mode.
Enter your password if prompted.
Router# show bfd neighbors details
(Optional) Displays the BFD adjacency database.
details keyword shows all BFD protocol parameters and timers per neighbor.
ipc-error |
ipc-event |
oir-error |
oir-event]
Router# debug bfd packet
(Optional) Displays debugging information about BFD packets.
Additional References
Related Documents
Related Topic
Document Title
Technical Assistance
Description
Feature Information for BGP
Support for BFD
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to . An account on Cisco.com is not required.
Table 1 Feature Information for BGP
Support for BFD
Feature Name
Information
Was this Document Helpful?
Contact Cisco
(Requires a )
Related Support Community Discussions验证在DFC线路卡的BFD硬件计数器7600个设备的 - Cisco
验证在DFC线路卡的BFD硬件计数器7600个设备的
(152.1 KB)
在各种设备上使用 Adobe Reader 查看
在 iPhone、iPad、Android、Sony Reader 或 Windows Phone 上使用各种应用查看
在 Kindle 设备上查看或在多个设备上使用 Kindle 应用查看
文档 ID:211272
关于此翻译
思科采用人工翻译与机器翻译相结合的方式将此文档翻译成不同语言，希望全球的用户都能通过各自的语言得到支持性的内容。
请注意：即使是最好的机器翻译，其准确度也不及专业翻译人员的水平。
Cisco Systems, Inc. 对于翻译的准确性不承担任何责任，并建议您总是参考英文原始文档（已提供链接）。
本文描述如何验证在分布式转发卡(DFC)线路卡的Bidireccional转发检测(BFD)硬件计数器7600个设备的。
Cisco 建议您具有以下主题的基础知识：
7600系列路由器配置和功能
DFC线路卡模块配置
使用的组件
本文档中的信息根据7600&IOS版本15.3。
&本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始（默认）配置。如果您使用的是真实网络，请确保您已经了解所有命令的潜在影响。
BFD是设计的网络协议检测通信的分秒的失败在任何系统(直接物理链路、虚拟电路、通道、MPLS LSP等等)之间的路径。
DFC代表DFC， DFC和CFC线路卡之间的主要区别是DFC线路卡有一个嵌入式子卡用L2引擎和L3/4引擎，这卸载在CFC线路卡将发送到在线路卡将执行的本地Supervisor的转发查找。
BFD数据包在硬件方面被对待方式他们不影响CPU，这意味着在此DFC的卡数据包总是接收并且转发，无需留下线路卡。
R1(Te3/21)---------R2
故障排除方法
您能看到R1不启动与他的邻居的BFD邻接Tengig3/21的。
检查邻接详细资料：
R1# sh bfd nei detIPv4 SessionsNeighAddr&&&&&&&&&&&&&&&&&&&&&&&&&&&&& LD/RD&&&&&&&& RH/RS&&&& State&&&& Int172.31.11.34&&&&&&&&&&&&&&&&&&&&&&&&&&& 1/0&&&&&&&&& Down&&&&& Down&&&&& Te3/21Session Host: HardwareOurAddr: 172.31.11.33&&Handle: 1Local Diag: 1, Demand mode: 0, Poll bit: 0MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 5Received MinRxInt: 200000, Received Multiplier: 5Holddown (hits): 0(0), Hello (hits): 1000(0)Rx Count: 37&& ssNotice received packets are too lowTx Count: 9401Elapsed time watermarks: 0 0 (last: 0)Registered protocols: ISIS CEFDowntime: 02:36:34Last packet: Version: 1&&&&&&&&&&&&&&&&& - Diagnostic: 0&&&&&&&&&&&& State bit: Up&&&&&&&&&&&&&& - Demand bit: 0&&&&&&&&&& &&Poll bit: 0&&&&&&&&&&&&&&&& - Final bit: 0&&&&&&&&&&&& C bit: 1&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& Multiplier: 5&&&&&&&&&&&&&& - Length: 24&&&&&&&&&&&& My Discr.: 77&&&&&&&&&&&&&& - Your Discr.: 1&&&&&&&&&&&& Min tx interval: 200000&&&& - Min rx interval: 200000&&&&&&&&&&&& Min Echo interval: 0&&&&&&R1# sh bfd nei detIPv4 SessionsNeighAddr&&&&&&&&&&&&&&&&&&&&&&&&&&&&& LD/RD&&&&&&&& RH/RS&&&& State&&&& Int172.31.11.34&&&&&&&&&&&&&&&&&&&&&&&&&&& 1/0&&&&&&&&& Down&&&&& Down&&&&& Te3/21Session Host: HardwareOurAddr: 172.31.11.33&&Handle: 1Local Diag: 1, Demand mode: 0, Poll bit: 0MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 5Received MinRxInt: 200000, Received Multiplier: 5Holddown (hits): 0(0), Hello (hits): 1000(0)Rx Count: 37&& ss--------------------------------------------------Notice received packets are not incrementingTx Count: 9456 ss-------------------------------------------------- Transmit packets are incrementingElapsed time watermarks: 0 0 (last: 0)Registered protocols: ISIS CEFDowntime: 02:36:34Last packet: Version: 1&&&&&&&&&&&&&&&&& - Diagnostic: 0&&&&&&&&&&&& State bit: Up&&&&&&&&&&&&&& - Demand bit: 0&&&&&&&&&&&& Poll bit: 0&&&&&&&&&&&&&&&& - Final bit: 0&&&&&&&&&&&& C bit: 1&&&& &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& Multiplier: 5&&&&&&&&&&&&&& - Length: 24&&&&&&&&&&&& My Discr.: 77&&&&&&&&&&&&&& - Your Discr.: 1&&&&&&&&&&&& Min tx interval: 200000&&&& - Min rx interval: 200000&&&&&&&&&&&& Min Echo interval: 0&&&&&&
您能也检查同一命令给同一输出的硬件， RX没有接收。
R1#show bfd neighbors hardware detailsIPv4 SessionsNeighAddr&&&&&&&&&&&&&&&&&&&&&&&&&&&&& LD/RD&&&&&&&& RH/RS&&&& State&&&& Int172.31.11.34&& &&&&&&&&&&&&&&&&&&&&&&&&&1/0&&&&&&&&& Down&&&&& Down&&&&& Te3/21Session Host: HardwareOurAddr: 172.31.11.33&&Handle: 1Local Diag: 1, Demand mode: 0, Poll bit: 0MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 5Received MinRxInt: 200000, Received Multiplier: 5Holddown (hits): 0(0), Hello (hits): 1000(0)Rx Count: 37Tx Count: 19337Elapsed time watermarks: 0 0 (last: 0)Registered protocols: ISIS CEFDowntime: 05:22:16Last packet: Version: 1&&&&&&&&&&&&&&&&& - Diagnostic: 0&&&&&&&&&&&& State bit: Up&&&&&&&&&&&&&& - Demand bit: 0&&&&&&&&&&&& Poll bit: 0&&&&&&&&&&&&&&&& - Final bit: 0&&&&&&&&&&&& C bit: 1&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& Multiplier: 5&&&&&&&&&&&&&& - Length: 24&&&&&&&&&&&& My Discr.: 77&&&&& &&&&&&&&&- Your Discr.: 1&&&&&&&&&&&& Min tx interval: 200000&&&& - Min rx interval: 200000&&&&&&&&&&&& Min Echo interval: 0&&&&&&R1#show bfd neighbors hardware detailsIPv4 SessionsNeighAddr&&&&&&&&&&&&&&&&&&&&&&&&&&&&& LD/RD&&&&&&&& RH/RS&&&& State&&&& Int172.31.11.34&&&&&&&&&&&&&&&&&&&&&&&&&&& 1/0&&&&&&&&& Down&&&&& Down&&&&& Te3/21Session Host: HardwareOurAddr: 172.31.11.33&&Handle: 1Local Diag: 1, Demand mode: 0, Poll bit: 0MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 5Received MinRxInt: 200000, Received Multiplier: 5Holddown (hits): 0(0), Hello (hits): 1000(0)Rx Count: 37Tx Count: 19348Elapsed time watermarks: 0 0 (last: 0)Registered protocols: ISIS CEFDowntime: 05:22:28Last packet: Version: 1&&&&&&&&&&&&&&&&& - Diagnostic: 0&&&&&&&&&&&& State bit: Up&&&&&&&&&&&&&& - Demand bit: 0&&&&&&&&&&&& Poll bit: 0&&&&&&&&&&&&&&&& - Final bit: 0&&&&&&&&&&&& C bit: 1&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& Multiplier: 5&&&&&&&&&&&&&& - Length: 24&&&&&&&&&&&& My Discr.: 77&& &&&&&&&&&&&&- Your Discr.: 1&&&&&&&&&&&& Min tx interval: 200000&&&& - Min rx interval: 200000
在此以后，您能继续到检查计数器直接地在线路卡。
对于此您需要在show bfd邻接详细资料输出的本地分辨器(LD)值，为了此案件LD值是1。
LD，此值用于独特识别此会话，并且一定是唯一和非零，为此设备的所有BFD会话。
您执行show module并且看到线路卡3是DFC。
您附加您要检查BFD值的线路卡，在这种情况下它是线路卡3。
R1# attach 3R1-dfc3# show platform npc bfd ld 1bfd_pak_big 0bfd_pak_authenticated 0bfd_x40g_xlifid_ifnum0 0bfd_wd_hash_table_retry_count 0bfd_ld_hash_table_retry_count 0x40g_sso_differ_ld_count 0Current normal_event_qsize 0 and 0 paks crossed the limit.****BFD Session info for ld(1) avlnode ld (1) ****ifnum(25), slotunit(21), txtimer(1000000) detect_timer(0)p bit(0), f bit(0), srcip(172.31.11.33) dstip(172.31.11.34)wdog cnterid(65664) tags inner(0) outer(0) tx sess info(0x19F4B7E0)ADJ registered(0x1) tag_count(0) tx sessid(830)dmac(dccc.eeee.aaaa), smac(5033.eeeee.8888), rx statid(508546), tx statid(508545)RX pkt count(5838365), TX pkt count (5208864) ss------------------------------------------ Here you can see the counters for the RX and TXIPV6 SA(::), IPV6 DA(::), no_adj_retry_tx (0)R1# show platform npc bfd ld 1bfd_pak_big 0bfd_pak_authenticated 0bfd_x40g_xlifid_ifnum0 0bfd_wd_hash_table_retry_count 0bfd_ld_hash_table_retry_count 0x40g_sso_differ_ld_count 0Current normal_event_qsize 0 and 0 paks crossed the limit.****BFD Session info for ld(1) avlnode ld (1) ****ifnum(25), slotunit(21), txtimer(1000000) detect_timer(0)p bit(0), f bit(0), srcip(172.31.11.33) dstip(172.31.11.34)wdog cnterid(65664) tags inner(0) outer(0) tx sess info(0x19F4B7E0)ADJ registered(0x1) tag_count(0) tx sessid(830)dmac(dccc.eeee.aaaa), smac(5033.eeeee.8888), rx statid(508546), tx statid(508545)RX pkt count(5838365), TX pkt count (5208864)& ss-------------------------- RX is not increasingIPV6 SA(::), IPV6 DA(::), no_adj_retry_tx (0)
这时，更加进一步您排除故障，并且SPAN捕获在相邻设备推荐发现该设备是否实际上发送数据包。
米格尔佩雷斯维特纳Cisco TAC工程师
古斯塔沃SibajaCisco TAC工程师
此文档是否有帮助?
相关的支持社区讨论IP Routing: BFD Configuration Guide
- BFD Multihop Support & Downloads for IPv4 Static Routes [Cisco Cloud Services Router 1000V Series] - Cisco
IP Routing: BFD Configuration Guide
Book Contents
Book Contents
Available Languages
Download Options
Book Title
IP Routing: BFD Configuration Guide
Chapter Title
BFD Multihop Support for IPv4 Static Routes
View with Adobe Reader on a variety of devices
Chapter: BFD Multihop Support for IPv4 Static Routes
Chapter Contents
BFD Multihop Support for IPv4 Static Routes The BFD Multihop Support for IPv4 Static Routes feature enables detection of IPv4 network failure between paths that are not directly connected. If a Bidirectional Forwarding Detection (BFD) session is up (that is, the next-hop destination is reachable), IPv4 static routes that are associated with IPv4 static BFD configuration are added to a routing table. If the BFD session is down, the routing table removes all associated static routes from the routing table.
This feature is applicable on different kinds of interfaces such as physical, subinterface, and virtual tunnels and across intra-area and interarea topologies.
Finding Feature
Information
Your software release
may not support all the features documented in this module. For the latest
caveats and feature information, see
release notes for your platform and software release. To find information about
the features documented in this module, and to see a list of the releases in
which each feature is supported, see the feature information table.
Use Cisco Feature
Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to
An account on Cisco.com is not required.
Prerequisites for BFD Multihop Support for IPv4 Static Routes
The BFD destination for which an IPv4 static route has to be configured must be reachable by all devices.
The configured device must have at least one static route with the next-hop destination as a BFD destination for an associated session. If not, the BFD session is not created on the device.
Information About BFD Multihop Support for IPv4 Static Routes
BFDv4 Associated Mode
In Bidirectional Forwarding Detection for IPv4 (BFDv4) associated mode, an IPv4 static route is automatically associated with an IPv4 static BFDv4 multihop destination address if the static route next hop exactly matches the static BFDv4 multihop destination address.
The state of the BFDv4 session is used to determine whether the associated IPv4 static routes are added in the IPv4 routing information base (RIB). For example, static routes are added in the IPv4 RIB only if the BFDv4 multihop destination is reachable, and the static routes are removed from the IPv4 RIB if the BFDv4 multihop destination subsequently becomes unreachable.
BFDv4 Unassociated Mode
In Bidirectional Forwarding Detection for IPv4 (BFDv4), an IPv4 static BFD multihop destination can be configured in unassociated mode. In unassociate mode, a BFD neighbor is not associated with a static route, and the BFD sessions are requested if the IPv4 static BFD is configured.
Unassociated mode is useful in the following scenario:
Absence of an IPv4 static route—This scenario occurs when a static route is on device A, and device B is the next hop. In associated mode, you must create both a static BFD multihop destination address and a static route on both devices to bring up the BFDv4 session from device B to device A. Specifying the static BFD multihop destination in unassociated mode on device B avoids the need to configure an unwanted static route.
How to Configure BFD Multihop Support for IPv4 Static Routes
Configuring BFD Multihop IPv4 Static Routes
Before You Begin
Specify a BFD destination address which is same as the IPv4 static route next hop or gateway address.
Configure a BFD map and a BFD multihop template for an interface on the device. The destination address and source address configured for a BFD map must match the BFD static multihop configuration and the source address must be a valid IP address configured for an interface in the routing table.
SUMMARY STEPS1.
configure terminal
prefix mask ip-address
ip route static bfd
multihop-destination-address multihop-source-address
ip route static bfd
multihop-destination-address multihop-source-address
unassociate
DETAILED STEPS Command or ActionPurposeStep 1
Device& enable
Enables privileged EXEC mode.
Enter your password if prompted.
Step 2configure terminal
Device# configure terminal
Enters global configuration mode.
Step 3ip route
prefix mask ip-address
Device(config)# ip route 192.0.2.0 255.255.255.0 10.1.1.2
Configures an IPv4 static route that BFD multihop uses to monitor static routes.
Step 4ip route static bfd
multihop-destination-address multihop-source-address
Device(config)# ip route static bfd 192.0.2.1 10.1.1.1
Configures the static IPv4 BFD multihop to be associated with a static IPv4 route.
Step 5ip route static bfd
multihop-destination-address multihop-source-address
unassociate
Device(config)# ip route static bfd 192.0.2.1 10.1.1.1 unassociate
(Optional) Configures the static IPv4 BFD multihop to be associated with a static IPv4 route in unassociated mode.
Device(config)# end
Exits global configuration mode and returns to privileged EXEC mode.
Verifying BFD Multihop Support for IPv4 Static Routes
The following show commands can be used to verify IPv4 static routes for BFD multihop:
SUMMARY STEPS1.
DETAILED STEPSStep 1
Displays a line-by-line listing of existing BFD adjacencies.
Displays information about the IPv4 static BFD configured parameters.
Configuration Examples for BFD Multihop Support for IPv4 Static Routes
Example: Configuring BFD Multihop for IPv4 Static Routes in Associated Mode
Device& enable
Device# configure terminal
Device(config)# bfd map ipv4 192.0.2.1/32
10.1.1.1/32 test
Device(config)# bfd-template multi-hop test
Device(config-bfd)# interval min-tx 51 min-rx 51 multiplier 3
Device(config-bfd)# exit
Device(config)# ip route 192.0.2.0 255.255.255.0 10.1.1.2
Device(config)# interface GigabitEthernet 1/1
Device(config-if)# ip address 10.1.1.1 255.255.0.0
Device(config-if)# exit
Device(config)# ip route static bfd 192.0.2.1 10.1.1.1
Device(config)# end
Example: Configuring IPv4 Static Multihop for BFD in Unassociated Mode
Device& enable
Device# configure terminal
Device(config)# bfd map ipv4 192.0.2.1/32
10.1.1.1/32 test
Device(config)# bfd-template multi-hop test
Device(config-bfd)# interval min-tx 51 min-rx 51 multiplier 3
Device(config-bfd)# exit
Device(config)# ip route 192.0.2.0 255.255.255.0 10.1.1.2
Device(config)# interface GigabitEthernet 1/1
Device(config-if)# ip address 10.1.1.1 255.255.0.0
Device(config-if)# exit
Device(config)# ip route static bfd 192.0.2.1 10.1.1.1 unassociate
Device(config)# end
Additional References for BFD Multihop Support for IPv4 Static Routes
Related Documents
Related Topic
Document Title
Standards and RFCs
Standard/RFC
Technical Assistance
Description
Feature Information for BFD Multihop Support for IPv4 Static Routes
The following table
provides release information about the feature or features described in this
module. This table lists only the software release that introduced support for
a given feature in a given software release train. Unless noted otherwise,
subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform
support and Cisco software image support. To access Cisco Feature Navigator, go
An account on Cisco.com is not required.
Table 1 Feature Information for BFD Multihop Support for IPv4 Static RoutesFeature Name
Feature Information
Was this Document Helpful?
Contact Cisco
(Requires a )
Related Support Community Discussions}