Cisco Cisco Nexus 5010 Switch Installation Guide
3
Cisco Nexus 5500 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.0(8)N1(1)
Upgrade Guidelines
Upgrade Guidelines
When upgrading system software, follow these guidelines:
•
Configuration changes
You cannot enter global configuration mode during an upgrade. You should save, commit, or discard
any active configuration sessions before you upgrade or downgrade the Cisco NX-OS software
image. The active configuration session is deleted without a warning during a reload.
any active configuration sessions before you upgrade or downgrade the Cisco NX-OS software
image. The active configuration session is deleted without a warning during a reload.
Use the show configuration session summary command to verify that there are no active
configuration sessions.
configuration sessions.
switch# show configuration session summary
There are no active configuration sessions
For more information on configuration sessions, see the System Management Configuration Guide
for your platform.
for your platform.
Note
CLI and SNMP configuration change requests are denied during an in-service software
upgrade (ISSU).
upgrade (ISSU).
•
Topology—You should make topology changes, such as Spanning Tree Protocol (STP) or Fiber
Channel (FC) fabric changes, that affect zoning, Fabric Shortest Path First (FSPF), or FC domains
before you perform an upgrade. You should perform module installations or removals only before
or after an upgrade.
Channel (FC) fabric changes, that affect zoning, Fabric Shortest Path First (FSPF), or FC domains
before you perform an upgrade. You should perform module installations or removals only before
or after an upgrade.
•
Scheduling—You should upgrade when your network is stable and steady. Ensure that everyone who
has access to the switch or the network is not configuring the switch or the network during this time.
You cannot configure a switch during an upgrade.
has access to the switch or the network is not configuring the switch or the network during this time.
You cannot configure a switch during an upgrade.
•
Space—Verify that sufficient space is available in the location where you are copying the images.
The internal bootflash requires approximately 200 MB of free space.
The internal bootflash requires approximately 200 MB of free space.
•
Hardware—Avoid power interruptions during an installation procedure. Power interruptions can
corrupt the software image.
corrupt the software image.
•
Connectivity to remote servers—Configure the IPv4 address or IPv6 address for the 10/100/1000
BASE-T Ethernet port connection (interface mgmt0). Ensure that the switch has a route to the
remote server. The switch and the remote server must be in the same subnetwork if you do not have
a router to route traffic between subnets.
BASE-T Ethernet port connection (interface mgmt0). Ensure that the switch has a route to the
remote server. The switch and the remote server must be in the same subnetwork if you do not have
a router to route traffic between subnets.
•
Software image—Ensure that the specified system and kickstart images are compatible with each
other as follows:
other as follows:
–
If the kickstart image is not specified, the switch uses the current running kickstart image.
–
If you specify a different system image, ensure that it is compatible with the running kickstart
image.
image.
•
Retrieve compatible images in one of two ways:
–
Locally—Images are locally available on the switch.
–
Remotely—Images are in a remote location and you specify the destination by using the remote
server parameters and the filename to be used locally.
server parameters and the filename to be used locally.
•
Command—Use the following commands to prepare for and install the new software:
–
Use the ping command to verify connectivity to the remote server.