Downloads |
Table Of Contents
CompactFlash Disk Commands with Cisco 7304 High Availability
High Availability Benefits—RPR Redundancy Mode
High Availability Benefits—RPR+ Redundancy Mode
High Availability Benefits—SSO Redundancy Mode
Restrictions in All Redundancy Modes
Restrictions—RPR Redundancy Mode
Restrictions—RPR+ Redundancy Mode
Restrictions—SSO Redundancy Mode
Supported Standards, MIBs, and RFCs
Setting the Config-Register Boot Variable
Configuring Fast Software Upgrade
Verifying Cisco 7304 High Availability
Monitoring and Maintaining Cisco 7304 High Availability
Setting the Config-Register Boot Variable Example
Performing a Manual Switchover Example
Cisco 7304 High Availability
Feature History
This document describes the High Availability feature on Cisco 7304 routers and contains the following sections:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
High Availability
The Cisco 7304 Route Processor High Availability feature adds support for a second dual-wide network services engine (NSE) or network processing engine (NPE) installed in a Cisco 7304 router. Previously only one dual-wide processor could be installed in slots 0 and 1. The Route Processor High Availability feature enables a second processor to be installed in slots 2 and 3. This additional processor can be the only processor installed in the system, or it can be a second processor. The processor installed in slots 0 and 1 is the preferred active processor. Upon bootup, the processor in slots 0 and 1 assumes the role of the active processor (active RP by some High Availability definitions). The standby processor (standby RP by some High Availability definitions) in slots 2 and 3 waits for 45 seconds for the processor in slots 0 and 1 to assume the role of active RP. If there is no processor installed in slots 0 and 1, the processor in slots 2 and 3 bypasses the 45-second wait and automatically assumes the role of active RP.
Upon booting, the system recognizes the processor installed in slot 0 and slot 1 as the active RP unless it is absent or there is some error condition existing on this processor. The active RP can be made to cede its role as the active to an operational standby using the redundancy force-switchover command.
You do not need to configure anything on the router to activate the Cisco 7304 High Availability feature. Installing a second processor in the chassis automatically creates redundancy in the system. Make sure that you have Cisco IOS images that support High Availability installed on both the active and the standby processors. We strongly recommend that you install the same Cisco IOS release image on both the active and standby RPs. You should also make sure that the configuration register is properly configured.
The Cisco 7304 can operate in one of three redundancy modes:
•
•
•
In all modes, the standby RP will take over when the active RP fails. However the general systems behavior is different for each mode and is summarized in Table 1:
For information on SSO, refer to the Stateful Switchover feature at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s20/fssso20s.htm
For information on the Nonstop Forwarding (NSF) feature, introduced on the Cisco 7304 router in Cisco IOS Release 12.2(20)S as part of the support for SSO, refer to the Cisco Nonstop Forwarding feature at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s20/fsnsf20s.htm
Line Card Reset Behavior
Line cards can reset across a switchover depending on the type of line card and the redundancy mode your system is in. Table 2 describes the reset behavior of line cards based on the redundancy mode. The "N/A" indicated in the table reflects that the PCI port adapter carrier cards do not support the RPR+ and SSO redundancy modes.
Table 2 Line Card Reset Behavior by Redundancy Mode
RPR
Yes
Yes
Yes
RPR+
No
Yes
N/A
SSO
No
No
N/A
Fast Software Upgrade
The High Availability feature supports Fast Software Upgrade (FSU) for Cisco 7304 routers. Using FSU, you can reduce planned downtime. With FSU, you can configure the system to switch over to a standby RP that is preloaded with an upgraded Cisco IOS software image. FSU reduces outage time during a software upgrade by transferring functions to the standby RP that has the upgraded Cisco IOS software pre-installed. The only downtime with Fast Software Upgrade is the time required for the standby RP to take control during the switchover. You can also use FSU to downgrade a system to an older version of Cisco IOS or have a backup system loaded for downgrading to a previous image immediately after an upgrade.
Note
Note
Note
Online Insertion and Removal
The Cisco 7304 High Availability feature supports online insertion and removal (OIR) of processors.
Once the standby RP boots up, it becomes the standby RP and the startup configuration is synchronized from the active to the newly inserted standby RP. The file systems on the standby RP also become visible and usable on the active RP as remote file systems.
If you perform a removal of the active RP from a Cisco 7304 router with redundant RPs, the standby RP (if it is booted up and ready as the standby RP) detects the removal of the active RP and switches over to become the new active RP.
If the previously active RP is inserted, it comes up as the standby RP.
The NSE-100 handles native Gigabit Ethernet interfaces differently than the NPE-G100 and NSE-150. When a standby Route Processor is present and running on the NSE-100, the Gigabit Ethernet interfaces on the standby Route Processor are visible and usable on the active Route Processor, irregardless of whether the standby system has or has not booted the Cisco IOS image.
On the NPE-G100, the three Gigabit Ethernet interfaces on the standby Route Processor are not designed to be visible or usable on the active Route Processor. On the NSE-150, the four Gigabit Ethernet interfaces are not designed to be visible or usable on the active Route Processor.
The Fast Ethernet management interface, however, should not be used by the active Route Processor at any time on both the NSE-100 and NSE-150.
The different handling of interfaces by the processors is the reason for the different interface numbering schemes for the Ethernet ports on the NSE-100. The Gigabit Ethernet interfaces require that slot and interface number (slot/interface-number) be specified in the CLI, while the Fast Ethernet interface only requires an interface number be specified. Similarly, because the Gigabit Ethernet interfaces on the standby Route Processor are not designed to be visible or usable on the active Router Process for the NPE-G100 or NSE-150, only the interface number must be entered in the CLI to specify a native NPE-G100 or NSE-150 Gigabit Ethernet interface.
Management Port
The Fast Ethernet port on the Cisco 7304 routers is the default management port. When two NSEs are installed in your system, the Fast Ethernet management port is configured as Fast Ethernet 0, not Fast Ethernet 0/0.
In Cisco IOS software images that pre-date the introduction of RPR support on the Cisco 7304, the Fast Ethernet port on the NSE-100 was numbered in the slot/unit format. The NSE-150 supported RPR at release and the Fast Ethernet management port is always Fast Ethernet 0.
If you already have configurations in your system for the management port configured as Fast Ethernet 0/0, the configuration is still recognized as valid. However new configuration changes will not accept Fast Ethernet 0/0, only Fast Ethernet 0. All configurations displayed by the show running-config command are displayed as Fast Ethernet 0.
On the NPE-G100, there is no dedicated management interface and so any of the GigabitEthernet ports on the NPE-G100 can be used as the management port.
CompactFlash Disk Commands with Cisco 7304 High Availability
With support for the Cisco 7304 High Availability feature, you can configure many Cisco IOS file system commands from the active RP to display and configure information on the standby RP by appending the stby- prefix to the usual file system commands.
Table 3 lists some of the CompactFlash Disk commands that can be issued on the active RP and affect the standby RP.
For more information about using file system commands, see the Cisco IOS File System Commands part of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.1.
For more information about basic software commands you can use with the CompactFlash Disk in a Cisco 7304 router, see the "Removing and Installing the NSE-100" chapter of the Cisco 7304 Network Service Engine Installation and Configuration guide.
For more information about basic software commands you can use with a CompactFlash Disk on a network processing engine (NPE-G100), see the "Working with a CompactFlash Disk" chapter of the Cisco 7304 Network Processing Engine Installation and Configuration.
Benefits
The Cisco 7304 Route Processor High Availability feature provides the following benefits based on the redundancy mode the system is configured for:
High Availability Benefits—RPR Redundancy Mode
•
•
•
•
•
High Availability Benefits—RPR+ Redundancy Mode
Route Processor Redundancy Plus (RPR+) redundancy mode provides the following benefits in addition to the benefits provided by Route Processor Redundancy (RPR) mode:
•
•
•
High Availability Benefits—SSO Redundancy Mode
Stateful Switchover (SSO) redundancy mode is the most sophisticated redundancy mode and provides the most benefits on a Cisco 7304 router. Benefits include Nonstop Forwarding (NSF) of data traffic in addition to the benefits provided by the RPR+ mode.
For information on High Availability benefits when your system is in the SSO redundancy mode, see the Stateful Switchover feature at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s20/fssso20s.htm
Also see the Cisco Nonstop Forwarding feature at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s20/fsnsf20s.htm
Restrictions
Restrictions in All Redundancy Modes
The following restrictions apply in all modes:
•
•
•
•
•
•
Restrictions—RPR Redundancy Mode
•
•
•
Restrictions—RPR+ Redundancy Mode
•
•
•
Restrictions—SSO Redundancy Mode
•
•
•
For information on High Availability restrictions when your system is in the SSO Redundancy Mode, see the Stateful Switchover document at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s20/fssso20s.htm
Related Documents
•
•
•
•
•
•
•
•
Supported Platforms
•
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
The Cisco 7304 router now supports the following MIB:
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
•
•
•
Configuration Tasks
No configuration is necessary for the Cisco 7304 High Availability feature. RP redundancy is automatic when a second processor is installed in slot 2 and slot 3. See the following sections for optional configuration tasks for the Cisco 7304 High Availability feature:
•
•
See the following sections for verification tasks and troubleshooting tips for the Cisco 7304 High Availability feature:
•
•
Setting the Config-Register Boot Variable
Though it is not required for RPR redundancy mode, we recommend that you modify the software configuration register boot field so that the system boots the same image that is loaded on the standby RP. The RPR+ and SSO redundancy modes will only operate if the same software version is running on both the active and standby RPs.
Step 1
Router# show version
Displays the current configuration register setting.
Step 2
Router# configure terminal
Enters configuration mode, selecting the terminal option.
Step 3
Router(config)# boot system flash disk0:[imagename]
Specifies the image filename for the system to boot up.
•
Step 4
Router(config)# config-register value
Modifies the existing configuration register setting to reflect the way in which you want to load a system image.
•
See Table 4 and Table 5 for more information about the configuration register settings.Step 5
Router# Ctrl-Z
Exits configuration mode.
Step 6
Router# reload
Reboots the router to make your changes take effect.
Table 4 Software Configuration Register Bit Meanings
00-03
0x0000-0x000F
Boot field (see Table 5)
06
0x0040
Ignore nonvolatile RAM (NVRAM) contents
07
0x0080
OEM bit enabled
08
0x0100
Break disabled
10
0x0400
IP broadcast with all zeros
11-2
0x0800-0x1000
Console line speed
13
0x2000
Boot default ROM software if network boot fails
14
0x4000
IP broadcasts do not have net numbers
15
0x8000
Enable diagnostic messages and ignore NVRAM contents
Table 5 Explanation of Boot Field (Configuration Register Bits 00-03)
00
Stays at the system bootstrap prompt
01
Boots system image on EPROM
02-F
Specifies a default netboot filename
Enables boot system commands that override default netboot filename.1
1 Values of the boot field are 2-15 in the form cisco<n>-processor_name, where 2 < n < 15.
1 For more information about setting the configuration register, refer to the document Software Configuration Register.
Configuring Fast Software Upgrade
To configure Fast Software Upgrade, use the commands below beginning in privileged EXEC mode:
Verifying Cisco 7304 High Availability
To verify Cisco 7304 High Availability, follow these steps:
Step 1
IOS (tm) 7300 Software (C7300-JS-MZ), Version 12.1(20020306:160533)]Copyright (c) 1986-2002 by cisco Systems, Inc.Compiled Tue 12-Mar-02 18:27 by abcImage text-base: 0x40008970, data-base: 0x4192C000...Configuration register is 0x2002...Step 2
Step 3
Router# show redundancyRedundant System Information :------------------------------Available system uptime = 23 hours, 21 minutesSwitchovers system experienced = 0Standby failures = 0Last switchover reason = noneHardware Mode = DuplexConfigured Redundancy Mode = SSOOperating Redundancy Mode = SSOMaintenance Mode = DisabledCommunications = UpCurrent Processor Information :-------------------------------Active Location = slot 0Current Software state = ACTIVEUptime in current state = 23 hours, 21 minutesImage Version = Cisco Internetwork Operating System SoftwareIOS (tm) 7300 Software (C7300-JS-M), Version 12.2(20)S, EARLY DEPLOYMENT RELEASE SOFTWARE(fc1)Copyright (c) 1986-2003 by Cisco Systems, Inc.Compiled Mon 06-Oct-03 16:02 by ssangiahBOOT = disk0:c7300-p-mz,12CONFIG_FILE =BOOTLDR = bootdisk:c7300-boot-mzConfiguration register = 0x2Peer Processor Information :----------------------------Standby Location = slot 2Current Software state = STANDBY HOTUptime in current state = 23 hours, 18 minutesImage Version = Cisco Internetwork Operating System SoftwareIOS (tm) 7300 Software (C7300-JS-M), Version 12.2(20)S, EARLY DEPLOYMENT RELEASE SOFTWARE(fc1)Copyright (c) 1986-2003 by Cisco Systems, Inc.Compiled Mon 06-Oct-03 16:02 by ssangiahBOOT = disk0:c7300-p-mz,12CONFIG_FILE =BOOTLDR = bootdisk:c7300-boot-mzConfiguration register = 0x2Router#
Troubleshooting Tips
•
•
rommon 1 > b disk0:c7300-js-mzSelf decompressing the image :##########################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################[OK]%Error:NSE in unsupported slot; NSE must be inserted in slot0.%Error:NSE in unsupported slot; NSE must be inserted in slot0.%Error:NSE in unsupported slot; NSE must be inserted in slot0.%Error:NSE in unsupported slot; NSE must be inserted in slot0.%Error:NSE in unsupported slot; NSE must be inserted in slot0.%Error:NSE in unsupported slot; NSE must be inserted in slot0.%Error:NSE in unsupported slot; NSE must be inserted in slot0.%Error:NSE in unsupported slot; NSE must be inserted in slot0.To recover from this situation, reset the processor in slot 2 from the active RP as follows:
Router# hw-module standby resetProceed with reset of standby NSE? [confirm]y
Note
You should then boot the processor in slot 2 with a High Availability image. This can be done by inserting the processor in slot 0 and copying system and boot High Availability images to the disk0: and bootdisk:. Another option is to insert a CompactFlash Disk with a High Availability image in the processor in slot 2 and boot that image. Both the boot and system images of both processors must be upgraded to run High Availability images for proper operation of the Cisco 7304 High Availability feature.
•
System Bootstrap, Version 12.1(20011026:021245) [rommon_1_1 101], DEVELOPMENT SOFTWARECopyright (c) 2002-2003 by cisco Systems, Inc.C7300 platform with 131072 Kbytes of main memoryCurrently running ROMMON from ROM 1Self decompressing the image:################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################## [OK]Restricted Rights LegendUse, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.Cisco Systems, Inc.170 West Tasman DriveSan Jose, California 95134-1706Cisco Internetwork Operating System SoftwareIOS (tm) 7300 Software (C7300-P-M), Version 12.2(20030704:195727) [biff-cwisp1 229]Copyright (c) 1986-2003 by cisco Systems, Inc.Compiled Sun 17-Aug-03 10:49 by biffImage text-base: 0x40008BF4, data-base: 0x42076000Downloading default microcode: system:pxf/ucode1.Successfully downloaded the production microcode.Currently running ROMMON from ROM 1Standby operating in RPR mode, console disabled[OK][OK]After this point, the standby console is not responsive to input.
Note that the standby RP boots up completely in RPR+ and SSO modes although the standby console is still disabled. The complete boot of the standby RP is one of the factors that allows a faster switchover time in RPR+ and SSO redundancy modes.
The following output is displayed on the standby RP console as the processor boots in RPR+ or SSO mode:
Self decompressing the image:####################################################################################################################################################### [OK]Restricted Rights LegendUse, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.cisco Systems, Inc.170 West Tasman DriveSan Jose, California 95134-1706Cisco Internetwork Operating System SoftwareIOS (tm) 7300 Software (C7300-JS-M), Version 12.2(20)S, EARLY DEPLOYMENT RELEASESOFTWARE (fc1)Copyright (c) 1986-2003 by cisco Systems, Inc.Compiled Mon 06-Oct-03 16:02 by ssangiahImage text-base:0x40008CFC, data-base:0x420B0000Downloading default microcode:system:pxf/ucode1.Successfully downloaded the production microcode.Currently running ROMMON from ROM 1cisco 7300 (NSE100) processor (revision D) with 114688K/16384K bytes of memory.Processor board IDR7000 CPU at 350Mhz, Implementation 39, Rev 3.2, 256KB L2, 1024KB L3 CacheLast reset from software reset or reloadX.25 software, Version 3.0.0.Bridging software.PXF processor tmc0 'system:pxf/ucode1' is running ( v4.1 ).PXF processor tmc1 'system:pxf/ucode1' is running ( v4.1 ).3 FastEthernet/IEEE 802.3 interface(s)4 Gigabit Ethernet/IEEE 802.3 interface(s)2 ATM network interface(s)509K bytes of non-volatile configuration memory.31360K bytes of ATA compact flash in bootdisk (Sector size 512 bytes).31360K bytes of ATA compact flash in disk0 (Sector size 512 bytes).[OK][OK]STDBY_SERVICES_SYNC_CONFIG_SIZE_REQ receivedLogging of %SNMP-3-AUTHFAIL is enabledSuccessfully configured from rcsf file, ha_alternate_parse TRUEPress RETURN to get started!00:02:42:%SYS-6-BOOTTIME:Time taken to reboot after reload = 236 secondsRouter>Standby console disabledRouter>Standby console disabledRouter>Standby console disabledRouter>Standby console disabledRouter>Standby console disabled•
If the processor is configured to operate in RPR+ or SSO redundancy modes and the processor determines at bootup that it cannot operate in those modes, then the system falls back to RPR mode. A system can fall back to RPR mode due to an error that prevents the configured mode from taking effect such as a failure in the synchronization of the running configuration. The fallback to RPR mode is reflected in the show redundancy command output where the configured and operations redundancy modes are different.
The most likely reason for a system falling back to RPR mode is that the Cisco 7304 chassis has installed cards that do not support RPR+ or SSO redundancy modes. For example, if a system has a PCI port adapter carrier card, the system would fall back to RPR mode even if RPR+ or SSO were the configured modes.
The fallback would also happen if any card not supported in RPR+ or SSO redundancy modes was inserted into the system using OIR.
Note that there is no support for fall-forward in that if all cards not supporting RPR+ or SSO modes are OIR removed from the system, then the system does not fall forward to the previously configured mode (such as RPR+ or SSO). The Cisco 7304 router remains in RPR mode. However if you remove the PCI port adapter carrier card, you can effect a fall-forward on your system by the following methods:
–
–
When redundancy mode fallback happens, the following informational message is logged to the console:
*Aug 19 13:32:25.979: %REDUNDANCY-3-IPC: IOS versions do not match, redundancy modefallback*Aug 19 13:32:28.523: %HA-6-FALLBACK: System redundancy mode fallback - configuredmode(SSO), fallback mode(RPR)•
Router# redundancy force-switchoverProceed with switchover to standby NSE? [confirm]Standby not operational; switchover aborted.•
Router# hw-module standby reloadProceed with reload of standby NSE? [confirm]y%Standby RP is not upIf you see this error message, reload the standby RP by entering the hw-module standby reset command.
•
...Self decompressing the image :################################################################################################################################################################################################################################################################################################################################################################[OK]Currently running ROMMON from ROM 1Downloading default microcode:system:pxf/ucode1.Successfully downloaded the production microcode.%Error:Flash type not supported%Error:NSE fpga download incomplete 0x40System in minimal boot mode...%PLATFORM-3-MINIMALBOOT:System in minimal boot mode.%LINK-4-NOMAC:A random default MAC address of 0000.0c70.30a0 hasbeen chosen. Ensure that this address is unique, or specify MACaddresses for commands (such as 'novell routing') that allow theuse of this address as a default.%SYS-6-BOOT_MESSAGES:Messages above this line are from the boot loader.boot of "muck/ssangiah/c7300-p-mz 223.255.254.254" using boot helper"bootdisk:c7300-boot-mz" failederror returned:No usable interfacesloadprog:error - on file openboot:cannot load "muck/ssangiah/c7300-p-mz 223.255.254.254"•
To avoid a bad switchover when the router experiences a memory leak, the active RP can be configured to automatically reload itself when it reaches a certain threshold of free memory. Configure the router to create a core dump with memory size exception parameters and to reload when certain memory size parameters are violated. Use the exception memory minimum command and exception dump command.
The exception memory minimum command defines a minimum contiguous block of memory in the free pool and a minimum size for the free memory pool. The command syntax is:
[no] exception memory minimum size
The value of size is in bytes and is checked every 60 seconds. If you enter a size that is greater than the free memory and the exception dump command has been configured, the router creates a core dump and reloads the Cisco IOS software after 60 seconds. If the exception dump command is not configured, the router reloads without generating a core dump.
The following example configures the router to monitor the free memory. If the free memory falls below 250,000 bytes, the router dumps the core and reloads the Cisco IOS software.
Router# configure terminalRouter (config)# exception dump 131.108.92.2Router (config)# exception core-file memory.overrunRouter (config)# exception memory minimum 250000Monitoring and Maintaining Cisco 7304 High Availability
Use the following show and debug commands to monitor and maintain Cisco 7304 High Availability:
For more information about these commands, see the debug redundancy and show redundancy command reference pages in this document.
Configuration Examples
This section provides the following configuration examples:
•
•
Setting the Config-Register Boot Variable Example
The following example shows how to set the config-register boot variable:
Router# show version...IOS (tm) 7300 Software (C7300-JS-MZ), Version 12.1(20020306:160533)]Copyright (c) 1986-2002 by cisco Systems, Inc.Compiled Tue 12-Mar-02 18:27 by abcImage text-base: 0x40008970, data-base: 0x4192C000...Configuration register is 0x2002...configure terminalboot system flash disk0: C7300-js-mzconfig-register 0x2102Ctrl-ZreloadLoading a New Image Example
The following example shows how to load a Cisco IOS image onto the active and standby RPs and how to reset the standby RP to execute the newly loaded image:
Router# copy tftp disk0:c7300-js-mzRouter# copy tftp bootdisk:c7300-boot-mzRouter# copy tftp stby-disk0:c7300-js-mzRouter# copy tftp stby-bootdisk:c7300-boot-mzRouter# hw-module standby resetProceed with reset of standby NSE? [confirm]yRouter# copy running-config startup-configPerforming a Manual Switchover Example
The following example shows how to manually trigger a switchover between the active and standby RPs:
Router# redundancy force-switchoverCommand Reference
This section documents new or modified commands in this release or in prior releases. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications and in the document Cisco 7304 Router Platform-Specific Commands.
debug redundancy
To enable Route Processor (RP) redundancy debugging, use the debug redundancy command in privileged EXEC mode. To disable RP redundancy debugging, use the no form of this command.
debug redundancy {alarms | all | fsm | keepalive | peer-monitor | services | timesync | config-sync {bulk | lbl} | ehsa | kpa | msg | progression | status | timer}
no debug redundancy {alarms | all | fsm | keepalive | peer-monitor | services | timesync | config-sync {bulk | lbl} | ehsa | kpa | msg | progression | status | timer}
Syntax Description
Defaults
Redundancy debugging is not enabled by default.
Command Modes
Privileged EXEC
Command History
12.1(10)EX2
This command was introduced.
12.2(18)S
This command was introduced on Cisco 7304 routers running Cisco IOS Release 12.2S.
Usage Guidelines
You must enter a keyword when using the debug redundancy command.
Use the alarms keyword to display information about alarms that are generated in response to various redundancy-related events.
Use the all keyword to turn on all debug commands relating to the redundant RP feature.
Use the fsm keyword to display debug information about the finite state machine that tracks the status of the peer RP.
Use the keepalive keyword to display information about the exchange of keepalives between the primary and standby RP. If a certain number of keepalive responses are missed, the system that notices the keepalive failure takes whatever action is appropriate for recovering a possibly indefinitely paused or crashed peer RP.
Use the peer-monitor keyword to display debug information about the process on the active RP that monitors the status and health of the peer standby RP.
Use the services keyword to display information about miscellaneous service-related actions that happen across the standby and active RPs.
Use the timesync keyword to display debug information about the synchronization of the system clock between the active and standby RPs.
Examples
The following example shows how to enable redundancy alarms debugging:
Router# debug redundancy alarmsAsserting alarm :STBDY_REMOVEDThe following example shows how to enable all redundancy debugging:
Router# debug redundancy allThe following example shows how to enable redundancy FSM debugging:
Router# debug redundancy fsm*Mar 22 18:32:15:ehsa_fsm:state change, events:major=2 minor=1REDUNDANCY_PEERSTANDBY_INITED(9) => REDUNDANCY_PEERSTANDBY_NONOPERATIONAL(6)*Mar 22 18:32:40:ehsa_fsm:state change, events:major=2 minor=3REDUNDANCY_PEERSTANDBY_NONOPERATIONAL(6) => REDUNDANCY_PEERSTANDBY_NOTPRESENT(10)The following example shows how to enable redundancy keepalive debugging:
Router# debug redundancy keepaliveReceived keepaliveSent keepaliveReceived keepaliveSent keepaliveReceived keepaliveSent keepaliveReceived keepaliveSent keepaliveThe following example shows how to enable redundancy peer-monitor debugging:
Router# debug redundancy peer-monitor00:09:48:%REDUNDANCY-5-PEER_MONITOR_EVENT:Active detected a standby crash(raw-event=KEEPALIVE_FAILURE(7))00:10:13:%REDUNDANCY-5-PEER_MONITOR_EVENT:Active detected a standby removal(raw-event=PEER_NOT_PRESENT(3))The following example shows how to enable redundancy services debugging:
Router# debug redundancy servicesset_slave_monvar:syncing monvar to standby:DIAG=1set_slave_monvar:syncing monvar to standby:BOOT=tftp:abc/c7300-boot-mz 171.69.1.129,12set_slave_monvar:syncing monvar to standby:CONFIG_FILE=set_slave_monvar:syncing monvar to standby:BOOTLDR=bootdisk:c7300-boot-mzehsa_sync_config_fn:config-sync requestThe following example shows how to enable redundancy time synchronization debugging:
Router# debug redundancy timesyncset_slave_time:timesync sent, time:*17:27:14.251 UTC Fri Mar 22 2002(3225806834.1081509396)set_slave_time:timesync sent, time:*17:28:14.255 UTC Fri Mar 22 2002(3225806894.1098671504)Related Commands
Displays the types of cards (RPs and line cards) installed in a Cisco 7304 router.
Displays redundancy information for the active and standby RPs.
hw-module standby
To reset the standby Route Processor (RP), use the hw-module standby command in privileged EXEC mode.
hw-module standby {reset | reload}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.1(10)EX2
This command was introduced.
12.2(18)S
This command was introduced on Cisco 7304 routers running Cisco IOS Release 12.2S.
Usage Guidelines
Use this command to reset or reload the standby RP. Use the reload keyword to cause the standby RP to reload with an upgraded image. Use this option when the standby RP is operating normally. Use the reset keyword for a hard reset of the standby RP. Use this option if the standby RP is experiencing problems and does not respond to the reload option.
Examples
The following example shows how to reset the standby RP (NSE-100 example):
Router# hw-module standby resetProceed with reset of standby NSE? [confirm]yThe following example shows an attempt to reset a standby RP, which is down or experiencing some other problem such as an indefinite pause.
Router# hw-module standby reloadProceed with reload of standby NSE? [confirm]y%Standby RP is not upIf there is a failure to reset a standby RP because it is in some fault condition, try performing a reload of the RP.
The following example shows how to reload the standby RP:
Router# hw-module standby reloadProceed with reload of standby NSE? [confirm]yRelated Commands
redundancy mode
To choose the High Availability mode, use the redundancy mode command in global configuration mode.
redundancy mode {rpr | rpr-plus | sso}
Syntax Description
rpr
Enables Route Processor Redundancy mode.
rpr-plus
Enables Route Processor Redundancy Plus (RPR+) mode.
sso
Enables Stateful Switchover mode.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
12.2(20)S
This command was introduced on Cisco 7304 routers running Cisco IOS Release 12.2(20)S.
Usage Guidelines
Use the redundancy mode command to choose the High Availability mode.
You can configure your system in one of three High Availability redundancy modes wherein the standby Route Processor (RP) will take over when the active Route Processor fails. Your system behaves differently depending on the redundancy mode. Refer to the High Availability Benefits—RPR Redundancy Mode, the High Availability Benefits—RPR+ Redundancy Mode, and High Availability Benefits—SSO Redundancy Mode for a description of benefits under each redundancy mode.
Examples
The following example enables the Route Processor Redundancy Plus (RPR+) redundancy mode on the Cisco 7304 router. First enter global configuration mode, then enter the redundancy configuration mode (config-red) with the redundancy command, and finally enter the mode rpr-plus command to select the RPR+ redundancy mode:
Router# config tRouter(config)# redundancyRouter(config-red)# mode rpr-plusRelated Commands
redundancy force-switchover
To force the standby RP to assume the role of the active RP, use the redundancy force-switchover command in privileged EXEC mode.
redundancy force-switchover
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the redundancy force-switchover command to switch control from the active processor to the standby processor. Both the active and standby processors must have a High Availability Cisco IOS image installed and must be configured for RPR redundancy mode before the redundancy force-switchover command can be used. Before switching over, the system first verifies that the standby processor is ready to take over.
When you use the redundancy force-switchover command and the current running configuration is different from the startup configuration, the system prompts you to save the running configuration before the switchover is performed.
Examples
The following example shows a switchover from the active RP to the standby RP on a Cisco 7513 router with RPR configured:
Router# configure terminalRouter(config)# hw-module slot 7 image slot0:rsp-pv-mzRouter(config)# hw-module slot 6 image slot0:rsp-pv-mzRouter(config)# slave auto-sync configRouter(config)# redundancyRouter(config-r)# mode rprRouter(config-r)# endRouter# copy running-config startup-configRouter# redundancy force-switchoverThe following example shows how to perform a manual switchover from the active to the standby processor (NSE-100) when the running configuration is different from the startup configuration:
Router# redundancy force-switchoverSystem configuration has been modified. Save? [yes/no]:yBuilding configuration...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK]Proceed with switchover to standby NSE? [confirm]y00:07:35:%SYS-5-SWITCHOVER:Switchover requestedThe following example shows how to perform a manual switchover from the active to the standby processor when the running configuration is the same as the startup configuration:
Router# redundancy force-switchoverProceed with switchover to standby NSE? [confirm]00:07:35:%SYS-5-SWITCHOVER:Switchover requestedRelated Commands
show c7300
To display status of RPs, information about types of line cards installed, information about line card configuration guidelines and incompatible FPGA images in a Cisco 7304 router, use the show c7300 command in global configuration mode.
show c7300
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
This command displays the status of the active and standby RPs installed, types of line cards (such as native line cards, ATM line cards, and PCI port adapter carrier cards), and information about incompatible FPGA images in a Cisco 7304 router. This command also displays if your system is in compliance with line card configuration guidelines. Empty slots are not displayed in the show c7300 command output. When the bundled and current FPGA images are compatible, they are not displayed.
If your system contains an unsupported line card or RP with no matching bundled FPGA image in Cisco IOS, then this command displays "None" instead of the bundled FPGA version number.
Examples
The following example displays information about a Cisco 7304 router that has current FPGA images:
Router# show c7300Slot Card Type Status Insertion time---- --------- ------ --------------0,1 NSE-100 Active 00:13:16 ago4 1OC48-POS Active 00:01:43 agoSystem is compliant with hardware configuration guidelines.All the FPGAs in the system are up-to-dateNetwork IO Interrupt Throttling:throttle count=3, timer count=3active=0, configured=1netint usec=3999, netint mask usec=200The following example displays information about a Cisco 7304 router that has incompatible FPGA images that need to be updated. If your system contains an unsupported line card or RP with no matching bundled FPGA image in Cisco IOS, "None" is displayed instead of a bundled FPGA version number.
Router# show c7300Slot Card Type Status Insertion time---- --------- ------ --------------0,1 NSE-100 Active 00:02:26 ago4 6T3 Active 00:02:23 ago5 6T3 Active 00:02:23 agoSystem is compliant with hardware configuration guidelines.%WARNING:The following FPGAs in the system may need an update.Slot Card Type Current FPGA Bundled FPGA---- --------- ------------ ------------0 NSE-100 (MB) 0.12 NoneNetwork IO Interrupt Throttling:throttle count=0, timer count=0active=0, configured=1netint usec=3999, netint mask usec=200The following example displays sample output information about the redundancy status of the RPs installed in the system. In the example below, the active RP is the NSE-100 installed in slot 0 and slot 1. The standby is the NSE-100 installed in slot 2 and slot 3.
Router# show c7300Slot Card Type Status Insertion time---- --------- ------ --------------0,1 NSE-100 Active 00:02:03 ago2,3 NSE-100 Standby 00:02:03 ago4 4OC3-POS Active 00:01:59 ago5 6T3 Active 00:01:59 agoSystem is compliant with hardware configuration guidelines.Network IO Interrupt Throttling:throttle count=0, timer count=0active=0, configured=1netint usec=3999, netint mask usec=200The following example displays the high availability options and the option output.
NPEG100# show c7300 ha ?registers Show redundancy negotiation registersstatistics Show chkpt event statisticsNPEG100#NPEG100# show c7300 ha registersRedundancy Control Register Settings (0x1012)This processor controls the busThis processor is readyThis processor asserted the NSE OK backplane signalRedundancy Status Register Values (0x1011)Other processor is presentOther processor is readyOther processor asserted the NSE OK backplane signalRedundancy Interrupt Enable Register Value:0x5Redundancy Interrupt Status Register Value:0x50NPEG100#---------------NPEG100# show c7300 ha statisticsThis is Active RPWS HA CHKPT aggregate statisticsMessages sent:3468 (Bytes 72236)Blocking messages:11Nonblocking messages failures:Failures:0, Unknown events:0Messages received:3 (Bytes 2176)Messages dropped:Tx 0 Rx 0Last sent 00:00:00Last transmit dropped neverLast received 00:57:28Last receive dropped neverCHKPT statistics for the OIR Sync EventMessages sent:5 (Bytes 100)Blocking messages:5Nonblocking messages failures:Failures:0, Unknown events:0Messages received:0 (Bytes 0)Messages dropped:Tx 0 Rx 0Last sent 00:53:29Last transmit dropped neverLast received neverLast receive dropped never[Output elided]CHKPT statistics for the Standby Logger Message eventMessages sent:0 (Bytes 0)Blocking messages:0Nonblocking messages failures:Failures:0, Unknown events:0Messages received:1 (Bytes 80)Messages dropped:Tx 0 Rx 0Last sent neverLast transmit dropped neverLast received 00:58:00Last receive dropped neverNPEG100#-----------------------------------------------------------------------Related Commands
show redundancy
To display redundancy information for the active and standby Route Processors (RPs), use the show redundancy command in privileged EXEC mode.
show redundancy {states | counters | clients | history | switchover history}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display information about the active and standby RPs installed in a Cisco 7304 router.
Examples
The following example shows sample output for the show redundancy command:
Router# show redundancyRedundant System Information :------------------------------Available system uptime = 23 hours, 21 minutesSwitchovers system experienced = 0Standby failures = 0Last switchover reason = noneHardware Mode = DuplexConfigured Redundancy Mode = SSOOperating Redundancy Mode = SSOMaintenance Mode = DisabledCommunications = UpCurrent Processor Information :-------------------------------Active Location = slot 0Current Software state = ACTIVEUptime in current state = 23 hours, 21 minutesImage Version = Cisco Internetwork Operating System SoftwareIOS (tm) 7300 Software (C7300-JS-M), Version 12.2(20)S, EARLY DEPLOYMENT RELEASE SOFTWARE(fc1)Copyright (c) 1986-2003 by cisco Systems, Inc.Compiled Mon 06-Oct-03 16:02 by ssangiahBOOT = disk0:c7300-p-mz,12CONFIG_FILE =BOOTLDR = bootdisk:c7300-boot-mzConfiguration register = 0x2Peer Processor Information :----------------------------Standby Location = slot 2Current Software state = STANDBY HOTUptime in current state = 23 hours, 18 minutesImage Version = Cisco Internetwork Operating System SoftwareIOS (tm) 7300 Software (C7300-JS-M), Version 12.2(20)S, EARLY DEPLOYMENT RELEASE SOFTWARE(fc1)Copyright (c) 1986-2003 by cisco Systems, Inc.Compiled Mon 06-Oct-03 16:02 by ssangiahBOOT = disk0:c7300-p-mz,12CONFIG_FILE =BOOTLDR = bootdisk:c7300-boot-mzConfiguration register = 0x2Router#Table 6 describes the significant fields shown in the display.
The following example shows sample output for the show redundancy states command:
Router# show redundancy statesmy state = 13 -ACTIVEpeer state = 8 -STANDBY HOTMode = DuplexUnit ID = 0Redundancy Mode (Operational) = SSORedundancy Mode (Configured) = SSOSplit Mode = DisabledManual Swact = EnabledCommunications = Upclient count = 18client_notification_TMR = 30000 millisecondsRF debug mask = 0x0The following example shows sample output for the show redundancy counters command:
Router# show redundancy countersRedundancy Facility OMscomm link up = 2comm link down down = 1invalid client tx = 2null tx by client = 0tx failures = 0tx msg length invalid = 0client not rxing msgs = 0rx peer msg routing errors = 0null peer msg rx = 0errored peer msg rx = 0buffers tx = 159tx buffers unavailable = 0buffers rx = 156buffer release errors = 0duplicate client registers = 1failed to register client = 0Invalid client syncs = 0The following example shows sample output for the show redundancy clients command:
Router# show redundancy clientsclientID = 0 clientSeq = 0 RF_INTERNAL_MSGclientID = 29 clientSeq = 60 Redundancy Mode RFclientID = 25 clientSeq = 130 CHKPT RFclientID = 1314 clientSeq = 137 7300 Platform RFclientID = 22 clientSeq = 140 Network RF ClientclientID = 24 clientSeq = 150 CEF RRP RF ClientclientID = 5 clientSeq = 170 RFS clientclientID = 23 clientSeq = 220 Frame RelayclientID = 49 clientSeq = 225 HDLCclientID = 20 clientSeq = 310 IPROUTING NSF RF cliclientID = 21 clientSeq = 320 PPP RFclientID = 34 clientSeq = 350 SNMP RF ClientclientID = 52 clientSeq = 355 ATMclientID = 35 clientSeq = 360 History RF ClientclientID = 54 clientSeq = 530 SNMP HA RF ClientclientID = 75 clientSeq = 534 VRF commonclientID = 57 clientSeq = 540 ARPclientID = 65000 clientSeq = 65000 RF_LAST_CLIENTThe following example shows sample output for the show redundancy history command:
Router# show redundancy history4w5d client added: CHKPT RF(25) seq=1304w5d client added: 7300 Platform RF(1314) seq=13700:00:00 client added: RFS client(5) seq=17000:00:00 client added: History RF Client(35) seq=36000:00:12 client added: Redundancy Mode RF(29) seq=6000:00:12 client added: SNMP RF Client(34) seq=35000:00:12 client added: Network RF Client(22) seq=14000:00:12 client added: CEF RRP RF Client(24) seq=15000:00:12 *my state = INITIALIZATION(2) *peer state = DISABLED(1)00:00:12 RF_PROG_INITIALIZATION(100) RF_INTERNAL_MSG(0) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) Redundancy Mode RF(29) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) CHKPT RF(25) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) 7300 Platform RF(1314) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) Network RF Client(22) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) CEF RRP RF Client(24) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) RFS client(5) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) SNMP RF Client(34) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) History RF Client(35) op=0 rc=1100:00:12 RF_PROG_INITIALIZATION(100) RF_LAST_CLIENT(65000) op=0 rc=1100:00:12 *my state = NEGOTIATION(3) peer state = DISABLED(1)00:00:12 RF_EVENT_GO_STANDBY(512) op=000:00:12 *my state = STANDBY COLD(4) peer state = DISABLED(1)00:00:12 RF_PROG_STANDBY_COLD(101) RF_INTERNAL_MSG(0) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) IPROUTING NSF RF client(20) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) PPP RF(21) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) SNMP RF Client(34) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) ATM(52) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) History RF Client(35) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) SNMP HA RF Client(54) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) VRF common(75) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) ARP(57) op=0 rc=1100:05:50 RF_PROG_STANDBY_HOT(105) RF_LAST_CLIENT(65000) op=0 rc=000:05:50 RF_EVENT_CLIENT_PROGRESSION(503) RF_LAST_CLIENT(65000) op=8 rc=000:05:50 RF_EVENT_PEER_PROG_DONE(506) RF_LAST_CLIENT(65000) op=10500:05:51 *my state = ACTIVE(13) *peer state = STANDBY HOT(8)The following example shows sample output for the show redundancy switchover history command:
Router# show redundancy switchover historyIndex Previous Current Switchover Switchoveractive active reason time----- -------- ------- ---------- ----------1 2 0 user forced 13:11:00 UTC Tue Aug 19 20032 0 2 user forced 13:24:09 UTC Tue Aug 19 2003Related Commands
Glossary
Active NSE—The Network Services Engine (NSE) that controls and runs the routing protocols, and presents the system management interface.
FPGA—Field-Programmable Gate Array (FPGA) is a programmable logic device.
FSU—Fast Software Upgrade (FSU) reduces outage time during a software upgrade by transferring functions to the standby RP that has the upgraded Cisco IOS software pre-installed. You can also use FSU to downgrade a system to an older version of Cisco IOS.
NPE—Network Processing Engine (NPE). The NPE-G100 is a general-purpose processor available on the Cisco 7304 router. It handles approximately up to 1 mpps and is optimized for flexible feature support.
NSE—Network Services Engine (NSE). The high-performance NSE-100 and NSE-150 are available on the Cisco 7304 router. Both NSEs deliver an evolving set of application-specific, hardware-accelerated IP services through Cisco Parallel Express Forwarding (PXF) technology.
NSF—Cisco Nonstop Forwarding (NSF) works with the Stateful Switchover (SSO) feature in Cisco IOS software. SSO is a prerequisite of Cisco NSF. NSF works with SSO to minimize the amount of time a network is unavailable to its users following a switchover. The main objective of Cisco NSF is to continue forwarding IP packets following a Route Processor (RP) switchover.
NVRAM—nonvolatile RAM. RAM that retains its contents when a unit is powered off. Most Cisco routers store their configuration in NVRAM.
Online Insertion and Removal—online insertion and removal (OIR) of Route Processors (RPs). If you perform a removal of the active RP from a Cisco 7304 router with redundant RPs, the standby RP (if it is booted up and ready as the standby RP) detects the removal of the active RP and switches over to become the new active RP. If the previously active Route Processor is inserted, it comes up as the standby RP.
Redundancy Mode—The redundancy mode for which your system can be configured where the standby Route Processor (RP) will take over when the active Route Processor fails. The redundancy modes are Route Processor Redundancy (RPR), Route Processor Redundancy Plus (RPR+), and Stateful Switchover (SSO). Your system behaves differently depending on the redundancy mode, such as whether the standby RP boots up partially or completely, what the switchover time to a standby RP is, whether the startup configuration and running configuration are synchronized from the active RP to the standby RP, and whether line cards are reset across the switchover.
RPR—Route Processor Redundancy is a redundancy mode that allows Cisco IOS software to be booted on the standby Route Processor (RP) prior to switchover (a cold boot). In RPR mode, the standby RP loads a Cisco IOS image at boot time and initializes itself in standby mode; however, although the startup configuration is synchronized to the standby RP, system changes are not. In the event of a fatal error on the active RP, the system switches to the standby processor, which reinitializes itself as the active processor, reads and parses the startup configuration, reloads all of the line cards, and restarts the system.
RPR+—Route Processor Redundancy Plus redundancy mode. The standby Route Processor (RP) is fully initialized. The active RP dynamically synchronizes startup and the running configuration changes to the standby RP, meaning that the standby RP need not be reloaded and reinitialized (a "hot boot"). This allows for a faster switchover to a standby RP, usually in 4-5 seconds. Line cards are not reset across the switchover (except for ATM line cards).
SSO—Stateful Switchover redundancy mode provides all the functionality of RPR+ in that Cisco IOS software is fully initialized on the standby Route Processor (RP). In addition, SSO supports synchronization of line card, protocol, and application state information between RPs for supported features and protocols (a "hot standby").
Standby NSE—The network services engine (NSE) that waits, ready to take over the functions of the active NSE in the event of unplanned or planned downtime.
