![]() |
|||||||||||||||||||||||||||
IPv6 NSF and Graceful Restart for MP-BGP IPv6 Address Family
![]() |
|||||||||||||||||||||||||||
Contents
IPv6 NSF and Graceful Restart for MP-BGP IPv6 Address FamilyLast Updated: July 19, 2012
Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool 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 www.cisco.com/go/cfn. An account on Cisco.com is not required. Information About IPv6 NSF and Graceful Restart for MP-BGP IPv6 Address FamilyNonstop Forwarding and Graceful Restart for MP-BGP IPv6 Address FamilyThe graceful restart capability is supported for IPv6 BGP unicast, multicast, and VPNv6 address families, enabling Cisco nonstop forwarding (NSF) functionality for BGP IPv6. The BGP graceful restart capability allows the BGP routing table to be recovered from peers without keeping the TCP state. NSF continues forwarding packets while routing protocols converge, therefore avoiding a route flap on switchover. Forwarding is maintained by synchronizing the FIB between the active and standby RP. On switchover, forwarding is maintained using the FIB. The RIB is not kept synchronized; therefore, the RIB is empty on switchover. The RIB is repopulated by the routing protocols and subsequently informs FIB about RIB convergence by using the NSF_RIB_CONVERGED registry call. The FIB tables are updated from the RIB, removing any stale entries. The RIB starts a failsafe timer during RP switchover, in case the routing protocols fail to notify the RIB of convergence. The Cisco BGP address family identifier (AFI) model is designed to be modular and scalable, and to support multiple AFI and subsequent address family identifier (SAFI) configurations. How to Configure IPv6 NSF and Graceful Restart for MP-BGP IPv6 Address FamilyConfiguring the IPv6 BGP Graceful Restart CapabilitySUMMARY STEPS
DETAILED STEPS Configuration Examples for IPv6 NSF and Graceful Restart for MP-BGP IPv6 Address FamilyExample: Configuring the IPv6 BGP Graceful Restart CapabilityIn the following example, the BGP graceful restart capability is enabled: Device# configure terminal Device(config)# router bgp 65000 Device(config-router)# address-family ipv6 Device(config-router-af)# bgp graceful-restart In the following example, the restart timer is set to 130 seconds: Device# configure terminal Device(config)# router bgp 65000 Device(config-router)# address-family ipv6 Device(config-router-af)# bgp graceful-restart restart-time 130 In the following example, the stalepath timer is set to 350 seconds: Device# configure terminal Device(config)# router bgp 65000 Device(config-router)# address-family ipv6 Device(config-router-af)# bgp graceful-restart stalepath-time 350 Additional ReferencesRelated Documents
MIBsTechnical Assistance
Feature Information for IPv6: NSF and Graceful Restart for MP-BGP IPv6 Address FamilyThe 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.
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. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||