Cisco Cisco Nexus 5010 Switch Guida All'Installazione
30
Cisco Nexus 5500 Series NX-OS Software Upgrade and Downgrade Guide, Release 6.0
OL-27890-03
Disruptive Installation Process
4.
The current state is saved.
5.
The system unloads and runs the new image.
6.
The stateful restart of the system software and application occurs.
7.
The installer resumes with the new image.
8.
The FEXs are upgraded sequentially. The upgrade completes on the single-homed FEXs and a sanity
check is performed on the dual-homed FEXs.
check is performed on the dual-homed FEXs.
Note
The dual-homed FEXs were upgraded by the primary switch.
9.
The configuration is unlocked on the primary and secondary switches.
10.
The installation is complete.
Disruptive Installation Process
The following lists the situations where a nondisruptive ISSU might not be possible when upgrading a
Cisco Nexus device:
Cisco Nexus device:
•
The topology and/or features are not ISSU ready. See the
for more information.
•
The current release or target release is lower than Release 5.0(3)N1(1). An ISSU can work only
when both the current and target releases are equal or later than Release 5.0(3)N1(1).
when both the current and target releases are equal or later than Release 5.0(3)N1(1).
Note
To use the ISSU process for Release 5.0(2)N1(1) through Release 5.0(3)N2(1a), you must first
upgrade to Release 5.2(1)N1(1). After that, use the ISSU process to upgrade to Release
6.0(2)N2(4).
upgrade to Release 5.2(1)N1(1). After that, use the ISSU process to upgrade to Release
6.0(2)N2(4).
•
The installation is a downgrade, such as a higher release to a lower release, unless stated otherwise
in the
in the
.
•
You want to do a disruptive upgrade. See the
Forcing an Upgrade
You can choose to do a disruptive upgrade if one of the ISSU conditions are not met. One additional
reason where you might choose to do a disruptive upgrade is when FEXs are upgraded in a rolling
fashion (one FEX at a time), which requires a longer maintenance window. With a disruptive upgrade,
all the connected FEXs are upgraded simultaneously, so the maintenance window can be shorter. If you
need a shorter maintenance window (with traffic disruption), you can force a disruptive upgrade even if
an ISSU can be leveraged. It is important to note the possibility of an outage if you do a disruptive
upgrade.
reason where you might choose to do a disruptive upgrade is when FEXs are upgraded in a rolling
fashion (one FEX at a time), which requires a longer maintenance window. With a disruptive upgrade,
all the connected FEXs are upgraded simultaneously, so the maintenance window can be shorter. If you
need a shorter maintenance window (with traffic disruption), you can force a disruptive upgrade even if
an ISSU can be leveraged. It is important to note the possibility of an outage if you do a disruptive
upgrade.
switch# install all force kickstart bootflash:/kickstart_image.bin system
bootflash:/system_image.bin
Installer is forced disruptive
Verifying image bootflash:/kickstart_image.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS