Cisco Systems 4500 Switching to the Standby Supervisor Engine

5-21
Software Configuration Guide—Release 15(02)SG
OL-23818-01
Chapter 5 Configuring the Cisco IOS In-Service Software Upgrade Process Performing the ISSU Process
The following example shows the redundancy mode as RPR:
Switch# show redundancy states
my state = 13 -ACTIVE
peer state = 4 -STANDBY COLD
Mode = Duplex
Unit = Primary
Unit ID = 1
Redundancy Mode (Operational) = RPR
Redundancy Mode (Configured) = Stateful Switchover
Redundancy State = RPR
Maintenance Mode = Disabled
Manual Swact = enabled
Communications = Up
client count = 39
client_notification_TMR = 240000 milliseconds
keep_alive TMR = 9000 milliseconds
keep_alive count = 1
keep_alive threshold = 18
RF debug mask = 0x0
Switching to the Standby Supervisor Engine
This task describes how to switchover to the standby supervisor engine, which is running the new Cisco
IOS software image.
Perform this task at the active supervisor engine:
This example shows how to cause a switchover to the former standby supervisor engine (slot 2), reset
the former active supervisor engine and reload it with the old image so it becomes the standby supervisor
engine:
Switch> enable
Switch# issu runversion 2 slavebootflash:new_image
This command will reload the Active unit. Proceed ? [confirm]
Command or Action Purpose
Step 1 Switch> enable Enables privileged EXEC mode.
• Enter your password if prompted.
Step 2 Switch# issu runversion standby-slot
[standby-image-new] Forces a switchover from the active to the standby
supervisor engine and reloads the former active (current
standby) supervisor engines with the old image.
When you enter the issu runversion command, an SSO
switchover is performed, and NSF procedures are invoked if
configured.
Step 3 Switch# show issu state [detail]Displays the state of the during the ISSU process. At this
point in the ISSU process, use this command to check that
a switchover occurs to slot 2.
Step 4 Switch# show redundancy [states]Displays redundancy facility state information.