Efsu restrictions and guidelines – Cisco 6500 User Manual
Page 56
4-56
Cisco IOS Software Configuration Guide, Release 12.2SX
OL-13013-06
Chapter 4 Configuring Virtual Switching Systems
Upgrading a VSS
eFSU Restrictions and Guidelines
When performing an eFSU, note the following guidelines and restrictions:
•
7600-SIP-400 is powered down during an eFSU and is powered up at the
at
.
•
An eFSU can install a full image upgrade or a patch upgrade. Any patch upgrade will be installed
by the same process as a full image upgrade, regardless of whether the patch requires a reload or a
process restart.
•
The new image file must reside in the file system of the supervisor engine in each chassis before the
eFSU can be initiated. The issu commands will accept only global file system names (for example,
disk0: or sup-bootdisk:). The issu commands will not accept switch number-specific file system
names (for example, sw1-slot5-disk0:).
•
When preparing for the eFSU, do not change the boot variable. Although a boot variable change is
required in the FSU (RPR) procedure, changing the boot variable in the eFSU procedure will cause
the CurrentVersion variable to be inconsistent, preventing execution of the eFSU.
•
The issu commands for a VSS eFSU upgrade are similar to those for a single-chassis (standalone)
eFSU, as described in the
“Performing an Enhanced Fast Software Upgrade” section on page 5-5
,
with the following differences:
–
Where the standalone issu commands accept an argument of slot number, the VSS issu
commands accept a switch and slot number, in the format of switch/slot (for example, 1/5 refers
to switch 1, slot 5).
–
For a normal VSS eFSU, it is not necessary to specify a switch or slot number when entering
the VSS issu commands.
•
You cannot change the rollback timer period during the eFSU process.
•
During the eFSU process, do not perform any manual switchover other than those caused by the issu
commands.
•
During the eFSU process, do not perform an online insertion or removal (OIR) of any module.
•
During an eFSU downgrade, if the process is aborted (either due to an MCL error or by entering the
abortversion command) just after executing the loadversion command, the SSO VSS standby is
reloaded with the original image but the SSO VSS standby’s ICS is not because the bootvar of the
SSO VSS standby’s ICS is not modified during an abort executed after the loadversion command.
•
Images with different feature sets fail the eFSU compatibility check, regardless of the software
release.
•
The eFSU feature does not support upgrades or downgrades between modular and non-modular IOS
versions.
•
The eFSU feature does not support upgrades or downgrades between installed and binary modes of
modular IOS. The Installed mode was removed after Cisco IOS Release 12.2(33)SXI3.
•
Before you start a downgrade with eFSU (reverting to an earlier version of Cisco IOS software),
remove configurations and disable any features or functions that are not supported in the earlier
version. Otherwise the configuration files fail to synchronize and the standby supervisor engine
reloads.
•
The eFSU upgrade feature works with NSF/SSO. Software features that do not support NSF/SSO
stop operating until after the software upgrade switchover, when they come back online.
•
Images with release dates more than 18 months apart are not supported for eFSU. See the
verify compatibility.