Table Of Contents
Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 4.0
About In-Service Software Upgrades on Devices with Dual Supervisor Modules
Prerequisites for Upgrading the Cisco NX-OS Software
Cisco NX-OS Software Upgrade Guidelines
Upgrading Cisco NX-OS Software
Upgrading a Device with Dual Supervisors
Benefits of Using the install all Command
Upgrading a Device with a Single Supervisor
Downgrading from a Higher Release
Example Outputs from Cisco NX-OS Software Upgrades
Example Nondisruptive Upgrade of an Device with Dual Supervisors
Example Disruptive Upgrade of an Device with Dual Supervisors
Example Upgrade of a Device with a Single Supervisor
Obtaining Documentation and Submitting a Service Request
Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 4.0
Updated Date: October 13, 2009
Part Number: OL-16505-01
This document provides information to upgrade or downgrade the Cisco NX-OS software.
![]()
Note
This document does not describe how to upgrade or downgrade the EPLD images. For information about EPLD images, see the Cisco Nexus 7000 Series FPGA/EPLD Upgrade Release Notes, Release 4.0.
This guide includes the following sections:
•
About In-Service Software Upgrades on Devices with Dual Supervisor Modules
•
Prerequisites for Upgrading the Cisco NX-OS Software
•
Upgrading Cisco NX-OS Software
•
Downgrading from a Higher Release
•
Example Outputs from Cisco NX-OS Software Upgrades
•
Obtaining Documentation and Submitting a Service Request
![]()
Tip
For information about the commands in this document, see the Cisco Nexus 7000 Series NX-OS Fundamentals Command Reference, Release 4.0.
![]()
CautionAll command-line interface (CLI) session examples provided in this document are intended only for reference. The actual session output differs based the configuration of the device.
About Software Images
Each device is shipped with the Cisco NX-OS software. The Cisco NX-OS software consists of two images—the kickstart image and the system image.
The software image install procedure is dependent on the following factors:
•
Software images—The kickstart and system image files reside in directories or folders that you can access from the Cisco NX-OS software prompt.
•
Image version—Each image file has a version.
•
Flash disks on the device—The bootflash: resides on the supervisor module and the CompactFlash disk is inserted into the slot0:, usb1, or usb2: device.
•
Supervisor modules—There are single or dual supervisor modules.
![]()
Note
On devices with dual supervisor modules, both supervisor modules must have connections on the console ports to maintain connectivity when switchovers occur during upgrades and downgrades. See the Cisco Nexus 7000 Series Hardware Installation and Reference Guide.
About In-Service Software Upgrades on Devices with Dual Supervisor Modules
The Cisco NX-OS software supports in-service software upgrades (ISSUs) on devices with dual supervisor modules. An ISSU can update the software images on your device without disrupting data traffic. Only control traffic is disrupted. If an ISSU will cause a disruption of data traffic, the Cisco NX-OS software warns you before proceeding so that you can stop the upgrade and reschedule it to a time that minimizes the impact on your network.
An ISSU updates the following images:
•
Kickstart image
•
System image
•
Supervisor module BIOS
•
Data module image
•
Data module BIOS
•
Connectivity management processor (CMP) image
•
CMP BIOS
Figure 1 shows the ISSU process.
Figure 1 ISSU Process
![]()
Figure 2 provides an example of the supervisor module status before and after an ISSU switchover.
Figure 2 Example of an ISSU Supervisor Module Switchover
![]()
Virtualization Support
When you upgrade the Cisco NX-OS software, you upgrade the software for all virtual device contexts (VDCs) on the physical device. You cannot upgrade the Cisco NX-OS software for an individual VDC.
Prerequisites for Upgrading the Cisco NX-OS Software
Upgrading the Cisco NX-OS software has the following prerequisite:
•
Save, commit, or discard any active configuration sessions before upgrading or downgrading the Cisco NX-OS software image on your device. On a device with dual supervisors, the active supervisor module cannot switchover to the standby supervisor module during the Cisco NX-OS software upgrade if you have an active configuration session.On a device with a single supervisor module, the Cisco NX-OS software deletes the active configuration session without warning when you reload the device.
Use the show configuration session summary command to verify that you have no active configuration sessions.
For more information on configuration sessions, see the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 4.0.
Cisco NX-OS Software Upgrade Guidelines
Before attempting to migrate to any software image version, follow these guidelines:
•
Scheduling
Schedule the upgrade when your network is stable and steady. Ensure that everyone who has access to the device or the network is not configuring the device or the network during this time. You cannot configure a device during an upgrade.
•
Space
Verify that sufficient space is available in the location where you are copying the images. This location includes the active and standby supervisor module bootflash: (internal to the device).
–
Standby supervisor module bootflash: file system.
–
Internal bootflash: has approximately 200 MB of free space available.
•
Hardware
Avoid power interruption during any install procedure, which can 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 the device has a route to the remote server. The device and the remote server must be in the same subnetwork if you do not have a router to route traffic between subnets.
•
Images
–
Ensure that the specified system and kickstart images are compatible with each other.
–
If the kickstart image is not specified, the device uses the current running kickstart image.
–
If you specify a different system image, ensure that it is compatible with the running kickstart image.
–
Retrieve 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 using the remote server parameters and the file name to be used locally.
•
Terminology
Table 1 summarizes terms used in the install all command output for checking compatibility.
•
Commands to use
–
Verify connectivity to the remote server using the ping command.
–
Ensure that the required space is available for the image files to be copied using the dir command.
–
We recommend the one-step install all command to upgrade your software. This command upgrades all modules in any Cisco NX-OS device.
–
Run only one installation on a device at a time.
–
Do not issue another command while running the installation.
–
Do the installation on the active supervisor module, not the standby supervisor module.
![]()
Note
If the I/O modules are not compatible with the software image you install on the supervisor module, some traffic disruption may occur in those modules, depending on your configuration. The install all command output identifies these commands. You can choose to proceed with the upgrade or end at this point.
•
Cisco TrustSec connected devices
Do not simultaneously upgrade or downgrade the images on devices connected with Cisco TrustSec. Allow the upgrade or downgrade to complete on one device before upgrading or downgrading the other device.
Upgrading Cisco NX-OS Software
Only users with the network-admin role can upgrade the Cisco NX-OS software image and only from the default VDC.
The upgrade procedure that you use depends on whether you device has a single supervisor module or has dual supervisor modules. To determine the number of supervisor modules on your device, use the show hardware and show redundancy commands.
![]()
Note
You can download the Cisco NX-OS software images to the bootflash:, slot0:, usb1:, or usb2: disks on your device. The examples in the procedures use bootflash:.
This section includes the following topics:
•
Upgrading a Device with Dual Supervisors
•
Upgrading a Device with a Single Supervisor
Upgrading a Device with Dual Supervisors
The install all command supports in-service software upgrade (ISSU) on devices that have dual supervisor modules and performs the following actions:
•
Determines whether the upgrade will be disruptive and asks if you wish to continue.
•
Copies the kickstart and system images to the standby supervisor module.
•
Sets the KICKSTART and SYSTEM boot variables.
•
Reloads the standby supervisor module with the new Cisco NX-OS software.
•
Reloads the active supervisor module with the new Cisco NX-OS software, which causes a switchover to the newly upgraded standby supervisor module.
![]()
Note
The install all command does not install the EPLD images.
This section includes the following topics:
•
Benefits of Using the install all Command
Benefits of Using the install all Command
The install all command provides the following benefits:
•
You can upgrade the entire device using just one command.
•
You can receive descriptive information on the intended changes to your system before you continue with the installation.
•
You have the option to cancel the command. Once the effects of the command are presented, you can continue or cancel when you see this question (the default is no):
Do you want to continue (y/n) [n] :y•
You can upgrade the entire device using the least disruptive procedure.
•
You can see the progress of this command on the console, Telnet, and SSH screens:
–
After a switchover process, you can see the progress from both the supervisor modules.
–
Before a switchover process, you can only see the progress from the active supervisor module.
•
The install all command automatically checks the image integrity. This includes the running kickstart and system images.
•
The install all command performs a platform validity check to verify that a wrong image is not used—for example, to check if a Cisco Nexus 5000 Series image is used inadvertently to upgrade a Cisco Nexus 7000 Series switch.
•
The Ctrl-c escape sequence gracefully ends the install all command. The command sequence completes the update step in progress and returns to the device prompt. (Other upgrade steps cannot be ended using Ctrl-c.)
•
After issuing the install all command, if any step in the sequence fails, the command completes the step in progress and ends.
For example, if an I/O module fails to be updated for any reason (for example, due to an unstable network state), then the command sequence disruptively updates that module and ends. In such cases, you can verify the problem on the affected switching module and upgrade the other I/O modules.
ISSU Failure Conditions
The following situations cause the installation to fail to complete:
•
If the standby supervisor module bootflash: file system does not have sufficient space to accept the updated image.
•
If the specified system and kickstart images are not compatible.
•
If the network or device is configured while the upgrade is in progress.
•
If the install all command is issued on the standby supervisor module.
•
If the install all command does not reference the default bootflash: in a dual supervisor module configuration.
•
If a module is removed while the upgrade is in progress.
•
If the device has any power disruption while the upgrade is in progress.
•
If the entire path for the remote server location is not specified accurately.
•
If images are incompatible after an upgrade. For example, an I/O module image may be incompatible with the system image, or a kickstart image may be incompatible with a system image. This is also identified by the show install all impact command in the compatibility check section of the output (under the Bootable column).
Upgrade Procedure Summary
The following summary procedure describes how to upgrade a device that has dual supervisor modules to the latest Cisco NX-OS software:
Step 1
Log in to the console port on both of the active and standby supervisor modules.
Step 2
Log in to Cisco.com and download the latest Cisco NX-OS kickstart and system images to a server.
Step 3
Download the Cisco NX-OS kickstart and system images from the server to your device using the copy command.
Step 4
Save the device configuration using the copy running-config startup-config vdc-all command.
Step 5
Enter the install all command at the active supervisor command prompt to upgrade the Cisco NX-OS software on your device.
![]()
Note
A supervisor module switchover occurs during the software installation.
![]()
Note
The install all command does not install the EPLD images.
Detailed Upgrade Procedure
To upgrade to the latest Cisco NX-OS software on a device with dual supervisors, follow these steps:
Step 1
Log in to the device on the console port connection on both of the active and standby supervisor modules.
Step 2
Log in to Cisco.com to access the links provided in this document. To log in to Cisco.com, go to the URL http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.
![]()
Note
Unregistered Cisco.com users cannot access the links provided in this document.
Step 3
Access the Software Download Center using this URL:
http://www.cisco.com/public/sw-center/index.shtml
Step 4
Navigate to the download site for your device.
You see links to the download images for your device.
Step 5
Select and download the kickstart and system software files to a server.
Step 6
Ensure that the required space is available for the image file(s) to be copied.
switch# dir bootflash:49152 Apr 16 14:43:39 2008 lost+found/80850712 Apr 04 15:57:44 2008 n7000-s1-dk9.4.0.1.bin22593024 Apr 04 15:52:56 2008 n7000-s1-kickstart.4.0.1.binUsage for bootflash://sup-local103492888 bytes used800604904 bytes free904097792 bytes total![]()
Tip
We recommend that you have the kickstart and system image files for at least one previous release of the Cisco NX-OS software on the device to use if the new image files do not load successfully.
Step 7
If you need more space on the active supervisor module, delete unnecessary files to make space available.
switch# delete bootflash:n7000-s1-kickstart.4.0.1.binswitch# delete bootflash:n7000-s1-dk9.4.0.1.binStep 8
Verify that there is space available on the standby supervisor module.
switch# dir bootflash://sup-standby/49152 Apr 16 14:43:39 2008 lost+found/80850712 Apr 04 15:57:44 2008 n7000-s1-dk9.4.0.1.bin22593024 Apr 04 15:52:56 2008 n7000-s1-kickstart.4.0.1.binUsage for bootflash://sup-standby103492888 bytes used800604904 bytes free904097792 bytes totalStep 9
If you need more space on the standby supervisor module, delete any unnecessary files to make space available.
switch# delete bootflash://sup-standby/n7000-s1-kickstart.4.0.1.binswitch# delete bootflash://sup-standby/n7000-s1-dk9.4.0.1.binStep 10
Copy the Cisco NX-OS kickstart and system images to the active supervisor module using a transfer protocol. You can use ftp:, tftp:, scp:, or sftp:. The examples in this procedure use scp:.
![]()
Note
When you download an image file, change to your FTP environment IP address or DNS name and the path where the files are located.
switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-kickstart.4.0.1a.bin bootflash:n7000-s1-kickstart.4.0.1a.binswitch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-dk9.4.0.1a.bin bootflash:n7000-s1-dk9.4.0.1a.binStep 11
Read the release notes for the related image file. See the Cisco NX-OS Software release notes.
Step 12
Save the running configuration to the start configuration.
switch# copy running-config startup-config vdc-allStep 13
Perform the upgrade using the install all command at the command prompt on the active supervisor module.
switch# install all kickstart bootflash:n7000-s1-kickstart.4.0.1a.bin system bootflash:n7000-s1-dk9.4.0.1a.binFor example output from a nondisruptive upgrade, see the "Example Nondisruptive Upgrade of an Device with Dual Supervisors" section.
For example output from a disruptive upgrade, see the "Example Disruptive Upgrade of an Device with Dual Supervisors" section.
![]()
Note
If the upgrade is disruptive, you can either resolve the issues that cause the disruption and repeat this step, or you can continue with the disruptive upgrade.
![]()
Note
The install all command does not install the EPLD images.
Step 14
After the installation operation completes, log in and verify that the device is running the required software version using the show version command.
switch# show versionCisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpSoftwareBIOS: version 3.15.0loader: version N/Akickstart: version 4.0(1a) [gdb]system: version 4.0(1a) [gdb]BIOS compile time: 03/04/08kickstart image file is: bootflash:/n7000-s1-kickstart.4.0.1a.binkickstart compile time: 3/6/2008 2:00:00 [04/02/2008 09:49:07]system image file is: bootflash:/n7000-s1-dk9.4.0.1a.binsystem compile time: 3/6/2008 2:00:00 [04/02/2008 10:28:32]Hardwarecisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X")Intel(R) Xeon(R) CPU with 2063436 kB of memory.Processor Board ID JAB10380101Device name: switchbootflash: 1023120 kBslot0: 0 kB (expansion flash)Kernel uptime is 2 day(s), 17 hour(s), 26 minute(s), 1 second(s)Last reset at 121426 usecs after Sun Apr 13 20:38:08 2008Reason: Reset Requested by CLI command reloadSystem version: 4.0(1a)Service:...Step 15
Reload both CMPs. For information about configuring and upgrading the CMP, see the Cisco Nexus 7000 Series Connectivity Management Processor Configuration Guide.
switch# reload cmp module 5switch# reload cmp module 6Step 16
(Optional) Install licenses (if necessary) to ensure that the required features are available on the device. See the Cisco Nexus 7000 Series NX-OS Licensing Guide, Release 4.0.
Upgrading a Device with a Single Supervisor
This section includes the following topics:
Upgrade Procedure Summary
The following summary procedure describes how to upgrade a device that has a single supervisor module to the latest Cisco NX-OS software:
Step 1
Log in to the console port on the supervisor modules.
Step 2
Log in to Cisco.com and download the latest Cisco NX-OS kickstart and system images.
Step 3
Download the Cisco NX-OS kickstart and system images to your device using the copy command.
Step 4
Update the KICKSTART and SYSTEM boot variables and module images using the install all command.
![]()
Note
The install all command does not install the EPLD images.
Step 5
Save the device configuration using the copy running-config startup-config vdc-all command.
Step 6
Enter the reload command at the active supervisor command prompt to upgrade the Cisco NX-OS software on your device.
![]()
CautionReloading the device disrupts traffic on the device.
Detailed Upgrade Procedure
![]()
CautionUpgrading a device with a single supervisor module disrupts traffic flow through the device.
To upgrade to the latest Cisco NX-OS software on a device with a single supervisor, follow these steps:
Step 1
Log in to the device on the console port connection.
Step 2
Log in to Cisco.com to access the links provided in this document. To log in to Cisco.com, go to the URL http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.
![]()
Note
Unregistered Cisco.com users cannot access the links provided in this document.
Step 3
Access the Software Download Center using this URL:
http://www.cisco.com/public/sw-center/index.shtml
Step 4
Navigate to the download site for your device.
You see links to the download images for your device.
Step 5
Select and download the kickstart and system software files to a server.
Step 6
Ensure that the required space is available in the bootflash: directory for the image file(s) to be copied.
switch# dir bootflash:49152 Apr 16 14:43:39 2008 lost+found/80850712 Apr 04 15:57:44 2008 n7000-s1-dk9.4.0.1.bin22593024 Apr 04 15:52:56 2008 n7000-s1-kickstart.4.0.1.binUsage for bootflash://sup-local103492888 bytes used800604904 bytes free904097792 bytes total![]()
Tip
We recommend that you have the kickstart and system image files for at least one previous release of the Cisco NX-OS software on the device to use if the new image files do not load successfully.
Step 7
If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.
switch# delete bootflash:n7000-s1-kickstart.4.0.1a.binswitch# delete bootflash:n7000-s1-dk9.4.0.1a.binStep 8
Copy the Cisco NX-OS kickstart and system images to the active supervisor module bootflash using a transfer protocol. You can use ftp:, tftp:, scp:, or sftp:. The examples in this procedure use scp:.
![]()
Note
When you download an image file, change to your FTP environment IP address or DNS name and the path where the files are located.
switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-kickstart.4.0.1a.bin bootflash:n7000-s1-kickstart.4.0.1a.binswitch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-dk9.4.0.1a.bin bootflash:n7000-s1-dk9.4.0.1a.binStep 9
Read the release notes for the related image file. See the Cisco NX-OS Software release notes.
Step 10
Update the boot variables and module images on your device.
switch# install all kickstart bootflash:n7000-s1-kickstart.4.0.1a.binsystem bootflash:n7000-s1-dk9.4.0.1a.bin![]()
Note
The install all command does not install the EPLD images.
Step 11
Save the running configuration to the start configuration.
switch(config)# copy running-config startup-config vdc-allStep 12
Perform the upgrade using the reload command.
switch(config)# reloadFor example output from the reload command, see the "Example Upgrade of a Device with a Single Supervisor" section.
Step 13
After the device completes the reload operation, log in and verify that the device is running the required software version.
switch# show versionCisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpSoftwareBIOS: version 3.15.0loader: version N/Akickstart: version 4.0(1a) [gdb]system: version 4.0(1a) [gdb]BIOS compile time: 03/04/08kickstart image file is: bootflash:/n7000-s1-kickstart.4.0.1a.binkickstart compile time: 3/6/2008 2:00:00 [04/02/2008 09:49:07]system image file is: bootflash:/n7000-s1-dk9.4.0.1a.binsystem compile time: 3/6/2008 2:00:00 [04/02/2008 10:28:32]Hardwarecisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X")Intel(R) Xeon(R) CPU with 2063436 kB of memory.Processor Board ID JAB10380101Device name: switchbootflash: 1023120 kBslot0: 0 kB (expansion flash)Kernel uptime is 2 day(s), 17 hour(s), 26 minute(s), 1 second(s)Last reset at 121426 usecs after Sun Apr 13 20:38:08 2008Reason: Reset Requested by CLI command reloadSystem version: 4.0(1a)Service:...Step 14
Reload the CMP. For information about configuring and upgrading the CMP, see the Cisco Nexus 7000 Series Connectivity Management Processor Configuration Guide.
switch# reload cmp module 6Step 15
(Optional) Install licenses to ensure that the required features are available on the device. See the Cisco Nexus 7000 Series NX-OS Licensing Guide, Release 4.0.
Downgrading from a Higher Release
Only users with the network-admin role can downgrade the Cisco NX-OS software image and only from the default virtual device context (VDC).
To downgrade your device to an earlier release of the Cisco NX-OS software, follow these steps:
Step 1
Log in to the device on the console port connection.
Step 2
Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.
switch# dir bootflash:49152 Apr 16 14:43:39 2008 lost+found/80850712 Apr 04 15:57:44 2008 n7000-s1-dk9.4.0.1.bin22593024 Apr 04 15:52:56 2008 n7000-s1-kickstart.4.0.1.binUsage for bootflash://sup-local103492888 bytes used800604904 bytes free904097792 bytes totalStep 3
If the software image file is not present, log in to Cisco.com to access the links provided in this document. To log in to Cisco.com, go to the URL http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password. You can obtain the software image file from the Cisco.com software download center at the following URL:
http://www.cisco.com/public/sw-center/index.shtml
![]()
Note
If you need more space on the active or standby supervisor module bootflash:, use the delete command to remove unnecessary files.
switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-kickstart.4.0.1.bin bootflash:n7000-s1-kickstart.4.0.1.binswitch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-dk9.4.0.1.bin bootflash:n7000-s1-dk9.4.0.1.binStep 4
Determine if you need to disable any features not supported by the older release using the show incompatibility system image-filename command.
switch# show incompatibility system bootflash:n7000-s1-dk9.4.0.1.binThe following configurations on active are incompatible with the system image1) Service : eth_port_channel , Capability : CAP_FEATURE_AUTO_CREATED_PORT_CHANNELDescription : active mode port channels, auto create enabled ports or auto created port-channels are presentCapability requirement : STRICTDisable command : 1.Convert Active mode port channels to On mode port channels (no channel mode active).2.Disable autocreate on interfaces (no channel-group auto).3.Convert autocreated port channels to be persistent (port-channel 1 persistent).Step 5
Disable any features that are incompatible with the downgrade system image.
Step 6
Save the running configuration to the start configuration
switch# copy running-config startup-config vdc-allStep 7
Upgrade the Cisco NX-OS software as described in the "Upgrading a Device with Dual Supervisors" section or the "Upgrading a Device with a Single Supervisor" section.
Example Outputs from Cisco NX-OS Software Upgrades
This section includes the following topics:
•
Example Nondisruptive Upgrade of an Device with Dual Supervisors
•
Example Disruptive Upgrade of an Device with Dual Supervisors
•
Example Upgrade of a Device with a Single Supervisor
![]()
Note
The output of the install all command depends on the software image, especially the upgrade required (Upg-Required) field information in the upgrade table.
Example Nondisruptive Upgrade of an Device with Dual Supervisors
The following console session output shows a nondisruptive execution of the install all command on a device with dual supervisor modules:
switch# install all kickstart bootflash:n7000-s1-kickstart.4.0.1a.bin system bootflash:n7000-s1-dk9.4.0.1a.binVerifying image bootflash:/n7000-s1-kickstart.4.0.1a.bin for boot variable "kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/n7000-s1-dk9.4.0.1a.bin for boot variable "system".[####################] 100% -- SUCCESSVerifying image type.[####################] 100% -- SUCCESSExtracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "bios" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/n7000-s1-kickstart.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "cmp" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "cmp-bios" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes non-disruptive rolling2 yes non-disruptive rolling3 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset7 yes non-disruptive rolling10 yes non-disruptive rollingImages will be upgraded according to following table:Module Image Running-Version(pri:alt) New-Version Upg-Required------ ---------- ---------------------------------------- -------------------- ------------1 lc1n7k 4.0(1au) 4.0(1a) yes1 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) no2 lc1n7k 4.0(1au) 4.0(1a) yes2 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) no3 lc1n7k 4.0(1au) 4.0(1a) yes3 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) no5 system 4.0(1au) 4.0(1a) yes5 kickstart 4.0(1au) 4.0(1a) yes5 bios v3.16.0(03/17/08): v3.16.0(03/17/08) v3.15.0(03/04/08) no5 cmp 4.0(1a) 4.0(1a) no5 cmp-bios 02.01.01 02.01.01 no6 system 4.0(1au) 4.0(1a) yes6 kickstart 4.0(1au) 4.0(1a) yes6 bios v3.16.0(03/17/08): v3.16.0(03/17/08) v3.15.0(03/04/08) no6 cmp 4.0(1a) 4.0(1a) no6 cmp-bios 02.01.01 02.01.01 no7 lc1n7k 4.0(1au) 4.0(1a) yes7 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) no10 lc1n7k 4.0(1au) 4.0(1a) yes10 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) noDo you want to continue with the installation (y/n)? [n] yInstall is in progress, please wait.Syncing image bootflash:/n7000-s1-kickstart.4.0.1a.bin to standby.[####################] 100% -- SUCCESSSyncing image bootflash:/n7000-s1-dk9.4.0.1a.bin to standby.[####################] 100% -- SUCCESSSetting boot variables.[####################] 100% -- SUCCESSPerforming configuration copy.[####################] 100% -- SUCCESS2008 Apr 17 08:04:57.822 switch %$ VDC-1 %$ %PLATFORM-2-MOD_REMOVE: Module 6 removed (Serial numberJAB114902HH)Module 6: Waiting for module online.-- SUCCESS2008 Apr 17 08:09:26.811 switch %$ VDC-1 %$ %CARDCLIENT-2-SSE: MOD:6 SUP ONLINENotifying services about the switchover.[####################] 100% -- SUCCESS"Switching over onto standby".Raw time read from Hardware Clock: Y=2008 M=4 D=17 08:11:23writing reset reason 7, SAP(93): Swover due to installNX7 SUP Ver 3.16.0Serial Port Parameters from CMOSPMCON_1: 0x200PMCON_2: 0x0PMCON_3: 0x3aPM1_STS: 0x101Performing Memory Detection and TestingTesting 1 DRAM PatternsTotal mem found : 4096 MBMemory test complete.NumCpus = 2.Status 61: PCI DEVICES Enumeration StartedStatus 62: PCI DEVICES Enumeration EndedStatus 9F: Dispatching DriversStatus 9E: IOFPGA FoundStatus 9A: Booting From Primary ROMStatus 98: Found Cisco IDEStatus 98: Found Cisco IDEStatus 98: Found Cisco IDEStatus 90: Loading Boot LoaderReset Reason Registers: 0x1 0x0Filesystem type is ext2fs, partition type 0x83GNU GRUB version 0.97Autobooting bootflash:/n7000-s1-kickstart.4.0.1a.bin bootflash:/n7000-s1-dk9.4.0.1a.bin...Filesystem type is ext2fs, partition type 0x83Booting kickstart image: bootflash:/n7000-s1-kickstart.4.0.1a.bin............................................................................Image verification OKStarting kernel...INIT: version 2.85 bootingChecking all filesystems..r.r.r.. done./bootflash//n7000-s1-dk9.4.0.1a.bin read doneSetting kernel variables: sysctlnet.ipv4.ip_forward = 0net.ipv4.ip_default_ttl = 64net.ipv4.ip_no_pmtu_disc = 1.Setting the System Clock using the Hardware Clock as reference...System Clock set. Local time: Thu Apr 17 08:13:43 UTC 2008Loading system softwareUncompressing system image: bootflash:/n7000-s1-dk9.4.0.1a.binLoading plugin 0: core_plugin...INIT: Entering runlevel: 3Exporting directories for NFS kernel daemon...done.Starting NFS kernel daemon:rpc.nfsd.rpc.mountddone.User Access Verificationswitch login: 2008 Apr 17 08:15:19.818 switch %$ VDC-1 %$ %IDEHSD-2-UMOUNT: slot0 offline2008 Apr 17 08:15:20.004 switch %$ VDC-1 %$ %IDEHSD-2-MOUNT: slot0 online2008 Apr 17 08:15:30.976 switch %$ VDC-1 %$ %IDEHSD-2-MOUNT: logflash onlineUser Access Verificationswitch login: adminPassword: <password>Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpswitch(standby)#![]()
Note
A supervisor module switchover has occurred and the active supervisor module is now the standby supervisor module.
The following example console session output from the standby supervisor module shows that the standby supervisor module switches over to become the active supervisor module.
switch(standby)#NX7 SUP Ver 3.16.0Serial Port Parameters from CMOSPMCON_1: 0x200PMCON_2: 0x0PMCON_3: 0x3aPM1_STS: 0x101Performing Memory Detection and TestingTesting 1 DRAM PatternsTotal mem found : 4096 MBMemory test complete.NumCpus = 2.Status 61: PCI DEVICES Enumeration StartedStatus 62: PCI DEVICES Enumeration EndedStatus 9F: Dispatching DriversStatus 9E: IOFPGA FoundStatus 9A: Booting From Primary ROMStatus 98: Found Cisco IDEStatus 98: Found Cisco IDEStatus 98: Found Cisco IDEStatus 90: Loading Boot LoaderReset Reason Registers: 0x0 0x8Filesystem type is ext2fs, partition type 0x83GNU GRUB version 0.97Autobooting bootflash:/n7000-s1-kickstart.4.0.1a.bin bootflash:/n7000-s1-dk9.4.0.1a.bin...Filesystem type is ext2fs, partition type 0x83Booting kickstart image: bootflash:/n7000-s1-kickstart.4.0.1a.bin............................................................................Image verification OKStarting kernel...INIT: version 2.85 bootingChecking all filesystems..r.r.r.. done./bootflash//n7000-s1-dk9.4.0.1a.bin read doneSetting kernel variables: sysctlnet.ipv4.ip_forward = 0net.ipv4.ip_default_ttl = 64net.ipv4.ip_no_pmtu_disc = 1.Setting the System Clock using the Hardware Clock as reference...System Clock set. Local time: Thu Apr 1708:07:14 UTC 2008Loading system softwareUncompressing system image: bootflash:/n7000-s1-dk9.4.0.1a.binLoading plugin 0: core_plugin...INIT: Entering runlevel: 3Exporting directories for NFS kernel daemon...done.Starting NFS kernel daemon:rpc.nfsd.rpc.mountddone.System is coming up ... Please wContinuing with installation, please wait2008 Apr 17 08:08:51.904 switch %$ VDC-1 %$ %IDEHSD-2-UMOUNT: slot0 offline2008 Apr 17 08:08:51.941 switch %$ VDC-1 %$ %IDEHSD-2-MOUNT: slot0 online2008 Apr 17 08:08:52.970 switch %$ VDC-1 %$ %IDEHSD-2-MOUNT: logflash onlineModule 6: Waiting for module online.-- SUCCESS2008 Apr 17 08:11:21.710 switch %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active (pre-start phase).2008 Apr 17 08:11:21.711 switch %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_START: This supervisor is becoming active.2008 Apr 17 08:11:27.202 switch %$ VDC-1 %$ %SYSMGR-2-SWITCHOVER_OVER: Switchover completed.Module 1: Non-disruptive upgrading.[####################] 100% -- SUCCESSModule 2: Non-disruptive upgrading.[####################] 100% -- SUCCESSModule 3: Non-disruptive upgrading.[####################] 100% -- SUCCESSModule 7: Non-disruptive upgrading.[####################] 100% -- SUCCESSModule 10: Non-disruptive upgrading.[####################] 100% -- SUCCESSRecommended action::"Please reload CMP(s) manually to have it run in the newer version.".Install has been successful.User Access Verificationswitch login: adminPassword: <password>Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpswitch#Example Disruptive Upgrade of an Device with Dual Supervisors
The following console session output shows a disruptive execution of the install all command on a device with dual supervisor modules:
switch# install all kickstart bootflash:n7000-s1-kickstart.4.0.1a.bin system bootflash:n7000-s1-dk9.4.0.1a.binVerifying image bootflash:/n7000-s1-kickstart.4.0.1a.bin for boot variable "kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/n7000-s1-dk9.4.0.1a.bin for boot variable "system".[####################] 100% -- SUCCESSVerifying image type.[####################] 100% -- SUCCESSExtracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "bios" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/n7000-s1-kickstart.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "cmp" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSExtracting "cmp-bios" version from image bootflash:/n7000-s1-dk9.4.0.1a.bin.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes disruptive reset Incompatible image3 yes disruptive reset Incompatible image5 yes disruptive reset Incompatible image6 yes disruptive reset Incompatible image10 yes disruptive reset Incompatible imageImages will be upgraded according to following table:Module Image Running-Version(pri:alt) New-Version Upg-Required------ ---------- ---------------------------------------- -------------------- ------------1 lc1n7k 4.0(1a) 4.0(2u) yes1 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) no3 lc1n7k 4.0(1a) 4.0(2u) yes3 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) no5 system 4.0(1a) 4.0(2u) yes5 kickstart 4.0(1a) 4.0(2u) yes5 bios v3.17.0(03/23/08): v3.17.0(03/23/08) v3.17.0(03/23/08) no5 cmp 4.0(1au) 4.0(2u) yes5 cmp-bios 02.01.01 02.01.03 yes6 system 4.0(1a) 4.0(2u) yes6 kickstart 4.0(1a) 4.0(2u) yes6 bios v3.17.0(03/23/08): v3.17.0(03/23/08) v3.17.0(03/23/08) no6 cmp 4.0(1au) 4.0(2u) yes6 cmp-bios 02.01.01 02.01.03 yes10 lc1n7k 4.0(1a) 4.0(2u) yes10 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) noSwitch will be reloaded for disruptive upgrade.Do you want to continue with the installation (y/n)? [n] yInstall is in progress, please wait.Syncing image bootflash:/n7000-s1-kickstart.4.0.1a.bin to standby.[####################] 100% -- SUCCESSSyncing image bootflash:/n7000-s1-dk9.4.0.1a.bin to standby.[####################] 100% -- SUCCESSSetting boot variables.[####################] 100% -- SUCCESSPerforming configuration copy.[####################] 100% -- SUCCESSRebooting the switch to finish the upgrade.Raw time read from Hardware Clock: Y=2008 M=4 D=18 02:31:29writing reset reason 31,NX7 SUP Ver 3.17.0Serial Port Parameters from CMOSPMCON_1: 0x200PMCON_2: 0x0PMCON_3: 0x3aPM1_STS: 0x101Performing Memory Detection and TestingTesting 1 DRAM PatternsTotal mem found : 4096 MBMemory test complete.NumCpus = 2.Status 61: PCI DEVICES Enumeration StartedStatus 62: PCI DEVICES Enumeration EndedStatus 9F: Dispatching DriversStatus 9E: IOFPGA FoundStatus 9A: Booting From Primary ROMStatus 98: Found Cisco IDEStatus 98: Found Cisco IDEStatus 90: Loading Boot LoaderReset Reason Registers: 0x10 0x0Filesystem type is ext2fs, partition type 0x83GNU GRUB version 0.97Autobooting bootflash:/n7000-s1-kickstart.4.0.1a.bin bootflash:/n7000-s1-dk9.4.0.1a.bin...Filesystem type is ext2fs, partition type 0x83Booting kickstart image: bootflash:/n7000-s1-kickstart.4.0.1a.bin............................................................................Image verification OKStarting kernel...INIT: version 2.85 bootingChecking all filesystems..r.r.r.. done./bootflash//n7000-s1-dk9.4.0.1a.bin read doneduplicate password entrydelete line `adminbackup:x:0:0::/var/home/adminbackup:/bin/bash'? Noduplicate password entrydelete line `adminbackup:x:2003:504::/var/home/adminbackup:/isan/bin/vsh_perm'? Nopwck: no changesSetting kernel variables: sysctlnet.ipv4.ip_forward = 0net.ipv4.ip_default_ttl = 64net.ipv4.ip_no_pmtu_disc = 1.Setting the System Clock using the Hardware Clock as reference...System Clock set. Local time: Fri Apr 18 02:33:51 UTC 2008Loading system softwareUncompressing system image: bootflash:/n7000-s1-dk9.4.0.1a.binLoad plugins that defined in image conf: /isan/plugin_img/img.confLoading plugin 0: core_plugin...INIT: Entering runlevel: 3Exporting directories for NFS kernel daemon...done.Starting NFS kernel daemon:rpc.nfsd.rpc.mountddone.System is coming up ... Please wait ...System is coming up ... Please wait ...System is coming up ... Please wait ...User Access Verificationswitch login: adminPassword: <password>![]()
Note
A supervisor module switchover has occurred and the active supervisor module is now the standby supervisor module.
The following example console session output from the standby supervisor module shows that the standby supervisor module switches over to become the active supervisor module.
switch(standby)#NX7 SUP Ver 3.17.0Serial Port Parameters from CMOSPMCON_1: 0x200PMCON_2: 0x0PMCON_3: 0x3aPM1_STS: 0x101Performing Memory Detection and TestingTesting 1 DRAM PatternsTotal mem found : 4096 MBMemory test complete.NumCpus = 2.Status 61: PCI DEVICES Enumeration StartedStatus 62: PCI DEVICES Enumeration EndedStatus 9F: Dispatching DriversStatus 9E: IOFPGA FoundStatus 9A: Booting From Primary ROMStatus 98: Found Cisco IDEStatus 98: Found Cisco IDEStatus 90: Loading Boot LoaderReset Reason Registers: 0x10 0x0Filesystem type is ext2fs, partition type 0x83GNU GRUB version 0.97Autobooting bootflash:/n7000-s1-kickstart.4.0.1a.bin bootflash:/n7000-s1-dk9.4.0.1a.bin...Filesystem type is ext2fs, partition type 0x83Booting kickstart image: bootflash:/n7000-s1-kickstart.4.0.1a.bin............................................................................Image verification OKStarting kernel...INIT: version 2.85 bootingChecking all filesystems..r.r.r.. done./bootflash//n7000-s1-dk9.4.0.1a.bin read doneduplicate password entrydelete line `adminbackup:x:0:0::/var/home/adminbackup:/bin/bash'? Noduplicate password entrydelete line `adminbackup:x:2003:504::/var/home/adminbackup:/isan/bin/vsh_perm'? Nopwck: no changesSetting kernel variables: sysctlnet.ipv4.ip_forward = 0net.ipv4.ip_default_ttl = 64net.ipv4.ip_no_pmtu_disc = 1.Setting the System Clock using the Hardware Clock as reference...System Clock set. Local time: Fri Apr 18 02:33:42 UTC 2008Loading system softwareUncompressing system image: bootflash:/n7000-s1-dk9.4.0.1a.binLoad plugins that defined in image conf: /isan/plugin_img/img.confLoading plugin 0: core_plugin...INIT: Entering runlevel: 3Exporting directories for NFS kernel daemon...done.Starting NFS kernel daemon:rpc.nfsd.rpc.mountddone.User Access Verificationswitch login: adminPassword: <password>Example Upgrade of a Device with a Single Supervisor
The following console session output shows the execution of the reload command on a device with a single supervisor module:
switch(config)# reloadThis command will reboot the system. (y/n)? [n] y
2008 Apr 13 20:16:52 switch %$ VDC-1 %$ %PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart from Command Line InterfaceRaw time read from Hardware Clock: Y=2008 M=4 D=13 20:17:01writing reset reason 9,NX7 SUP Ver 3.15.0Serial Port Parameters from CMOSPMCON_1: 0x200PMCON_2: 0x0PMCON_3: 0x3aPM1_STS: 0x1Performing Memory Detection and TestingTesting 1 DRAM PatternsNX7 SUP Ver 3.15.0Serial Port Parameters from CMOSPMCON_1: 0x200PMCON_2: 0x0PMCON_3: 0x3aPM1_STS: 0x1Performing Memory Detection and TestingTesting 1 DRAM PatternsTotal mem found : 2048 MBMemory test complete.NumCpus = 2.Status 61: PCI DEVICES Enumeration StartedStatus 62: PCI DEVICES Enumeration EndedStatus 9F: Dispatching DriversStatus 9E: IOFPGA FoundStatus 9A: Booting From Primary ROMStatus 98: Found Cisco IDEStatus 90: Loading Boot LoaderReset Reason Registers: 0x10 0x10Filesystem type is ext2fs, partition type 0x83GNU GRUB version 0.97Autobooting bootflash:/n7000-s1-kickstart.4.0.1a.bin bootflash:/old_images/n7000-s1-dk9.4.0.1a.bin...Filesystem type is ext2fs, partition type 0x83Booting kickstart image: bootflash:/n7000-s1-kickstart.4.0.1a.bin..............................................................................Imageverification OKStarting kernel...INIT: version 2.85 bootingChecking all filesystems..r.r.r.. done.no matching password file entrydelete line `adminbackup:$1$Oip/C5Ci$oOdx7oJSlBCFpNRmQK4na.:13419:0:99999:7:::'?Nopwck: no changesSetting kernel variables: sysctlnet.ipv4.ip_forward = 0net.ipv4.ip_default_ttl = 64net.ipv4.ip_no_pmtu_disc = 1.Setting the System Clock using the Hardware Clock as reference...System Clock set. Local time: Sun Apr 13 20:19:38 UTC 2008Loading system software/bootflash//n7000-s1-dk9.4.0.1a.bin read doneUncompressing system image: bootflash:/n7000-s1-dk9.4.0.1a.binLoading plugin 0: core_plugin...INIT: Entering runlevel: 3Exporting directories for NFS kernel daemon...done.Starting NFS kernel daemon:rpc.nfsd.rpc.mountddone.2008 Apr 13 20:21:45 switch %$ VDC-1 %$ %KERN-2-SYSTEM_MSG: Starting kernel... - kernel2008 Apr 13 20:22:09 switch %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come onlineUser Access Verificationswitch login: adminpassword: <password>Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
![]()
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0908R)
Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide
Copyright © 2008-2009 Cisco Systems, Inc. All rights reserved.