Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual page 240

Nondisruptive Upgrades on Fabric and Modular Switches
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Nondisruptive upgrades on these fabric switches take down the control plane for not more than 80
seconds. In some cases, when the upgrade has progressed past the point at which it cannot be stopped
gracefully, or if a failure occurs, the software upgrade may be disruptive.
During the upgrade the control plane is down, but the data plane remains up. So new devices will be
Note
unable to log in to the fabric via the control plane, but existing devices will not experience any disruption
of traffic via the data plane.
Before attempting to upgrade any software images on these fabric switches, follow these guidelines:
•
•
•
•
•
•
•
•
•
To ensure that you can view the entire upgrade process, it is recommended that you perform the upgrade
via the console port; performing the upgrade in this way also enables you to log your session to a file (in
case you need it later for troubleshooting). Also, Telnet sessions are lost when the switch is rebooted, so
if you wish to view the process in its entirety, use the console port instead.
Example 8-11
switch# install all kickstart bootflash:boot-fs9124 system bootflash:isan-164
Verifying image bootflash:/boot-fs9124 for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/isan-164 for boot variable "system".
[####################] 100% -- SUCCESS
Cisco MDS 9000 Family CLI Configuration Guide
8-22
During the upgrade, the fabric must be stable. None of the following configuration activities are
allowed:
Zoning changes
–
Telnet sessions
–
Schedule changes
–
Switch cabling
–
– Addition or removal of physical devices
Configure the FSPF timers to the default value of 20 seconds.
If there are any CFS commits pending in the fabric, the upgrade is aborted.
If there is a zone server merge in progress, the upgrade is aborted.
If the upgrade is aborted due to a service not being ready for the upgrade, you are prompted to enter
the show install all failure-reason command to identify the reason why.
If there is insufficient space available in the system to load the new images, then you will be notified
via the compatibility table. At this point, you need to either abort the upgrade or proceed with a
disruptive upgrade.
Issue the no logging level all command before the commencing with the upgrade. Failing to issue
this command could result in a failure due to the debug system log messages being printed and
potentially resulting in control plane downtime exceeding 80 seconds.
If VRRP is running on the mgmt0 interface, and the switch being upgraded is the master, then a new
master is selected. This cannot be avoided because the mgmt0 interface goes down when the control
plane goes down.
On the Cisco MDS 18/4-port multiservice module, upgrades of the 4-Gigabit Ethernet ports for the
hybrid Supervisor 18/4 line card will be disruptive.
Failed Nondisruptive Upgrade Due to Insufficient Resources
Chapter 8 Software Images
OL-18084-01, Cisco MDS NX-OS Release 4.x