|
|
Table Of Contents
show redundancy running-config-file
Redundancy Commands
CPU switch module redundancy provides protection against CPU switch module failure. Use the following commands to configure and monitor CPU switch module redundancy operations.
auto-sync counters interface
To enable automatic synchronizing of traffic statistics, performance monitoring counters, and performance history counters on the active CPU switch module to the standy CPU switch module, use the auto-sync counters interface command. To disable this feature, use the no form of this command.
auto-sync counters interface
no auto-sync counters interface
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled
Command Modes
Redundancy configuration
Command History
This table includes the following release-specific history entries:
12.2(24)SV
This command was introduced.
12.2(29)SV
Added support for the automatic syncing of performance history counters.
Usage Guidelines
Use this command to enable or disable automatic synchronizing of the traffic statistics, performance monitoring counters, and performance history counters without affecting the following types of synchronization:
•
Startup configuration
•
•
Examples
The following example shows how to disable automatic synchronizing of the traffic statistics and performance counters.
Switch#configure terminalSwitch(config)# redundancySwitch(config-red)# no auto-sync counters interfaceRelated Commands
auto-sync running-config
To selectively enable only automatic synchronizing of the running configuration on the active processor to the standby CPU switch module, use the auto-sync running-config command. To disable automatic synchronizing of the running configuration, use the no form of this command.
auto-sync running-config
no auto-sync running-config
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled
Command Modes
Redundancy configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to enable or disable automatic synchronizing of the running configuration without affecting the following types of synchronization:
•
•
When a CPU switch module switchover occurs, the standby CPU switch module normally uses the running configuration rather than the startup configuration. However, if auto-sync running-config is disabled when a CPU switch module switchover occurs, the standby CPU switch module uses the startup configuration.
In maintenance mode, all database synchronizing to the standby CPU switch module is disabled even if auto-sync running-config is enabled.
Examples
The following example shows how to disable automatic synchronizing of the running configuration.
Switch#configure terminalSwitch(config)# redundancySwitch(config-red)# no auto-sync running-configRelated Commands
auto-sync startup-config
To selectively enable only automatic synchronizing of the startup configuration to the standby CPU switch module, use the auto-sync startup-config command. To disable automatic synchronizing of the startup configuration, use the no form of this command.
auto-sync startup-config
no auto-sync startup-config
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled
Command Modes
Redundancy configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to enable or disable only automatic synchronizing of the startup configuration without affecting the following synchronization:
•
•
In maintenance mode, all database synchronizing to the standby CPU switch module is disabled even if auto-sync startup-config is enabled.
Examples
The following example shows how to disable automatic synchronizing of the startup configuration.
Switch#configure terminalSwitch(config)# redundancySwitch(config-red)# no auto-sync startup-configRelated Commands
clear redundancy
To clear redundancy history or counters, use the clear redundancy command.
clear redundancy {history | counters}
Syntax Description
history
Clears the redundancy event history log.
counters
Clears the redundancy internal operational counters.
Defaults
None
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to perform a one-time clear of the specified redundancy history or statistics database. This command may be useful for debugging or monitoring redundancy performance.
Examples
The following example shows how to clear the redundancy history log.
Switch# clear redundancy historyRelated Commands
Displays redundancy software counter information.
Displays redundancy software history information.
maintenance-mode
To disable all CPU switch module redundancy synchronization, use the maintenance-mode redundancy command. To reenable redundancy synchronization, use the no form of this command.
maintenance-mode
no maintenance-mode
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Redundancy configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
In maintenance mode, the active CPU switch module does not automatically synchronize information to the standby CPU switch module. No standby CPU switch module errors and alarms are reported to the active CPU switch module. The standby CPU switch module leaves the hot-standby mode, enters the negotiation state, and transitions to the cold-standby state.
When maintenance mode is disabled, the standby CPU switch module reloads until it reaches the hot-standby state.
Maintenance mode is useful for CPU switch module maintenance operations and system image troubleshooting.
Note
Examples
The following example shows how to enable maintenance mode redundancy.
Switch# configure terminalSwitch(config)# redundancySwitch(config-red)# maintenance-modeThis command will place the system in SIMPLEX mode [confirm] yRelated Commands
Enters redundancy configuration mode.
Displays CPU switch module redundancy status and configuration information.
redundancy
To switch to redundancy configuration mode, use the redundancy command.
redundancy
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
Global configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to gain access to both CPU switch module redundancy configuration commands and APS configuration commands.
Examples
The following example shows how to switch to redundancy configuration mode.
Switch#configure terminalSwitch(config)#redundancySwitch(config-red)#Related Commands
redundancy manual-sync
To cause an immediate one-time database update of the specified database information, use the redundancy manual-sync command.
redundancy manual-sync {running-config | startup-config | both}
Syntax Description
Defaults
None
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command is not usually required because automatic synchronization is enabled by default and, upon exiting global configuration mode, the running configuration is updated on the standby CPU switch module. (Exit global configuration mode by entering Ctrl-Z or end.) The startup configuration is updated when the copy command is issued.
If auto-synchronizing is disabled, the redundancy manual-sync command updates the standby processor database information to be identical with the active CPU switch module.
If the system is unable to complete the update, an error message is displayed.
This command is only allowed on the active CPU switch module.
Examples
The following example shows how to make the active CPU switch module send an update for both the running configuration and the startup configuration to the standby CPU switch module.
Switch# redundancy manual-sync bothRelated Commands
redundancy reload peer
To reload the standby CPU switch module, use the redundancy reload peer command.
redundancy reload peer
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to reload the standby (or peer) CPU switch module.
The active CPU switch module is allowed to reload a standby CPU switch module that is fully running the Cisco IOS software by using an NMI (non-maskable interrupt).
This command will not succeed on the active CPU switch module if the standby CPU switch module has not fully loaded its system IOS image and reached the hot-standby state.
This command cannot be entered on the standby CPU switch module.
Examples
The following example shows how to reload the standby CPU switch module.
Switch#redundancy reload peerReload peer [confirm] yPreparing to reload peerRelated Commands
redundancy reload shelf
To reload both redundant CPU switch modules, use the redundancy reload shelf command.
redundancy reload shelf
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command causes both CPU switch modules to reload.
Examples
The following example shows how to reload the entire shelf.
Switch#redundancy reload shelfReload the entire shelf [confirm] yPreparing to reload shelfRelated Commands
redundancy switch-activity
To manually switch activity from the active CPU switch module to the standby CPU switch module, use the redundancy switch-activity command.
redundancy switch-activity [force]
Syntax Description
force
Forces a switch of activity even when the standby CPU switch module has not reached the hot-standby state, or if some other software condition is preventing a normal switchover from occurring.
Defaults
The active CPU switch module switches over only if the standby CPU switch module has reached hot-standby mode.
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command must be issued on the active CPU switch module. It takes effect if the CPU switch module is in a state to allow switchover; that is, the standby CPU switch module is in the "Standby Hot" state and platform software is not temporarily disallowing the switchover.
Examples
The following example shows how to switch activity to the standby CPU switch module.
Switch#redundancy switch-activityPreparing to switch activityThis will reload the active unit and force a switch of activity [confirm] y01:40:35: %SYS-5-RELOAD: Reload requestedRelated Commands
show redundancy capability
To display capabilities of the active and standby CPU switch modules, use the show redundancy capability command.
show redundancy capability
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display hardware and functional versions of the various components. If the capabilities do not match, the system is running in a degraded redundancy mode.
Examples
The following example shows how to display capabilities for the active and standby CPU switch modules. (See Table 7-1 for field descriptions.)
Switch# show redundancy capabilityCPU capability supportActive CPU Sby CPU Sby Compat CPU capability description---------- ---------- ----------- ----------------------------------------96 MB 96 MB OK CPU DRAM size32 MB 32 MB OK CPU PMEM size512 KB 512 KB OK CPU NVRAM size16 MB 16 MB OK CPU Bootflash size3.5 3.5 OK CPU hardware major.minor version1.20 1.18 OK CPU functional major.minor versionLinecard driver major.minor versions, (counts: Active=18, Standby=18)Active CPU Sby CPU Sby Compat Drv ID Driver description---------- ---------- ----------- ------ -----------------------------------1.1 1.1 OK 0x1000 CPU w/o Switch Fabric1.1 1.1 OK 0x1001 Fixed Transponder, w/monitor1.1 1.1 OK 0x1002 Fixed Transponder, no monitor1.1 1.1 OK 0x1003 Pluggable Transponder, w/monitor1.1 1.1 OK 0x1004 Pluggable Transponder, no monitor1.1 1.1 OK 0x1005 Line Card Motherboard1.1 1.1 OK 0x1006 Backplane1.1 1.1 OK 0x1007 32-ch Mux/Demux1.1 1.1 OK 0x1008 Fixed 4-ch Mux/Demux, no OSC1.1 1.1 OK 0x1009 Fixed 8-ch Mux/Demux, no OSC1.1 1.1 OK 0x100A Modular 4-ch Mux/Demux, no OSC1.1 1.1 OK 0x100B Modular 8-ch Mux/Demux, no OSC1.1 1.1 OK 0x100C 32-ch Array Wave Guide1.1 1.1 OK 0x100D Mux/Demux Motherboard1.1 1.1 OK 0x100E Modular 4-ch Mux/Demux plus OSC1.1 1.1 OK 0x100F Modular 8-ch Mux/Demux plus OSC1.1 1.1 OK 0x1010 Mux-Demux Motherboard, no OSC1.1 1.1 OK 0x1011 Line Card Motherboard, no splitterSoftware sync client versions, listed as version range X-Y.X indicates the oldest peer version it can communicate with.Y indicates the current sync client version.Sync client counts: Active=2, Standby=2Active CPU Sby CPU Sby Compat Cl ID Redundancy Client description---------- ---------- ----------- ----- ------------------------------------ver 1-1 ver 1-1 OK 17 CPU Redundancyver 1-1 ver 1-1 OK 6 OIR ClientBackplane IDPROM comparisonBackplane IDPROM field Match Local CPU Peer CPU--------------------------- ----- -------------------- --------------------idversion YES 1 1magic YES 153 153card_type YES 4102 4102order_part_num_str YES N/A N/Adescription_str YES Manhattan_Backplane_PHASE_0Manhattan_Backplane_PHASE_0board_part_num_str YES 73-5655-03 73-5655-03board_revision_str YES 02 02serial_number_str YES TBC05031572 TBC05031572date_of_manufacture_str YES 02/16/2001 02/16/2001deviation_numbers_str YES 0 0manufacturing_use YES 0 0rma_number_str YES 0x00 0x00rma_failure_code_str YES 0x00 0x00oem_str YES Cisco_Systems Cisco_Systemsclei_str YESsnmp_oid_substr NO 0schematic_num_str YES 92-4113-03 92-4113-03hardware_major_version YES 3 3hardware_minor_version YES 0 0engineering_use_str YES 1 1crc16 OK 5913 24184user_track_string NO labdiagst YES ^A ^Aboard_specific_revision YES 1 1board_specific_magic_number YES 153 153board_specific_length YES 56 56mac_address_block_size YES 16 16mac_address_base_str YES 0000164428fb0 0000164428fb0cpu_number OK 1 1optical_backplane_type YES 255 255
Table 7-1 show redundancy capability Field Descriptions
Active CPU
Shows the following information for the active CPU switch module:
•
•
•
•
•
•
Sby CPU
Shows information for the standby CPU switch module. See the " Active CPU" description above.
Sby Compat
Indicates whether the standby CPU switch module is compatible with the active CPU switch module.
CPU capability description
Shows the capability descriptions for the active and standby CPU switch modules. See the " Active CPU" description above.
Linecard driver major.minor versions
Shows the number of line card drivers.
Drv ID
Shows the driver ID.
Driver description
Shows the driver description.
Software sync client versions
Shows the redundancy client version in the range X-Y, where:
•
•
Also shows the sync client counts.
Cl ID
Shows the client ID.
Redundancy Client description
Shows the redundancy client descriptions.
Related Commands
show redundancy clients
To display a list of internal redundancy clients, use the show redundancy clients command.
show redundancy clients
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display information about the software subsystems that are clients of the platform-independent RF (Redundancy Facility) subsystem. Subsystems that need to synchronize information from the active CPU switch module to the standby CPU switch module (or vice versa) are registered as clients of the RF.
This client information can be used to debug redundancy software.
Examples
The following example shows how to display a list of internal redundancy clients. (See Table 7-2 for field descriptions.)
Switch# show redundancy clientsclientID = 0 clientSeq = 0 RF_INTERNAL_MSGclientID = 6 clientSeq = 16 OIR ClientclientID = 17 clientSeq = 40 CPU RedundancyclientID = 19 clientSeq = 9999 RF_LAST_CLIENT
Related Commands
show redundancy counters
To display internal redundancy software counters, use the show redundancy counters command.
show redundancy counters
Syntax Description
This command has no other arguments or keywords
Defaults
None
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display internal redundancy software counter information, which can be used to debug redundancy software.
Examples
The following example shows how to display internal redundancy software counter information. (See Table 7-3 for field descriptions.)
Switch# show redundancy countersRedundancy Facility OMscomm link up = 1comm link down down = 0invalid client tx = 0null 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 = 656tx buffers unavailable = 0buffers rx = 1302buffer release errors = 0duplicate client registers = 0failed to register client = 0Invalid client syncs = 0
Related Commands
show redundancy history
To display internal redundancy software history, use the show redundancy history command.
show redundancy history
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display the internal redundancy software history log, which can be used to debug redundancy software.
Examples
The following example shows how to display the internal redundancy software history log, which can be useful for debugging redundancy software. (See Table 7-4 for field descriptions.)
Switch# show redundancy historyRedundancy Facility Event Log:00:00:00 client added: RF_INTERNAL_MSG(0) seq=000:00:00 client added: RF_LAST_CLIENT(19) seq=999900:00:16 client added: CPU Redundancy(17) seq=4000:00:16 *my state = INITIALIZATION(2) *peer state = DISABLED(1)00:00:16 RF_PROG_INITIALIZATION(0) RF_INTERNAL_MSG(0) op=0 rc=1100:00:16 RF_PROG_INITIALIZATION(0) CPU Redundancy(17) op=0 rc=1100:00:16 RF_PROG_INITIALIZATION(0) RF_LAST_CLIENT(19) op=0 rc=1100:00:16 *my state = NEGOTIATION(3) peer state = DISABLED(1)00:00:16 RF_STATUS_PEER_PRESENCE(12) op=000:00:16 RF_EVENT_GO_ACTIVE(28) op=000:00:16 *my state = ACTIVE-FAST(9) peer state = DISABLED(1)00:00:16 RF_STATUS_SPLIT_ENABLE(15) CPU Redundancy(17) op=000:00:16 RF_PROG_ACTIVE_FAST(6) RF_INTERNAL_MSG(0) op=0 rc=1100:00:16 RF_PROG_ACTIVE_FAST(6) CPU Redundancy(17) op=0 rc=1100:00:16 RF_PROG_ACTIVE_FAST(6) RF_LAST_CLIENT(19) op=0 rc=1100:00:16 *my state = ACTIVE-DRAIN(10) peer state = DISABLED(1)00:00:16 RF_PROG_ACTIVE_DRAIN(7) RF_INTERNAL_MSG(0) op=0 rc=1100:00:16 RF_PROG_ACTIVE_DRAIN(7) CPU Redundancy(17) op=0 rc=1100:00:16 RF_PROG_ACTIVE_DRAIN(7) RF_LAST_CLIENT(19) op=0 rc=1100:00:16 *my state = ACTIVE_PRECONFIG(11) peer state = DISABLED(1)00:00:16 RF_PROG_ACTIVE_PRECONFIG(8) RF_INTERNAL_MSG(0) op=0 rc=1100:00:16 RF_PROG_ACTIVE_PRECONFIG(8) CPU Redundancy(17) op=0 rc=1100:00:16 RF_PROG_ACTIVE_PRECONFIG(8) RF_LAST_CLIENT(19) op=0 rc=1100:00:16 *my state = ACTIVE_POSTCONFIG(12) peer state = DISABLED(1)00:00:16 RF_PROG_ACTIVE_POSTCONFIG(9) RF_INTERNAL_MSG(0) op=0 rc=1100:00:16 RF_PROG_ACTIVE_POSTCONFIG(9) CPU Redundancy(17) op=0 rc=1100:00:16 RF_PROG_ACTIVE_POSTCONFIG(9) RF_LAST_CLIENT(19) op=0 rc=1100:00:16 *my state = ACTIVE(13) peer state = DISABLED(1)00:00:16 RF_PROG_ACTIVE(10) RF_INTERNAL_MSG(0) op=0 rc=1100:00:16 RF_PROG_ACTIVE(10) CPU Redundancy(17) op=0 rc=1100:00:16 RF_PROG_ACTIVE(10) RF_LAST_CLIENT(19) op=0 rc=1100:00:16 client added: OIR Client(6) seq=1600:00:19 RF_STATUS_PEER_PRESENCE(12) op=000:00:36 Configuration parsing complete00:00:36 System initialization complete
Related Commands
show redundancy running-config-file
To display the running configuration on the standby CPU switch module, use the show redundancy running-config-file command.
show redundancy running-config-file
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command is only available on the standby CPU switch module. It shows the stored running-config file that has been synchronized from the active CPU switch module, which will be applied as the system configuration during the next standby to active transition.
If auto-synchronization is disabled for the running-config-file on the active CPU switch module, or if the IPC (interprocessor communications) is down, this command displays the message
running-config-file is not currently validand does not show the running-config-file.
Note
Examples
The following example displays the running-config file on the standby CPU switch module. (See Table 7-5 for field descriptions.)
sby-Switch# show redundancy running-config-file!version 12.1no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname Switch!boot system flash bootflash:ons15530-i-mzboot bootldr slot0:ons15530-i-mz<Information deleted>
Related Commands
show redundancy states
To display internal redundancy software state information, use the show redundancy states command.
show redundancy states
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display internal redundancy software state information, which may be used to debug redundancy software.
Examples
The following example shows how to display internal redundancy software state information. (See Table 7-6 for field descriptions.)
Switch> show redundancy statesmy state = 13 -ACTIVEpeer state = 8 -STANDBY HOTMode = DuplexUnit ID = 6Split Mode = DisabledManual Swact = EnabledCommunications = Upclient count = 5client_notification_TMR = 30000 millisecondskeep_alive TMR = 5000 millisecondskeep_alive count = 1keep_alive threshold = 10RF debug mask = 0x0
Related Commands
show redundancy summary
To display a summary of active and standby CPU switch module redundancy information, use the show redundancy summary command.
show redundancy summary
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display a summary of redundancy-related information, including active and standby slots, uptimes, images, and current alarms. This information is useful for troubleshooting CPU switch module redundancy problems.
Examples
The following example shows how to display a summary of redundancy-related information for the system. (See Table 7-7 for field descriptions.)
Switch# show redundancy summaryRedundant system information----------------------------Available Uptime: 12 minutesTime since last switchover: 6 minutesSwitchover Count: 2Inter-CPU Communication State:UPLast Restart Reason: Switch overReported Switchover Reason: User initiatedSoftware state at switchover: STANDBY HOTLast Running Config sync: 2 minutesRunning Config sync status: In SyncLast Startup Config sync: 2 minutesStartup Config sync status: In SyncThis CPU is the Active CPU.-------------------------------Slot: 6Time since CPU Initialized: 8 minutesImage Version: ONS-15530 Software (ONS15530-I-M), Experimental Version 12.1(20010824:021324) [ffrazer-lh2 106]Image File: tftp://171.69.1.129/ffrazer/ons15530-i-mzSoftware Redundancy State: ACTIVEHardware State: ACTIVEHardware Severity: 0Peer CPU is the Standby CPU.-------------------------------Slot: 7Time since CPU Initialized: 2 minutesImage Version: ONS-15530 Software (ONS15530-I-M), Experimental Version 12.1(20010824:021324) [ffrazer-lh2 106]Image File (on sby-CPU): tftp://171.69.1.129/ffrazer/ons15530-i-mzSoftware Redundancy State: STANDBY HOTHardware State: STANDBYHardware Severity: 0
Related Commands
standby privilege-mode enable
To enable access to privileged EXEC mode from the standby CPU switch module CLI, use the standby privilege-mode enable command. To revert to the default state, use the no form of the command.
standby privilege-mode enable
no standby privilege-mode enable
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Redundancy configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command must be entered on the active CPU switch module CLI before you can access privileged EXEC mode on the standby CPU switch module CLI.
Examples
The following example shows how to enable access to privileged EXEC mode on the standby CPU switch processor module.
Switch(config-red)# standby privilege-mode enableRelated Commands
Posted: Mon Feb 27 03:18:27 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
