Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 6.x
First Published: 2011-10-14
Last Modified: 2019-02-15
Text Part Number: OL-25758-02
Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide
This document describes how to upgrade or downgrade the Cisco NX-OS software.
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
Note: CMP is a Supervisor 1 only feature.
Figure 1: ISSU Process
This figure shows the ISSU process.
Note: CMP is a Supervisor 1 only feature.
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.
Parallel Upgrade
Parallel Upgrade with I/O Modules
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).
Parallel Upgrade with Fabric Extenders
Beginning with Cisco NX-OS Release 6.1(1), a parallel upgrade on the Fabric Extenders (FEX) is supported if the user types the parallel keyword in the command. You can perform a parallel upgrade of 10 FEXs at a time.
For releases prior to Cisco NX-OS Release 6.1(1), only a serial upgrade of FEXs 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.
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 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.
Cisco NX-OS Software Upgrade Guidelines
Note: Cisco Nexus 7000 Series NX-OS Release Notes contain specific upgrade guidelines for each release. See the Release Notes document for the target upgrade release before starting the upgrade.
Before attempting to use ISSU to upgrade 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). Internal bootflash: has approximately 250 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 that 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.
- Software 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 the 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 filename to be used locally.
- PowerOn Auto Provisioning (POAP):
- To support POAP to be more secure, ensure that DHCP snooping is enabled.
- To support POAP, set the firewall rules to block unintended or malicious DHCP servers.
Table 1: Supported ISSU and ISSD Paths for the Cisco Nexus 7000 Series Platform (Cisco NX-OS Release 6.2(x))
| Current Release | Releases That Support Direct ISSU to the Current Release | ISSD |
|---|---|---|
| NX-OS Release 6.2(22) | 6.2(20a), 6.2(20), 6.2(18), 6.2(16),6.2(14), 6.2(12), 6.2(10), 6.2(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(20a) | 6.2(20), 6.2(18), 6.2(16), 6.2(14), 6.2(12), 6.2(10), 6.2(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(20) | 6.2(18), 6.2(16), 6.2(14), 6.2(12), 6.2(10), 6.2(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(18) | 6.2(8a), 6.2(8b), 6.2(10), 6.2(12), 6.2(14), 6.2(16) | No Support |
| NX-OS Release 6.2(16) | 6.2(8a), 6.2(8b), 6.2(10), 6.2(12), 6.2(14) | No Support |
| NX-OS Release 6.2(14) | 6.2(12),6.2(10),6.2(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(12) | 6.2(10), 6.2.(8a),6.2(8b) | No Support |
| NX-OS Release 6.2(10) | 6.2(8a),6.2(8b),6.2(8) | No Support |
| NX-OS Release 6.2(8b) | 6.2(8a),6.1(5a),5.2(9a) | No Support |
| NX-OS Release 6.2(8a) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a), 6.2(6b), 6.2(8), 6.1(3), 6.1(4), 6.1(4a), 6.1(5), 5.2(7), 5.2(9) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a), 6.2(6b). 6.2(8) |
| NX-OS Release 6.2(8) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a) |
| NX-OS Release 6.2(6b) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a) |
| NX-OS Release 6.2(6a) | 6.2(2), 6.2(2a), 6.2(6), 6.1(3), 6.1(4), 6.1(4a), 6.0(4), 5.2(7), 5.2(9) | 6.2(2), 6.2(2a), 6.2(6) |
| NX-OS Release 6.2(6) | 6.2(2), 6.2(2a), 6.1(3), 6.1(4), 6.1(4a), 6.0(4), 5.2(7), 5.2(9) | 6.2(2), 6.2(2a) |
| NX-OS Release 6.2(2a) | 6.2(2), 6.1(2), 6.1(3), 6.1(4), 6.1(4a), 6.0(4), 5.2(4), 5.2(5), 5.2(7),5.2(9) | 6.2(2) |
Table 2: Supported ISSU and ISSD Paths for the Cisco Nexus 7700 Series Platform (Cisco NX-OS Release 6.2(x))
| Current Release | Releases That Support Direct ISSU to the Current Release | ISSD |
|---|---|---|
| NX-OS Release 6.2(22) | 6.2(20a), 6.2(20), 6.2(18), 6.2(16),6.2(14), 6.2(12), 6.2(10), 6.2(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(20) | 6.2(18), 6.2(16), 6.2(14), 6.2(12), 6.2(10), 6.2(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(20a) | 6.2(20), 6.2(18), 6.2(16), 6.2(14), 6.2(12), 6.2(10), 6.2(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(18) | 6.2(8a), 6.2(8b), 6.2(10), 6.2(12), 6.2(14), 6.2(16) | No Support |
| NX-OS Release 6.2(16) | 6.2(8a), 6.2(8b), 6.2(10), 6.2(12), 6.2(14) | No Support |
| NX-OS Release 6.2(14) | 6.2(12), 6.2(10), 6.2(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(12) | 6.2(10), 6.2.(8a), 6.2(8b) | No Support |
| NX-OS Release 6.2(10) | 6.2(8a), 6.2(8b), 6.2(8) | No Support |
| NX-OS Release 6.2(8b) | 6.2(8a) | No Support |
| NX-OS Release 6.2(8a) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a), 6.2(6b). 6.2(8) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a), 6.2(6b). 6.2(8) |
When you run Cisco NX-OS release earlier than 6.2(8a) you can perform multi-hop ISSU to releases 6.2(12), 6.1(4), 6.2(16), 6.2(20), and 6.2(20a). The following table lists the supported multi-hop ISSU paths.
Table 3: Multi-hop ISSU Paths for the Cisco Nexus 7000 Series Chassis (Cisco NX-OS Release 6.2(x))
| Destination Release | Current Release | Intermediate Release |
|---|---|---|
| Cisco NX-OS Release 6.2(16) | 5.2(7), 5.2(9) | 6.2(8a) |
| Cisco NX-OS Release 6.2(14) | ||
| Cisco NX-OS Release 6.2(12) | ||
| Cisco NX-OS Release 6.2(16) | 6.1(3), 6.1(4), 6.1(4a), 6.1(5) | 6.2(8a) |
| Cisco NX-OS Release 6.2(14) | ||
| Cisco NX-OS Release 6.2(12) | ||
| Cisco NX-OS Release 6.2(16) | 6.2(2), 6.2(2a), 6.2(6), 6.2(6a), 6.2(8a) | 6.2(8) |
| Cisco NX-OS Release 6.2(14) | ||
| Cisco NX-OS Release 6.2(12) | ||
| Cisco NX-OS Release 6.2(16) | 5.2(9a), 6.1(5a) | 6.2(8b) |
| Cisco NX-OS Release 6.2(14) | ||
| Cisco NX-OS Release 6.2(12) |
If the Cisco NX-OS releases that you are running is not listed in "Starting Release" column in the above table, you are recommended to reload the switch to a destination release -6.2(12), 6.2(14), 6.2.(16), 6.2(18), 6.2(20), and 6.2(20a).
Table 4: Multi-hop ISSU Paths for the Cisco Nexus 7700 Series Chassis (Cisco NX-OS Release 6.2(x))
| Destination Release | Current Release | Intermediate Release |
|---|---|---|
| Cisco NX-OS Release 6.2(16) | 6.2(6), 6.2(6a), 6.2(8) | 6.2(8a) |
| Cisco NX-OS Release 6.2(14) | ||
| Cisco NX-OS Release 6.2(12) |
Performing an ISSU to a target release from one of the ISSU supported releases listed in the table above, follow these steps:
- Enter the
show running-config aclmgr inactive-if-configcommand for all VDCs. - Enter the
clear inactive-config aclcommand for all VDCs. - If the configuration has any mac packet-classify configurations on any interfaces, remove all of the configurations by entering the
no mac packet-classifycommand. - Start the ISSU procedure.
Performing a non-ISSU to a target release from any release earlier than Release 6.2(x)/7.2(x), follow these steps:
- Change the boot variable.
- Enter the
copy running-config startup-config vdc-allcommand. - Enter the reload command to reload the switch.
Note: Allow time after the reload for the configuration to be applied.
FCOE over FEX
- Post ISSU user need to change port-channel load-balance for FEX, from default VDC, in order to apply load-balancing for SAN traffic.
Device(config)#port-channel load-balance src-dst mac fex 101- User can revert to default load-balance after changing the load-balance for FEX.
- When you perform an ISSU from any earlier releases to Cisco NX-OS 7.3(2)D1(1) or any later releases, then reload the FEXs after the ISSU to avoid any FCoE traffic loss.
ISSU from 6.2.X to 7.2.x with MPLS L2VPN configuration:
- After upgrading ISSU to 7.2 VPLS AD LDP signaling VC becomes down after the peer reload. To resolve this issue, reload the F3 module and then reload PE1/PE3. The LDP signaling will be up. Reload F3 and flap the L2VPN service even if the VC is down.
No 6.2.x to 7.2.x ISSU support for OTV/GRE/ERSPAN on F3:
- ISSU is blocked and it requires cold boot from 6.2.x to 7.2.x when OTV/GRE/ERSPAN is enabled on F3.
- For multihop ISSU scenario refer to the following: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/release/notes/62_nx-os_release_note.html#pgfld-812362
- The default Control Plane Policing (CoPP) policy does not change when you upgrade the Cisco NX-OS software.
Cisco NX-OS Software Upgrade Guidelines
- COPP MAC policies are supported beginning with Cisco NX-OS Release 5.1, and default policies are installed upon execution of the initial setup script.
- VPC peers can only operate dissimilar versions of the Cisco NX-OS software during the upgrade or downgrade process. Operating VPC peers with dissimilar versions, after the upgrade or downgrade process is complete, is not supported.
Table 5: install all Command Output Terminology
| 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. |
Commands to use
- Verify connectivity to the remote server using the
pingcommand. - Ensure that the required space is available on both the active and standby supervisor modules for the image files to be copied using the
dircommand. - Use the one-step
install allcommand 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.
Note: During vPC setup, the configuration is locked on the peer switch while ISSU is in progress.
• ISSU is not supported when the vPC peers are on a single physical device but are across VDCs.
• Do not enter another command while running the installation.
Cisco NX-OS Software Downgrade Guidelines
- Any features introduced in a release must be disabled before downgrading to a release that does not support those features. See the release notes for information on the new features introduced in each release.
- VPC peers can only operate dissimilar versions of the Cisco NX-OS software during the upgrade or downgrade process. Operating VPC peers with dissimilar versions, after the upgrade or downgrade process is complete, is not supported.
To determine incompatibility before you downgrade your software, use the following commands:
- For hardware incompatibility—
sh install all impact system system_name - For software incompatibility—
show incompatibility-all system image_filename
Upgrading a Device with Dual Supervisor Modules
The install all command supports in-service software upgrades (ISSUs) on devices that have dual supervisor modules and performs the following actions:
- Determines whether the upgrade will be disruptive and asks if you want to continue.
- Ensure that you have enough space in the standby bootflash.
- 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.
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. 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:
- Before a switchover process, you can only see the progress from the active supervisor module.
- After a switchover process, you can see the progress from both the supervisor modules.
- The
install allcommand automatically checks the image integrity, which includes the running kickstart and system images. - The
install allcommand performs a platform validity check to verify that a wrong image is not used—for example, to check if a Nexus 7000 device image is used inadvertently to upgrade a Nexus 5000 device. - The Ctrl-c escape sequence gracefully ends the
install allcommand. You are prompted to confirm your decision to abort the ISSU process. If you proceed, 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 entering the
install allcommand, 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), 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.
• The show install all impact image-name command runs pre-upgrade checks against a given image and informs the user if the images are compatible for an upgrade or a downgrade.
Note: Refer to the "Supported Upgrade and Downgrade Paths" section of the Cisco Nexus 7000 Series NX-OS Release Notes to get details on the supported Cisco NX-OS release versions to which you can upgrade to or for the downgrade details.
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 a Spanning Tree Protocol (STP) topology change occurs while the upgrade is in progress.
- If the
install allcommand is entered on the standby supervisor module. - If the
install allcommand 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 some FEX ports are operating in LACP fast rate mode.
- 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 impactcommand in the compatibility check section of the output (under the Bootable column). - If a linecard is in failure state, the ISSU will abort.
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.
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.
Procedure
- Log in to the console port on both of the active and standby supervisor modules.
- Log in to Cisco.com and download the latest Cisco NX-OS kickstart and system images to a server.
- Download the Cisco NX-OS kickstart and system images from the server to your device using the
copycommand. - Save the device configuration using the
copy running-config startup-config vdc-allcommand. - Enter the
install allcommand 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.
Detailed Upgrade Procedure
This section describes the detailed procedure to upgrade to the latest Cisco NX-OS software on a device with dual supervisor modules.
Procedure
- Log in to the device on the console port connection on both of the active and standby supervisor modules.
- 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.
- Access the Software Download Center using this URL: http://www.cisco.com/public/sw-center/index.shtml
- Navigate to the download site for your device.
- You see links to the download images for your device.
- Select and download the kickstart and system software files to a server.
- Ensure that the required space is available for the image file(s) to be copied.
switch# dir bootflash: 4096 Oct 24 18:06:54 2015 lost+found/ 146701191 Aug 09 15:18:05 2015 n7000-s1-dk9.6.2.12.bin.CCO 30674944 Apr 25 15:51:13 2015 n7000-s1-kickstart.6.2.12.bin.CCO Usage for bootflash://sup-local 1260208128 bytes used 579682304 bytes free 1839890432 bytes total switch#
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.
- If you need more space on the active supervisor module, delete unnecessary files to make space available.
switch# delete bootflash:n7000-s1-kickstart.6.2.12.bin.CCOswitch# delete bootflash:n7000-s1-dk9.6.2.12.bin.CCO- Verify that there is space available on the standby supervisor module.
switch# dir bootflash://sup-standby/ 49152 Oct 16 14:43:39 2015 lost+found 80850712 Oct 04 15:57:44 2015 n7000-s1-dk9.6.2.12.bin.CCO 22593024 Oct 04 15:52:56 2015 n7000-s1-kickstart.6.2.12.bin.CCO
- 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.6.2.12.bin.CCOswitch# delete bootflash://sup-standby/n7000-s1-dk9.6.2.12.bin.CCO- 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:.
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.7.2.0.D1.1.bin n7000-s1-kickstart.7.2.0.D1.1.bin switch# copy scp://user@scpserver.cisco.com/downloads/n7000-s1-dk9.7.2.0.D1.1.bin n7000-s1-dk9.7.2.0.D1.1.bin
- Read the release notes for the related image file. See the Cisco Nexus 7000 Series NX-OS Release Notes.
- Save the running configuration to the startup configuration.
switch# copy running-config startup-config vdc-all
- Perform the upgrade using the
install allcommand at the command prompt on the active supervisor module.
switch# install all kickstart n7000-s1-kickstart.7.2.0.D1.1.bin system n7000-s1-dk9.7.2.0.D1.1.bin
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.
- After the installation operation completes, log in and verify that the device is running the required software version using the
show versioncommand.
switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents:
http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie
s home.html
Copyright (c) 2002-2015, 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/1gpl-2.1.php
Software
BIOS:
version 3.1.0
kickstart: version 7.2(0) D1 (1)
system:
version 7.2(0) D1 (1)
02/27/2013
BIOS compile time:
kickstart image file is: bootflash:///n7000-s2-kickstart.7.2.0.D1.1.bin.S28
kickstart compile time:
system image file is:
system compile time:
5/19/2015 11:00:00 [06/14/2015 21:46:24]
bootflash:///n7000-s2-dk9.7.2.0.D1.1.bin.S28
5/19/2015 11:00:00 [06/14/2015 23:40:21]
Hardware
cisco Nexus7000 C7018 (18 Slot) Chassis ("Supervisor module-1X")
Intel(R) Xeon(R) CPU
with 8245320 kB of memory.
Processor Board ID JAB1152011N
Upgrading a Device with a Single Supervisor Module
This section describes how to upgrade a Cisco NX-OS device with a single supervisor module.
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.
Procedure
- Log in to the console port on the supervisor modules.
- Log in to Cisco.com and download the latest Cisco NX-OS kickstart and system images.
- Download the Cisco NX-OS kickstart and system images to your device using the copy command.
- Update the KICKSTART and SYSTEM boot variables and module images using the
install allcommand.
Detailed Upgrade Procedure
This section describes the detailed procedure to upgrade to the latest Cisco NX-OS software on a device with a single supervisor.
Procedure
- Log in to the device on the console port connection.
- 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.
- Access the Software Download Center using this URL: http://www.cisco.com/public/sw-center/index.shtml
- Navigate to the download site for your device.
- You see links to the download images for your device.
- Select and download the kickstart and system software files to a server.
- Ensure that the required space is available in the bootflash: directory for the image file(s) to be copied.
switch# dir bootflash: 4096 Oct 24 18:06:54 2015 lost+found/ 146701191 Aug 09 15:18:05 2015 n7000-s1-dk9.6.2.12.bin.CCO 30674944 Apr 25 15:51:13 2015 n7000-s1-kickstart.6.2.12.bin.CCO Usage for bootflash://sup-local 1260208128 bytes used 579682304 bytes free 1839890432 bytes total switch#
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.
- If you need more space on the supervisor module bootflash, delete unnecessary files to make space available.
switch# delete bootflash: n7000-s1-kickstart.6.2.12.bin.CCOswitch# delete bootflash: n7000-s1-dk9.6.2.12.bin.CCO- 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:.
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.7.2.0.D1.1.bin n7000-s1-kickstart.7.2.0.D1.1.bin switch# copy scp://user@scpserver.cisco.com/downloads/n7000-s1-dk9.7.2.0.D1.1.bin n7000-s1-dk9.7.2.0.D1.1.bin
- Read the release notes for the related image file. See the Cisco Nexus 7000 Series NX-OS Release Notes.
- Use the
install allcommand to update the boot variables and module images on your device.
switch# install all kickstart n7000-s1-kickstart.7.2.0.D1.1.bin system n7000-s1-dk9.7.2.0.D1.1.bin
Note: Beginning with Cisco NX-OS Release 5.2, you can save time by upgrading up to three line cards concurrently. To do so, add the parallel option at the end of the install all command (for example, install all kickstart bootflash:n7000-s1-kickstart.5.2.1.bin system bootflash:n7000-s1-dk9.5.2.1.bin parallel). The parallel option is available only when you are upgrading from Cisco NX-OS Release 5.2 to a later release.
- 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
Documents:
http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie
s home.html
Copyright (c) 2002-2015, 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/1gpl-2.1.php
Software
BIOS:
version 3.1.0
kickstart: version 7.2(0) D1 (1)
system:
version 7.2(0) D1 (1)
02/27/2013
BIOS compile time:
kickstart image file is: bootflash:///n7000-s2-kickstart.7.2.0.D1.1.bin.S28
kickstart compile time:
system image file is:
system compile time:
5/19/2015 11:00:00 [06/14/2015 21:46:24]
bootflash:///n7000-s2-dk9.7.2.0.D1.1.bin.S28
5/19/2015 11:00:00 [06/14/2015 23:40:21]
Hardware
cisco Nexus7000 C7018 (18 Slot) Chassis ("Supervisor module-1X")
Intel(R) Xeon(R) CPU
with 8245320 kB of memory.
Processor Board ID JAB1152011N
Performing a Traditional Upgrade or Downgrade (Chassis Reload)
This procedure is recommended for these specific scenarios:
- In lab environments where continuous uptime is not a requirement
- In production environments in the unlikely event that an upgrade needs to be downgraded in a timely manner
- In situations where ISSU or ISSD is not supported for the respective images
Before you begin
Save and back up all configurations before reloading the system to load the new software.
Power down unsupported line cards.
Procedure
- Configure the boot variable for the Cisco NX-OS software kickstart image.
switch (config)# boot kickstart bootflash:n7000-s1-kickstart.7.2.0.D1.1.bin
- Configure the boot variable for the Cisco NX-OS software system image.
switch(config)# boot system bootflash:n7000-s1-dk9.7.2.0.D1.1.bin
- Save the running configuration to the startup configuration.
switch# copy running-config startup-config vdc-all
- Verify that the "Current Boot Variables" and the "Boot Variables on the next reload" match the expected image.
Current Boot Variables: sup-1 kickstart variable = bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin system variable = bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin sup-2 kickstart variable = bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin system variable = bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin No module boot variable set Boot Variables on next reload: sup-1 kickstart variable = bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin system variable = bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin sup-2 kickstart variable = bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin system variable = bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin No module boot variable set
- Verify that the image location and the image name match the above boot statements. In redundant supervisor chassis, the images auto-synchronize from to standby once the boot statements are set.
switch# show boot auto-copy list switch# dir bootflash://sup-active/ 161980383 May 15 17:52:03 2015 n7000-s1-dk9.7.2.0.D1.1.bin 29471232 May 15 18:01:38 2015 n7000-s1-kickstart.7.2.0.D1.1.bin switch# dir bootflash://sup-standby/ 161980383 May 15 18:04:55 2015 n7000-s1-dk9.7.2.0.D1.1.bin 29471232 May 15 18:06:18 2015 n7000-s1-kickstart.7.2.0.D1.1.bin
- After you verify the image location and statements, reload the Cisco NX-OS device.
switch# reload
Example Outputs from Cisco NX-OS Software Upgrades
This section includes example outputs from Cisco NX-OS software upgrades.
- The output of the
install allcommand depends on the software image, especially the upgrade required (Upg-Required) field information in the upgrade table. - Any time you perform a disruptive ISSU, the supervisor modules will be reloaded.
Example Nondisruptive Upgrade of a 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 n7000-s1-kickstart.7.2.0.D1.1.bin system n7000-s1-dk9.7.2.0.D1.1.bin Verifying image bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin for boot variable "kickstart". [####################] 100% SUCCESS Verifying image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin for boot variable "system". [####################] 100% SUCCESS Verifying image type. [####################] 100% SUCCESS Extracting "lc-m1-n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "bios" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc-lc-f1-n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc-m1 m1-n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc c-ml-n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "system" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "kickstart" version from image bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc-m 1c-m1-n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc-m 1c-m1-n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc- f1-n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc-m1-n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "fexth" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "fexth" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "fexth" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "cmp" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "cmp-bios" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.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:
yes yes yes yes| Module | Image | Upg-Required | Running-Version(pri:alt) | New-Version |
|---|---|---|---|---|
| 1 | 1c-m1-n7k | 6.2(12) | 7.2(0) D1 (1) | |
| 1 | bios | no | v1.10.17 (04/25/15): v1.10.17 (04/25/15) | |
| 2 | lc-f1-n7k | 6.2(12) | 7.2(0) D1 (1) | |
| 2 | bios | no | v1.10.17(04/25/15): v1.10.17 (04/25/15) | |
| 3 | 1c-m1-n7k | 6.2(12) | 7.2(0) D1 (1) | |
| 3 | bios | no | v1.10.17(04/25/15): v1.10.17 (04/25/15) | |
| 8 | 1c-m1-n7k | 6.2(12) | 7.2(0) D1 (1) | |
| 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.7.2.0.D1.1.bin to standby. | ||||
| [####################] 100% SUCCESS | ||||
| Syncing image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin to standby. | ||||
| [####################] 100% SUCCESS | ||||
| Setting boot variables. | ||||
| [####################] 100% SUCCESS |
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.
Example Disruptive Upgrade of a 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 n7000-s1-kickstart.7.2.0.D1.1.bin system n7000-s1-dk9.7.2.0.D1.1.bin Verifying image bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin for boot variable "kickstart". [####################] 100% SUCCESS Verifying image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin for boot variable "system". [####################] 100% SUCCESS Verifying image type. [####################] 100% SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "bios" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "system" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "kickstart" version from image bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "cmp" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "cmp-bios" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 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 Upg-Required Running-Version(pri:alt) New-Version 1 1c1n7k yes 6.2(12) 7.2(0) D1 (1) 1 bios no v1.10.17(04/25/15): v1.10.17 (04/25/15)
Example Disruptive Upgrade of a Device with a Single Supervisor
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.7.2.0.D1.1.bin system n7000-s1-dk9.7.2.0.D1.1.bin Verifying image bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin for boot variable "kickstart". [####################] 100% SUCCESS Verifying image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin for boot variable "system". [####################] 100% SUCCESS Verifying image type. [####################] 100% SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "bios" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc1m c1n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "ystem" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. Extracting "k 'kickstart" version from image bootflash:/n7000-s1-kickstart.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "cmp" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Extracting "cmp-bios" version from image bootflash:/n7000-s1-dk9.7.2.0.D1.1.bin. [####################] 100% SUCCESS Performing module support checks. [####################] 100% SUCCESS Notifying services about system upgrade. [####################] 100% SUCCESS
Communications, Services, and Additional Information
- To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.
- To get the business impact you're looking for with the technologies that matter, visit Cisco Services.
- To submit a service request, visit Cisco Support.
- To discover and browse secure, validated enterprise-class apps, products, solutions and services, visit Cisco Marketplace.
- To obtain general networking, training, and certification titles, visit Cisco Press.
- To find warranty information for a specific product or product family, access Cisco Warranty Finder.
Cisco Bug Search Tool
Cisco Bug Search Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.
Feature History for Software Upgrade and Downgrade
This table lists the release history for this document.
Table 6: Feature History for Software Upgrade and Downgrade
| Feature Name | Releases | Feature Information |
|---|---|---|
| Software upgrade | 6.2(22) | Added guidelines for upgrading to Release 6.2(22). |
| Software upgrade | 6.2(20) | Added guidelines for upgrading to Release 6.2(20). |
| Software upgrade | 6.2(18) | Added guidelines for upgrading to Release 6.2(18). |
| Software upgrade | 6.2(16) | Added guidelines for upgrading to Release 6.2(16). |
| Software upgrade | 6.2(14) | Added guidelines for upgrading to Release 6.2(14). |
| Software upgrade | 6.2(2) | Added guidelines for upgrading to Release 6.2(2). |
| Software upgrade | 6.1(1) | Added support for parallel upgrade of Fabric Extenders. |
| Software downgrade | 6.0(1) | Added the ability to perform a non-disruptive in-service software downgrade (ISSD) to Release 5.2(1) |
