The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to upgrade or downgrade the Cisco NX-OS software.
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:
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. |
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:
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.
Parallel Upgrade
Starting with Cisco NX-OS Release 5.2(1), multiple linecards can be simultaneously upgraded, and the infrastructure support is available. This decreases the ISSU time when compared with an ISSU upgrade that is done serially (one card at a time).
To start a parallel upgrade, use the following command: install all kickstart image system image parallel
Up to three linecards can be upgraded in parallel with this command. During the upgrade process, the upgrade of the linecards is displayed in the output as follows:
Non-disruptive upgrading. [# ] 0% Module 5 upgrade completed successfully. . Module 3 upgrade completed successfully. . Module 6 upgrade completed successfully. . Non-disruptive upgrading. [####################] 100% -- SUCCESS Non-disruptive upgrading. [# ] 0% Module 9 upgrade completed successfully. . Non-disruptive upgrading. [####################] 100% -- SUCCESS
Note |
This command will be ignored for a downgrade to a release below Cisco NX-OS Release 5.2.(1). |
Beginning with Cisco NX-OS Release 6.1(1), a parallel upgrade on the Fabric Extenders is supported if the user types the parallel keyword in the command.
For releases prior to Cisco NX-OS Release 6.1(1), only a serial upgrade of Fabric Extenders is supported. The upgrade process switches to a serial upgrade even for the I/O modules present. Even if the user types the parallel keyword in the command, the upgrade will be a serial upgrade.
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 switch over 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.
Before attempting to use ISSU to upgrade to any software image version, follow these guidelines:
Term |
Definition |
|
---|---|---|
bootable |
The module's ability to boot or not boot based on image compatibility. |
|
impact |
The type of software upgrade mechanism—disruptive or nondisruptive. |
|
install-type |
reset |
Resets the module. |
sw-reset |
Resets the module immediately after a switchover. |
|
rolling |
Upgrades each module in sequence. |
|
copy-only |
Updates the software for BIOS, loader, or bootrom. |
Note |
During vPC setup, the configuration is locked on the peer switch while ISSU is in progress. |
Note |
If the I/O modules are not compatible with the software image you install on the supervisor module, some traffic disruption might 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. |
Before attempting to use the in-service software downgrade (ISSD) to downgrade to any software image version, follow these guidelines:
5.2 |
5.1 |
5.0 |
4.2 |
4.1 |
4.0 |
|
---|---|---|---|---|---|---|
XL line cards |
X |
X |
X |
-- |
-- |
-- |
32-port, 10-Gigabit Ethernet XL module (N7K-M132XP-12L) |
X |
X |
-- |
-- |
-- |
-- |
Nondisruptive downgrades from Cisco NX-OS Release 5.x |
X |
X |
X |
X |
-- |
-- |
The install all command supports in-service software upgrades (ISSUs) on devices that have dual supervisor modules and performs the following actions:
The install all command provides the following benefits:
Do you want to continue (y/n) [n] : y
The following situations cause the installation to fail to complete:
The Cisco NX-OS software prevents most configuration changes while the install all command is in progress. However, the Cisco NX-OS software allows configuration changes from Cisco Fabric Services (CFS) and those changes may affect the ISSU.
The following summary procedure describes how to upgrade a device that has dual supervisor modules to the latest Cisco NX-OS software.
This section describes the detailed procedure to upgrade to the latest Cisco NX-OS software on a device with dual supervisor modules.
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.
|
||||
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 2009 lost+found/ 80850712 Apr 04 15:57:44 2009 n7000-s1-dk9.4.2.1.bin 22593024 Apr 04 15:52:56 2009 n7000-s1-kickstart.4.2.1.bin Usage for bootflash://sup-local 103492888 bytes used 800604904 bytes free 904097792 bytes total
|
||||
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.2.1.bin switch# delete bootflash:n7000-s1-dk9.4.2.1.bin |
||||
Step 8 |
Verify that there is space available on the standby supervisor module. switch# dir bootflash://sup-standby/ 49152 Apr 16 14:43:39 2009 lost+found 80850712 Apr 04 15:57:44 2009 n7000-s1-dk9.4.2.1.bin 22593024 Apr 04 15:52:56 2009 n7000-s1-kickstart.4.2.1.bin Usage for bootflash://sup-standby 103492888 bytes used 800604904 bytes free 904097792 bytes total |
||||
Step 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.2.1.bin switch# delete bootflash://sup-standby/n7000-s1-dk9.4.2.1.bin |
||||
Step 10 |
Copy the 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:.
switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-kickstart.4.2.1.bin bootflash:n7000-s1-kickstart.4.2.1.bin switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-dk9.4.2.1.bin bootflash:n7000-s1-dk9.4.2.1.bin |
||||
Step 11 | Read the release notes for the related image file. See the Cisco Nexus 7000 Series NX-OS Release Notes, Release 5.x. | ||||
Step 12 |
Save the running configuration to the startup configuration. switch# copy running-config startup-config vdc-all |
||||
Step 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.2.1.bin system bootflash:n7000-s1-dk9.4.2.1.bin
|
||||
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 version Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php Software BIOS: version 3.15.0 loader: version N/A kickstart: version 4.2(1) [gdb] system: version 4.2(1) [gdb] BIOS compile time: 03/04/09 kickstart image file is: bootflash:/n7000-s1-kickstart.4.2.1.bin kickstart compile time: 3/6/2009 2:00:00 [04/02/2009 09:49:07] system image file is: bootflash:/n7000-s1-dk9.4.2.1.bin system compile time: 3/6/2009 2:00:00 [04/02/2009 10:28:32] Hardware cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X") Intel(R) Xeon(R) CPU with 2063436 kB of memory. Processor Board ID JAB10380101 Device name: switch bootflash: 1023120 kB slot0: 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 2009 Reason: Reset Requested by CLI command reload System version: 4.2(1) Service: ... |
||||
Step 15 |
Reload both CMPs. switch# reload cmp module 5 switch# reload cmp module 6 |
||||
Step 16 |
Type the show install all status command. The entire upgrade process is displayed.
|
||||
Step 17 | (Optional) Install licenses (if necessary) to ensure that the required features are available on the device. See the Cisco NX-OS Licensing Guide. |
This section describes how to upgrade a Cisco NX-OS device with a single supervisor module.
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. |
This section describes the detailed procedure to upgrade to the latest Cisco NX-OS software on a device with a single supervisor.
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.
|
||
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 2009 lost+found/ 80850712 Apr 04 15:57:44 2009 n7000-s1-dk9.4.2.1.bin 22593024 Apr 04 15:52:56 2009 n7000-s1-kickstart.4.2.1.bin Usage for bootflash://sup-local 103492888 bytes used 800604904 bytes free 904097792 bytes total
|
||
Step 7 |
If you need more space on the supervisor module bootflash, delete unnecessary files to make space available. switch# delete bootflash:n7000-s1-kickstart.4.2.1.bin switch# delete bootflash:n7000-s1-dk9.4.2.1.bin |
||
Step 8 |
Copy the 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:.
switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-kickstart.4.2.1.bin bootflash:n7000-s1-kickstart.4.2.1.bin switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-dk9.4.2.1.bin bootflash:n7000-s1-dk9.4.2.1.bin |
||
Step 9 | Read the release notes for the related image file. See the Cisco Nexus 7000 Series NX-OS Release Notes, Release 5.x. | ||
Step 10 |
Use the install all command to update the boot variables and module images on your device. switch# install all kickstart bootflash:n7000-s1-kickstart.4.2.1.bin system bootflash:n7000-s1-dk9.4.2.1.bin
|
||
Step 11 |
After the device completes the reload operation, log in and verify that the device is running the required software version. switch# show version Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php Software BIOS: version 3.15.0 loader: version N/A kickstart: version 4.2(1) [gdb] system: version 4.2(1) [gdb] BIOS compile time: 03/04/08 kickstart image file is: bootflash:/n7000-s1-kickstart.4.2.1.bin kickstart compile time: 3/6/2009 2:00:00 [04/02/2009 09:49:07] system image file is: bootflash:/n7000-s1-dk9.4.2.1.bin system compile time: 3/6/2009 2:00:00 [04/02/2009 10:28:32] Hardware cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X") Intel(R) Xeon(R) CPU with 2063436 kB of memory. Processor Board ID JAB10380101 Device name: switch bootflash: 1023120 kB slot0: 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 2009 Reason: Reset Requested by CLI command reload System version: 4.2(1) Service: ... |
||
Step 12 |
Type the show install all status command. The entire upgrade process is displayed.
|
||
Step 13 |
Reload the CMP modules. switch# reload cmp module 5 switch# reload cmp module 6 |
||
Step 14 | (Optional) Install licenses to ensure that the required features are available on the device. See the Cisco NX-OS Licensing Guide. |
Only users with the network-admin role can use ISSD to downgrade the Cisco NX-OS software image and only from the default virtual device context (VDC).
Prior to downgrading your software, use the show incompatibility-all system image-filename command. The resulting output displays incompatibilities and remedies.
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.2.1.bin 22593024 Apr 04 15:52:56 2008 n7000-s1-kickstart.4.2.1.bin Usage for bootflash://sup-local 103492888 bytes used 800604904 bytes free 904097792 bytes total |
||
Step 3 |
If the software image files are 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 files from the Cisco.com software download center at the following URL: http://www.cisco.com/public/sw-center/index.shtml.
switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-kickstart.4.2.1.bin bootflash:n7000-s1-kickstart.4.0.1a.bin switch# copy scp://user@scpserver.cisco.com//downloads/n7000-s1-dk9.4.2.1.bin bootflash:n7000-s1-dk9.4.0.1a.bin |
||
Step 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.2.1.bin The following configurations on active are incompatible with the system image 1) Service : eth_port_channel , Capability : CAP_FEATURE_AUTO_CREATED_PORT_CHANNEL Description : active mode port channels, auto create enabled ports or auto created port-channels are present Capability requirement : STRICT Disable 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 startup configuration. switch# copy running-config startup-config vdc-all |
||
Step 7 |
Downgrade the Cisco NX-OS software. switch# install all kickstart n7000-s1-kickstart.4.2.1.bin system n7000-s1-dk9.4.2.1.bin
|
Save and back up all configurations before reloading the system to load the new software.
Power down unsupported line cards.
Step 1 |
Configure the boot variable for the Cisco NX-OS software kickstart image. switch# boot kickstart bootflash:n7000-s1-kickstart.6.0.1.bin |
Step 2 |
Configure the boot variable for the Cisco NX-OS software system image. switch# boot system bootflash:n7000-s1-dk9.6.0.1.bin |
Step 3 |
Save the running configuration to the startup configuration. switch# copy running-config startup-config vdc-all |
Step 4 |
Verify that the "Current Boot Variables" and the "Boot Variables on next reload" match the expected image. switch# show boot Current Boot Variables: sup-1 kickstart variable = bootflash:/n7000-s1-kickstart.6.0.1.bin system variable = bootflash:/n7000-s1-dk9.6.0.1.bin sup-2 kickstart variable = bootflash:/n7000-s1-kickstart.6.0.1.bin system variable = bootflash:/n7000-s1-dk9.6.0.1.bin No module boot variable set Boot Variables on next reload: sup-1 kickstart variable = bootflash:/n7000-s1-kickstart.6.0.1.bin system variable = bootflash:/n7000-s1-dk9.6.0.1.bin sup-2 kickstart variable = bootflash:/n7000-s1-kickstart.6.0.1.bin system variable = bootflash:/n7000-s1-dk9.6.0.1.bin No module boot variable set |
Step 5 |
Verify that the image location and the image name match the above boot statements. In redundant supervisor chassis, the images auto-synchronize from active to standby once the boot statements are set. switch# show boot auto-copy list switch# dir bootflash://sup-active/ 161980383 Aug 15 17:52:03 2011 n7000-s1-dk9.6.0.1.bin 29471232 Aug 15 18:01:38 2011 n7000-s1-kickstart.6.0.1.bin switch# dir bootflash://sup-standby/ 161980383 Aug 15 18:04:55 2011 n7000-s1-dk9.6.0.1.bin 29471232 Aug 15 18:06:18 2011 n7000-s1-kickstart.6.0.1.bin |
Step 6 |
After you verify the image location and statements, reload the Cisco NX-OS device. switch# reload |
This section includes example outputs from Cisco NX-OS software upgrades.
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 n7000-s1-kickstart.6.0.1.bin system n7000-s1-dk9.6.0.1.bin Verifying image bootflash:/n7000-s1-kickstart.6.0.1.bin for boot variable "kickstart". [####################] 100% -- SUCCESS Verifying image bootflash:/n7000-s1-dk9.6.0.1.bin for boot variable "system". [####################] 100% -- SUCCESS Verifying image type. [####################] 100% -- SUCCESS Extracting "lc-m1-n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "bios" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc-f1-n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc-m1-n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc-m1-n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "system" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "kickstart" version from image bootflash:/n7000-s1-kickstart.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc-m1-n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc-m1-n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc-f1-n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc-m1-n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "fexth" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "fexth" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "fexth" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "cmp" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "cmp-bios" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Performing module support checks. [####################] 100% -- SUCCESS Notifying services about system upgrade. [####################] 100% -- SUCCESS Compatibility check is done: Module bootable Impact Install-type Reason ------ -------- -------------- ------------ ------ 1 yes non-disruptive rolling 2 yes non-disruptive rolling 3 yes non-disruptive rolling 8 yes non-disruptive rolling 9 yes non-disruptive reset 10 yes non-disruptive reset 11 yes non-disruptive rolling 14 yes non-disruptive rolling 16 yes non-disruptive rolling 18 yes non-disruptive rolling 101 yes non-disruptive rolling 102 yes non-disruptive rolling 103 yes non-disruptive rolling Images will be upgraded according to following table: Module Image Running-Version(pri:alt) New-Version Upg-Required ------ ---------- ---------------------------------------- -------------------- ------------ 1 lc-m1-n7k 5.2(1) 6.0(1) yes 1 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 2 lc-f1-n7k 5.2(1) 6.0(1) yes 2 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 3 lc-m1-n7k 5.2(1) 6.0(1) yes 3 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 8 lc-m1-n7k 5.2(1) 6.0(1) yes 8 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 9 system 5.2(1) 6.0(1) yes 9 kickstart 5.2(1) 6.0(1) yes 9 bios v3.22.0(02/20/10): v3.22.0(02/20/10) no 9 cmp 6.0(1u) 6.0(1) yes 9 cmp-bios 02.01.05 02.01.05 no 10 system 5.2(1) 6.0(1) yes 10 kickstart 5.2(1) 6.0(1) yes 10 bios v3.22.0(02/20/10): v3.22.0(02/20/10) no 10 cmp 6.0(1u) 6.0(1) yes 10 cmp-bios 02.01.05 02.01.05 no 11 lc-m1-n7k 5.2(1) 6.0(1) yes 11 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 14 lc-m1-n7k 5.2(1) 6.0(1) yes 14 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 16 lc-f1-n7k 5.2(1) 6.0(1) yes 16 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 18 lc-m1-n7k 5.2(1) 6.0(1) yes 18 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no Do you want to continue with the installation (y/n)? [n] y Install is in progress, please wait. Performing runtime checks. [####################] 100% -- SUCCESS Syncing image bootflash:/n7000-s1-kickstart.6.0.1.bin to standby. [####################] 100% -- SUCCESS Syncing image bootflash:/n7000-s1-dk9.6.0.1.bin to standby. [####################] 100% -- SUCCESS Setting boot variables. [####################] 100% -- SUCCESS Performing configuration copy. [####################] 100% -- SUCCESS Module 1: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 2: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 3: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 8: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 9: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 10: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 11: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 14: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 16: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS Module 18: Refreshing compact flash and upgrading bios/loader/bootrom. Warning: please do not remove or power off the module at this time. [####################] 100% -- SUCCESS 2011 Oct 24 09:55:57 switch-B %$ VDC-1 %$ %PLATFORM-2-MOD_REMOVE: Module 10 removed (Serial number JAB1229002Q) 2011 Oct 24 10:01:00 switch-B %$ VDC-1 %$ %IDEHSD-STANDBY-2-MOUNT: slot0: online 2011 Oct 24 10:01:39 switch-B %$ VDC-1 %$ %IDEHSD-STANDBY-2-MOUNT: logflash: online 2011 Oct 24 10:01:41 switch-B %$ VDC-1 %$ %CMPPROXY-STANDBY-2-LOG_CMP_UP: Connectivity Management processor(on module 10) is now UP Module 10: Waiting for module online. -- SUCCESS Notifying services about the switchover. [####################] 100% -- SUCCESS
As displayed, once the active supervisor module reloads, the output for the standby supervisor module is displayed.
writing reset reason 7, SAP(93): Swover due to install 2011 Oct ? NX7 SUP Ver 3.22.0 Serial Port Parameters from CMOS On Standby sup: switch-B(standby)# NX7 SUP Ver 3.22.0 Serial Port Parameters from CMOS PMCON_1: 0x200 PMCON_2: 0x0 PMCON_3: 0x3a PM1_STS: 0x101 Performing Memory Detection and Testing Total mem found : 8192 MB Performing memory test... Passed. NumCpus = 2. Status 61: PCI DEVICES Enumeration Started Status 62: PCI DEVICES Enumeration Ended Status 9F: Dispatching Drivers Status 9E: IOFPGA Found Status 9A: Booting From Primary ROM Status 98: Found Cisco IDE Status 98: Found Cisco IDE Status 98: Found Cisco IDE Y??2??0```````````````?0```````````````? Reset Reason Registers: 0x0 0x8 Filesystem type is ext2fs, partition type 0x83 GNU GRUB version 0.97 Autobooting bootflash:/n7000-s1-kickstart.6.0.1.bin bootflash:/n7000-s1-dk9 .6.0.1.bin... Filesystem type is ext2fs, partition type 0x83 Booting kickstart image: bootflash:/n7000-s1-kickstart.6.0.1.bin.... ............................................................................... .................Image verification OK INIT: Checking all filesystems..r.r.r..r done. Loading system software /bootflash//n7000-s1-dk9.6.0.1.bin read done Uncompressing system image: bootflash:/n7000-s1-dk9.6.0.1.bin Mon Oct 24 10:00:07 PST 2011 blogger: nothing to do. ..done Mon Oct 24 10:00:12 PST 2011 Load plugins that defined in image conf: /isan/plugin_img/img.conf Loading plugin 0: core_plugin... num srgs 1 0: swid-core-supdc3, swid-core-supdc3 num srgs 1 0: swid-supdc3-ks, swid-supdc3-ks INIT: Entering runlevel: 3 Continuing with installation, please wait 2011 Oct 24 10:01:00 switch-B %$ VDC-1 %$ %IDEHSD-2-MOUNT: slot0: online 2011 Oct 24 10:01:39 switch-B %$ VDC-1 %$ %IDEHSD-2-MOUNT: logflash: online 2011 Oct 24 10:01:41 switch-B %$ VDC-1 %$ %CMPPROXY-2-LOG_CMP_UP: Connectivity Management processor(on module 10) is now UP Module 10: Waiting for module online. -- SUCCESS 2011 Oct 24 10:04:53 switch-B %$ VDC-1 %$ Oct 24 10:04:53 %KERN-2-SYSTEM_MSG: [ 480.115904] Switchover started by redundancy driver - kernel 2011 Oct 24 10:04:53 switch-B %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active (pre-start phase). 2011 Oct 24 10:04:53 switch-B %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_START: Supervisor 10 is becoming active. 2011 Oct 24 10:04:55 switch-B %$ VDC-1 %$ %SYSMGR-2-SWITCHOVER_OVER: Switchover completed. 2011 Oct 24 10:05:01 switch-B %$ VDC-1 %$ %CALLHOME-2-EVENT: HARDWARE_REMOVAL 2011 Oct 24 10:05:01 switch-B %$ VDC-1 %$ %PLATFORM-2-MOD_REMOVE: Module 6 removed (Serial number ) 2011 Oct 24 10:11:03 switch-B %$ VDC-1 %$ %IDEHSD-STANDBY-2-MOUNT: slot0: online 2011 Oct 24 10:11:12 switch-B %$ VDC-1 %$ %CMPPROXY-STANDBY-2-LOG_CMP_UP: Connectivity Management processor(on module 9) is now UP 2011 Oct 24 10:11:15 switch-B %$ VDC-1 %$ %CALLHOME-2-EVENT: PERIODIC_CONFIGURATION 2011 Oct 24 10:12:02 switch-B %$ VDC-1 %$ %IDEHSD-STANDBY-2-MOUNT: logflash: online Module 1: Non-disruptive upgrading. [####################] 100% -- SUCCESS Module 2: Non-disruptive upgrading. [####################] 100% -- SUCCESS Module 3: Non-disruptive upgrading. [####################] 100% -- SUCCESS Module 8: Non-disruptive upgrading. [####################] 100% -- SUCCESS Module 11: Non-disruptive upgrading. [####################] 100% -- SUCCESS Module 14: Non-disruptive upgrading. [####################] 100% -- SUCCESS Module 16: Non-disruptive upgrading. [####################] 100% -- SUCCESS Module 18: Non-disruptive upgrading. [####################] 100% -- SUCCESS Module 10: Upgrading CMP image. Warning: please do not reload or power cycle CMP module at this time. [####################] 100% -- SUCCESS Module 9: Upgrading CMP image. Warning: please do not reload or power cycle CMP module at this time. [####################] 100% -- SUCCESS Recommended action:: "Please reload CMP(s) manually to have it run in the newer version.". Install has been successful. User Access Verification switch-B login: 2011 Oct 24 10:54:44 switch-B %$ VDC-1 %$ %COPP-2-COPP_PROFILE_DIFF: CoPP Default Profile may have changed, please check the diffs using show copp diff profile <profile-type> prior-ver profile <profile-type> User Access Verification switch-B login: admin Password:<password> Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2011, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php
Note |
A supervisor module switchover has occurred, and the active supervisor module is now the standby supervisor module. |
The following example console session output shows a disruptive execution of the install all command on a device with dual supervisor modules:
switch# install all kickstart n7000-s1-kickstart.6.0.1.bin system n7000-s1-dk9.6.0.1.bin Verifying image bootflash:/n7000-s1-kickstart.6.0.1.bin for boot variable "kickstart". [####################] 100% -- SUCCESS Verifying image bootflash:/n7000-s1-dk9.6.0.1.bin for boot variable "system". [####################] 100% -- SUCCESS Verifying image type. [####################] 100% -- SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "bios" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "system" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "kickstart" version from image bootflash:/n7000-s1-kickstart.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "cmp" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "cmp-bios" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Performing module support checks. [####################] 100% -- SUCCESS Notifying services about system upgrade. [####################] 100% -- SUCCESS Compatibility check is done: Module bootable Impact Install-type Reason ------ -------- -------------- ------------ ------ 1 yes disruptive reset Incompatible image 3 yes disruptive reset Incompatible image 4 yes disruptive reset Incompatible image 5 yes disruptive reset Incompatible image 6 yes disruptive reset Incompatible image 10 yes disruptive reset Incompatible image Images will be upgraded according to following table: Module Image Running-Version(pri:alt) New-Version Upg-Required ------ ---------- ---------------------------------------- -------------------- ------------ 1 lc1n7k 5.0(5) 6.0(1) yes 1 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 3 lc1n7k 5.0(5) 6.0(1) yes 3 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 4 lc1n7k 5.0(5) 6.0(1) yes 4 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 5 system 5.0(5) 6.0(1) yes 5 kickstart 5.0(5) 6.0(1) yes 5 bios v3.22.0(02/20/10): v3.22.0(02/20/10) no 5 cmp 6.0(1) 6.0(1) no 5 cmp-bios 02.01.05 02.01.05 no 6 system 5.0(5) 6.0(1) yes 6 kickstart 5.0(5) 6.0(1) yes 6 bios v3.22.0(02/20/10): v3.22.0(02/20/10) no 6 cmp 6.0(1) 6.0(1) no 6 cmp-bios 02.01.05 02.01.05 no 10 lc1n7k 5.0(5) 6.0(1) yes 10 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no Switch will be reloaded for disruptive upgrade. Do you want to continue with the installation (y/n)? [n] n
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.0 Serial Port Parameters from CMOS PMCON_1: 0x20 PMCON_2: 0x0 PMCON_3: 0x3a PM1_STS: 0x101 Performing Memory Detection and Testing Testing 1 DRAM Patterns Total mem found : 4096 MB Memory test complete. NumCpus = 2. Status 61: PCI DEVICES Enumeration Started Status 62: PCI DEVICES Enumeration Ended Status 9F: Dispatching Drivers Status 9E: IOFPGA Found Status 9A: Booting From Primary ROM Status 98: Found Cisco IDE Status 98: Found Cisco IDE Status 90: Loading Boot Loader Reset Reason Registers: 0x10 0x0 Filesystem type is ext2fs, partition type 0x83 GNU GRUB version 0.97 Autobooting bootflash:/n7000-s1-kickstart.4.0.1a.bin bootflash:/n7000-s1 -dk9.4.0.1a.bin... Filesystem type is ext2fs, partition type 0x83 Booting kickstart image: bootflash:/n7000-s1-kickstart.4.0.1a.bin.... ........................................................................Image verification OK Starting kernel... INIT: version 2.85 booting Checking all filesystems..r.r.r.. done. /bootflash//n7000-s1-dk9.4.0.1a.bin read done duplicate password entry delete line `adminbackup:x:0:0::/var/home/adminbackup:/bin/bash'? No duplicate password entry delete line `adminbackup:x:2003:504::/var/home/adminbackup:/isan/bin/vsh_perm'? No pwck: no changes Setting kernel variables: sysctlnet.ipv4.ip_forward = 0 net.ipv4.ip_default_ttl = 64 net.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 2008 Loading system software Uncompressing system image: bootflash:/n7000-s1-dk9.4.0.1a.bin Load plugins that defined in image conf: /isan/plugin_img/img.conf Loading plugin 0: core_plugin... INIT: Entering runlevel: 3 Exporting directories for NFS kernel daemon...done. Starting NFS kernel daemon:rpc.nfsd. rpc.mountddone. User Access Verification switch login: admin Password: <password>
The following example console session output shows a disruptive execution of the install all command on a device with a single supervisor module:
switch# install all kickstart n7000-s1-kickstart.6.0.1.bin system n7000-s1-dk9.6.0.1.bin Verifying image bootflash:/n7000-s1-kickstart.6.0.1.bin for boot variable "kickstart". [####################] 100% -- SUCCESS Verifying image bootflash:/n7000-s1-dk9.6.0.1.bin for boot variable "system". [####################] 100% -- SUCCESS Verifying image type. [####################] 100% -- SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "bios" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "system" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "kickstart" version from image bootflash:/n7000-s1-kickstart.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "cmp" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Extracting "cmp-bios" version from image bootflash:/n7000-s1-dk9.6.0.1.bin. [####################] 100% -- SUCCESS Performing module support checks. [####################] 100% -- SUCCESS Notifying services about system upgrade. [####################] 100% -- SUCCESS Compatibility check is done: Module bootable Impact Install-type Reason ------ -------- -------------- ------------ ------ 1 yes disruptive reset Incompatible image 3 yes disruptive reset Incompatible image 4 yes disruptive reset Incompatible image 5 yes disruptive reset Incompatible image 6 yes disruptive reset Incompatible image 10 yes disruptive reset Incompatible image Images will be upgraded according to following table: Module Image Running-Version(pri:alt) New-Version Upg-Required ------ ---------- ---------------------------------------- -------------------- ------------ 1 lc1n7k 5.0(5) 6.0(1) yes 1 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 3 lc1n7k 5.0(5) 6.0(1) yes 3 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 4 lc1n7k 5.0(5) 6.0(1) yes 4 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no 5 system 5.0(5) 6.0(1) yes 5 kickstart 5.0(5) 6.0(1) yes 5 bios v3.22.0(02/20/10): v3.22.0(02/20/10) no 5 cmp 6.0(1) 6.0(1) no 5 cmp-bios 02.01.05 02.01.05 no 6 system 5.0(5) 6.0(1) yes 6 kickstart 5.0(5) 6.0(1) yes 6 bios v3.22.0(02/20/10): v3.22.0(02/20/10) no 6 cmp 6.0(1) 6.0(1) no 6 cmp-bios 02.01.05 02.01.05 no 10 lc1n7k 5.0(5) 6.0(1) yes 10 bios v1.10.17(04/25/11): v1.10.17(04/25/11) no Switch will be reloaded for disruptive upgrade. Do you want to continue with the installation (y/n)? [n] n
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.
Feature Name |
Releases |
Feature Information |
---|---|---|
Software upgrade |
5.2(1) |
Added the ability to upgrade up to three line cards concurrently. |