Cisco Cisco Nexus 5010 Switch Installation Guide
30
Cisco Nexus 5500 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.0(8)N1(1)
Disruptive Installation Process
software that are designed to allow an upgraded dual-home FEX to interoperate with vPC secondary
switches running the original version of Cisco NX-OS while the primary switch is running the upgrade
version.
switches running the original version of Cisco NX-OS while the primary switch is running the upgrade
version.
Upgrade Process for a vPC Topology on the Secondary Switch
The following list summarizes the upgrade process on a secondary switch in a vPC topology.
1.
The install all command issued on the vPC second switch triggers the installation upgrade.
2.
The compatibility checks display the impact of the upgrade.
3.
The installation proceeds or not based on the upgrade impact.
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
Note
Doing a disruptive upgrade between incompatible images will result in loss of certain configurations
such as unified ports, breakout, and FEX configurations. See
such as unified ports, breakout, and FEX configurations. See
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.2(1)N1(1). An ISSU can work only
when both the current and target releases are equal or later than Release 5.2(1)N1(1).
when both the current and target releases are equal or later than Release 5.2(1)N1(1).
Note
To use the ISSU process for Release 5.0(2)N1(1) through Release 5.1(3)N2(1c), you must first
upgrade to Release 5.2(1)N1(1). After that, use the ISSU process to upgrade to Release
7.0(8)N1(1).
upgrade to Release 5.2(1)N1(1). After that, use the ISSU process to upgrade to Release
7.0(8)N1(1).
•
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