Cisco 6500 - Manual (Page 61)

4-61
Cisco IOS Software Configuration Guide, Release 12.2SX
OL-13013-06
Chapter 4 Configuring Virtual Switching Systems
Upgrading a VSS
If you intend to bring up the ICS supervisor engine with Cisco IOS Release 12.2(33)SXI4, you will need
to manually boot up the ICS supervisor engine after the eFSU cycle is complete.
Performing an eFSU Upgrade from Cisco IOS Release 12.2(33)SXI4 to Future Cisco IOS Releases
To perform an eFSU upgrade of a VSS from Cisco IOS Release 12.2(33)SXI4 to a future Cisco IOS
Release, perform this task:
Step 6 Router# issu commitversion Loads the new software image onto the standby chassis.
Step 7 Router# show issu state [switch/slot][detail] Verifies the status of the upgrade process. If the upgrade
was successful, both the active and standby chassis are
running the new software version.
Command Purpose
Command Purpose
Step 1 Router# copy tftp disk_name Uses TFTP to copy the new software image to flash memory
on the active and standby chassis (disk0: and slavedisk0:)
and to the ICSs, if they exist. Answer the prompts to
identify the name and location of the new software image.
Step 2 Router# show issu state [switch/slot] [detail] (Optional) Verifies that the VSS is ready to run the eFSU.
Note You can use the show issu state command at any
stage of the upgrade to verify the progress and status
of the upgrade.
Step 3 Router# switch virtual in-chassis standby
switch [disable | enable]
(Optional) Includes or removes the ICS, from the eFSU
cycle. This command must be executed before the start of
the eFSU cycle even if the ICS is in ROMMON.
Step 4 Router# issu loadversion
[active_switch/slot] active-image
[standby_switch/slot] standby-image
Starts the upgrade process by loading the new software
image onto the standby chassis. The image name includes
the path of the target image to be loaded, in the format
devicename:filename.
It may take several seconds for the new image to load and
for the standby chassis to transition to SSO mode.
Note This command is not extended for the ICS. The file
system mentioned for the ICA is used for the
respective ICS. For example, if the issu
loadversion disk0:image_name
slavesup-bootdisk:image_name command is
executed the loadversion command is accepted. The
presence of the image is checked in the disk0: for
the active supervisor engine (both the ICA and ICS)
and the SPs bootdisk for the SSO standby (both the
ICA and ICS).