Cisco Cisco Nexus 5010 Switch Guida All'Installazione

You can receive descriptive information about the intended changes to your system before you 
continue with the installation. For example, it identifies potential disruptive upgrades.

You can continue or cancel the upgrade when you see this question (the default is no):

Do you want to continue (y/n) [n] : y

You can upgrade the Cisco NX-OS software using a nondisruptive procedure, when supported.

The command automatically checks the image integrity, which includes the running kickstart and 
system images. The command sets the kickstart and system boot variables.

The command performs a platform validity check to verify that a wrong image is not used.

Pressing Ctrl-C gracefully ends the install all command. The command sequence completes the 
update step in progress and returns to the EXEC prompt.

After entering the install all command, if any step in the sequence fails, the upgrade ends.

The following message appears to warn you about the impact of upgrading the power sequencer:

Warning: please do not remove or power off the module at this time.

Note: Power-seq upgrade needs a power-cycle to take into effect.

After a successful power sequence upgrade, you must switch off the power to the system and 
then power it up.

 You can enter the force keyword to perform a disruptive upgrade. For information on forcing an 
upgrade, see 

Changes to BIOS and power sequencers are rare; however, when they occur, they are included in the 
Cisco NX-OS system image, and the BIOS and power sequencer are upgraded. The summary displayed 
by the installer during the installation process indicates the current version of the BIOS and power 
sequencer and the target version.

After a successful power sequence upgrade, you must switch off the power to the system and 
then power it up.

Cisco NX-OS supports in-service software upgrades (ISSUs) that allow a Cisco Nexus device and any 
connected FEXs to be upgraded without any traffic disruption (with a brief control plane disruption). A 
few conditions have to be met for the system to be upgraded through an ISSU process—the access layer 
topology should be ISSU compliant, the current and target versions should be ISSU capable, and the 
network should be stable.

If the conditions required for an ISSU are not met or if you intend to downgrade the software version, 
the installation process is disruptive. For example, the Cisco Nexus device and any connected FEXs are 
rebooted, which causes a disruption. If Cisco’s virtual port channel (vPC) is configured on Cisco Nexus 
devices, it is possible to achieve an upgrade/downgrade with very minimal traffic disruption to 
servers/hosts.