Cisco Cisco Nexus 5010 Switch Guida All'Installazione
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
29
Cisco Nexus 5000 Series NX-OS Software Upgrade and Downgrade Guide, Release 5.2
Disruptive Installation Process
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 conditions where a nondisruptive ISSU might not be possible when upgrading a
Cisco Nexus 5000 Series access layer switch:
Cisco Nexus 5000 Series access layer switch:
•
The topology and/or features are not ISSU ready. See the section on ISSU prerequisites for more
information.
information.
•
The current release or target release is lower than 5.0(3)N1(1). An ISSU can work only when both
the current and target releases are equal or later than 5.0(3)N1(1).
the current and target releases are equal or later than 5.0(3)N1(1).
Note
To use the ISSU process for Release 4.2(1)N1(1) through Release 5.0(2)N2(1a), you must first
upgrade to Release 5.1(3)N1(1). After that, use the ISSU process to upgrade to Release 5.2.
upgrade to Release 5.1(3)N1(1). After that, use the ISSU process to upgrade to Release 5.2.
•
The installation is a downgrade, such as a higher release to a lower release, unless stated otherwise
in Release specific Information section.
in Release specific Information section.
•
You want to do a disruptive upgrade. See the Forcing an Upgrade section.
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
Verifying image bootflash:/system_image.bin for boot variable "system".
...
You can also add force at the end of the install all command as follows:
s
witch # install all kickstart bootflash:/kickstart_image.bin system
bootflash:/system_image.bin force