Cisco Cisco Nexus 5010 Switch Guida All'Installazione
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
34
Cisco Nexus 5600 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.1(1)N1(1)
Forcing an Upgrade
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 the force keyword at the end of the install all command as follows:
switch # install all kickstart bootflash:/kickstart_image.bin system
bootflash:/system_image.bin force
Installer is forced disruptive
Verifying image bootflash:/kickstart_image.bin for boot variable "kickstart".
...
Minimizing the Impact of a Disruptive Upgrade
A non-ISSU upgrade is a disruptive upgrade that results in the reload of the Cisco Nexus device and the
Fabric Extenders. The reload is a cold reboot that brings down the control plan and the data plane. The
reload causes disruptions to the connected servers and hosts. When a vPC is deployed in the access layer,
it is possible to minimize the impact of a non-ISSU upgrade. When one of the vPC switches is being
reset during the upgrade process, all the server traffic can flow through its vPC peer.
Fabric Extenders. The reload is a cold reboot that brings down the control plan and the data plane. The
reload causes disruptions to the connected servers and hosts. When a vPC is deployed in the access layer,
it is possible to minimize the impact of a non-ISSU upgrade. When one of the vPC switches is being
reset during the upgrade process, all the server traffic can flow through its vPC peer.
Upgrading a Direct vPC or a Single-Homed FEX Access Layer
The following figures show topologies in which the access layer includes a vPC configuration to hosts
or downstream switches.
or downstream switches.