Feedback
|
Contents
- BFD for RIPv2 Support
- Finding Feature Information
- Prerequisites for BFD for RIPv2 Support
- How to Configure BFD for RIPv2 Support Feature
- Configuring BFD on RIPv2 Neighbors
- Configuration Example for BFD for RIPv2 Support Feature
- Example Configuring BFD for a RIPv2 Neighbor
- Additional References
- Feature Information for BFD for RIPv2 Support
BFD for RIPv2 Support
The BFD for RIPv2 Support feature is used to facilitate an alternate path selection when a neighboring router is inactive.
Routing Information Protocol (RIP) uses the timeout of prefixes of a particular neighbor to identify if a neighbor is inactive. By default, the timeout is 180 seconds; that is, although the next-hop router is inactive, the RIP router will still broadcast prefixes for up to 180 seconds.
Bidirectional Forward Detection (BFD) is a protocol that provides subsecond failure detection using a single, common standardized mechanism that is independent of media and routing protocols.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see 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 document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for BFD for RIPv2 Support
BFD is independent of RIPv2 and must be enabled and functional on the router.
How to Configure BFD for RIPv2 Support Feature
Configuring BFD on RIPv2 Neighbors
DETAILED STEPS
Configuration Example for BFD for RIPv2 Support Feature
Example Configuring BFD for a RIPv2 Neighbor
The following example shows how to configure BFD for all interfaces associated with a RIPv2 neighbor:
! interface GigabitEthernet 0/0/0 ip address 10.10.10.1 255.255.255.0 bfd interval 50 min_rx 50 multiplier 5 end ! interface GigabitEthernet 0/0/1 ip address 10.10.20.1 255.255.255.0 bfd interval 50 min_rx 50 multiplier 5 end ! router rip version 2 redistribute connected network 10.0.0.0 neighbor 10.10.20.2 bfd bfd all-interfaces no auto-summary !
Additional References
Related Documents
Technical Assistance
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for BFD for RIPv2 Support
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 www.cisco.com/go/cfn. An account on Cisco.com is not required.
| Table 1 | Feature Information for BFD for RIPv2 Support |
|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
BFD for RIPv2 Support |
Cisco IOS XE Release 3.3 |
The BFD for RIPv2 Support feature is used to facilitate alternate path selection when a neighboring router is inactive. The following commands were introduced or modified: bfd all-interfaces, debug ip rip bfd events, neighbor (RIP),and show ip rip neighbor. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Feedback