![]() |
IP Routing: OSPF Configuration Guide, Cisco IOS Release 15S
|
||||||||||||||
OSPF NSR
![]() |
|||||||||||||||
|
Contents
OSPF NSRLast Updated: November 26, 2012
The OSPF NSR feature allows a device with redundant Route Processors (RPs) to maintain its Open Shortest Path First (OSPF) state and adjacencies across planned and unplanned RP switchovers. It does this by checkpointing state information from OSPF on the active RP to the standby RP. Later, following a switchover to the standby RP, OSPF can use this checkpointed information to continue operation without interruption. 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. Prerequisites for OSPF NSR
Restrictions for OSPF NSR
Information About OSPF NSROSPF NSR FunctionalityAlthough OSPF NSR serves a similar function to OSPF NSF, it works differently. With NSF, OSPF on the newly active standby RP initially has no state information, so it uses extensions to the OSPF protocol to recover its state from neighboring OSPF devices. For this to work, the neighbors must support the NSF protocol extensions and be willing to act as "helpers" to the restarting device. They must also continue forwarding data traffic to the restarting device while this recovery is taking place. With NSR, by contrast, the device performing the switchover preserves its state internally, and in most cases the neighbors are unaware that anything has happened. Because no assistance is needed from neighboring devices, NSR can be used in situations where NSF cannot; for example, in networks where not all the neighbors implement the NSF protocol extensions, or where network topology changes during the recovery can make NSF unreliable. How to Configure OSPF NSRConfiguring OSPF NSR
DETAILED STEPS Troubleshooting TipsOSPF NSR can increase the amount of memory used by the OSPF device process. To determine how much memory OSPF is currently using without NSR, you can use the show processes and show processes memory commands: Device# show processes | include OSPF 276 Mwe 133BE14 1900 1792 1060 8904/12000 0 OSPF-1 Router 296 Mwe 133A824 10 971 10 8640/12000 0 OSPF-1 Hello Process 276 is the OSPF device process that is to be checked. The show processes memory command is used to display its current memory use: Device# show processes memory 276 Process ID: 276 Process Name: OSPF-1 Router Total Memory Held: 4454800 bytes In this case, OSPF is using 4,454,800 bytes, or approximately 4.5 megabytes (MB). OSPF NSR could double this amount of memory for brief periods, so make sure the device has at least 5 MB of free memory before enabling OSPF NSR. Configuration Examples for OSPF NSRExample: Configuring OSPF NSRThe following example shows how to configure OSPF NSR: Device> enable Device# configure terminal Device(config)# router ospf 1 Device(config-router)# nsr Device(config-router)# end Device# show ip ospf 1 nsr Standby RP Operating in duplex mode Redundancy state: STANDBY HOT Peer redundancy state: ACTIVE ISSU negotation complete ISSU versions compatible Routing Process "ospf 1" with ID 10.1.1.100 NSR configured Checkpoint message sequence number: 3290 Standby synchronization state: synchronized Bulk sync operations: 1 Last sync start time: 15:22:48.971 UTC Fri Jan 14 2011 Last sync finish time: 15:22:48.971 UTC Fri Jan 14 2011 Last sync lost time: - Last sync reset time: - LSA Count: 2, Checksum Sum 0x00008AB4 The output shows that OSPF NSR is configured and that OSPF on the standby RP is fully synchronized and ready to continue operation should the active RP fail or if a manual switchover is performed. Additional ReferencesRelated DocumentsMIBsTechnical Assistance
Feature Information for OSPF NSRThe 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.
|
||||||||||||||
|
|