Cisco Nexus 3500 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x)
First Published: 2018-07-16
Last Modified: 2021-02-02
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000 800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOT WITH STANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned 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. (1721R)
© 2018–2021 Cisco Systems, Inc. All rights reserved.
Preface
This preface includes the following sections:
- Audience
- Document Conventions
- Related Documentation for Cisco Nexus 3500 Series Switches
- Documentation Feedback
- Communications, Services, and Additional Information
Audience
This publication is for network administrators who install, configure, and maintain Cisco Nexus switches.
Document Conventions
Command descriptions use the following conventions:
| Convention | Description |
| bold | Bold text indicates the commands and keywords that you enter literally as shown. |
| Italic | Italic text indicates arguments for which the user supplies the values. |
| [x] | Square brackets enclose an optional element (keyword or argument). |
| [x | y] | Square brackets enclosing keywords or arguments separated by a vertical bar indicate an optional choice. |
| {x | y} | Braces enclosing keywords or arguments separated by a vertical bar indicate a required choice. |
| [x {y | z}] | Nested set of square brackets or braces indicate optional or required choices within optional or required elements. Braces and a vertical bar within square brackets indicate a required choice within an optional element. |
| variable | Indicates a variable for which you supply values, in context where italics cannot be used. |
| string | A non quoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks. |
| Examples use the following conventions: | |
| screen font | Terminal sessions and information the switch displays are in screen font. |
| boldface screen font | Information you must enter is in boldface screen font. |
| italic screen font | Arguments for which you supply values are in italic screen font. |
| < > | Nonprinting characters, such as passwords, are in angle brackets. |
| [ ] | Default responses to system prompts are in square brackets. |
| !, # | An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line. |
The entire Cisco Nexus 3500 Series switch documentation set is available at the following URL:
https://www.cisco.com/c/en/us/support/switches/nexus-3000-series-switches/tsd-products-support-series-home.html
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus3k-docfeedback@cisco.com. We appreciate your feedback.
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.
New and Changed Information
This chapter provides release-specific information for each new and changed feature in the Cisco Nexus 3500 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.x.
- New and Changed Information
New and Changed Information
This table summarizes the new and changed features for the Cisco Nexus 3500 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.x and tells you where they are documented.
Table 1: New and Changed Features for Cisco NX-OS Release 9.x
| Feature | Description | Changed in Release | Where Documented |
| Upgrade Process | Updated the section for upgrading to the new release. | 9.2(1) | Upgrading the Cisco NX-OS Software |
Upgrading or Downgrading the CiscoNexus 3500 Series NX-OS Software
This chapter describes how to upgrade or downgrade the Cisco NX-OS software. It contains the following sections:
- About the Software Image
- Recommendations for Upgrading the Cisco NX-OS Software
- Prerequisites for Upgrading the Cisco NX-OS Software
- Prerequisites for Downgrading the Cisco NX-OS Software
- Cisco NX-OS Software Upgrade Guidelines
- Cisco NX-OS Software Downgrade Guidelines
- Compact Image for Cisco Nexus 3000, 3100, and 3500
- Booting the Switch from the USB
- Upgrading the Cisco NX-OS Software
- Downgrading to an Earlier Software Release
About the Software Image
Each device is shipped with the Cisco NX-OS software. The Cisco NX-OS software consists a single NXOS software image. Only this image is required to load the Cisco NX-OS operating system. This image runs on all Cisco Nexus 3500 Series switches.
Note Another type of binary file is the software maintenance upgrade (SMU) package file. SMUs contain fixes for specific defects. They are created to respond to immediate issues and do not include new features. SMU package files are available for download from Cisco.com and generally include the ID number of the resolved defect in the filename. For more information on SMUs, see the Cisco Nexus 3500 Series NX-OS System Management Configuration Guide.
Recommendations for Upgrading the Cisco NX-OS Software
Cisco recommends performing a Nexus Health and Configuration Check before performing an upgrade. The benefits include identification of potential issues, susceptible Field Notices and Security Vulnerabilities, missing recommended configurations and so on. For more information about the procedure, see Perform Nexus Health and Configuration Check.
Prerequisites for Upgrading the Cisco NX-OS Software
Upgrading the Cisco NX-OS software has the following prerequisites:
- 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. Use the show configuration session summary command to verify that you have no active configuration sessions.
- 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.
- 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. To verify connectivity to the remote server, use the ping command.
switch# ping 172.18.217.1 vrf management
PING 172.18.217.1 (172.18.217.1): 56 data bytes
64 bytes from 172.18.217.1: icmp_seq=0 ttl=239 time=106.647 ms
64 bytes from 172.18.217.1: icmp_seq=1 ttl=239 time=76.807 ms
64 bytes from 172.18.217.1: icmp_seq=2 ttl=239 time=76.593 ms
64 bytes from 172.18.217.1: icmp_seq=3 ttl=239 time=81.679 ms
64 bytes from 172.18.217.1: icmp_seq=4 ttl=239 time=76.5 ms
— 172.18.217.1 ping statistics —
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 76.5/83.645/106.647 ms
For more information on configuration sessions, see the Cisco Nexus 3500 Series NX-OS System Management Configuration Guide.
Prerequisites for Downgrading the Cisco NX-OS Software
Downgrading the Cisco NX-OS software has the following prerequisites:
- Verify the compatibility of the software using the show incompatibility system bootflash:filename command. If an incompatibility exists, disable any features that are incompatible with the downgrade image before downgrading the software.
Cisco NX-OS Software Upgrade Guidelines
Note The Cisco Nexus 3500Series NX-OS Release Notes contain specific upgrade guidelines for each release. See the Release Notes for the target upgrade release before starting the upgrade.
Before attempting to upgrade to any software image, follow these guidelines:
- Schedule the upgrade when your network is stable and steady.
- Avoid any power interruption, which could corrupt the software image, during the installation procedure.
- The supervisor module must have connection on the console ports to maintain connectivity when switchovers occur during a software upgrade. See the Hardware Installation Guide for your specific chassis.
- An upgrade to Cisco NX-OS Release 9.2(x) is supported only from Cisco NX-OS Release 6.0(2)A8(9) or higher releases.
Note You must compact the Cisco NX-OS Release image before you upgrade from Cisco NX-OS Release 6.0(2)A8(7b) to Cisco NX-OS Release 9.2(1). The image can be compacted only during the scp file copy process.
- Beginning with Cisco NX-OS Release 9.2(1), a simplified NX-OS numbering format is used for the platforms that are supported in the release. In order to support a software upgrade from releases prior to Release 7.0(3)I7(4) that have the old release format, an installer feature supplies an I9(1) label as a suffix to the actual release during the install all operation. This label is printed as part of the image during the install operation from any release prior to 7.0(3)I7(4) to Release 9.2(1), and it can be ignored. See the following example.
switch# install all nxos bootflash:nxos.9.2.1.bin
Installer will perform compatibility check first. Please wait.
Installer is forced disruptive
Verifying image bootflash:/nxos.9.2.1.bin for boot variable “nxos”.
[####################] 100% — SUCCESS
Verifying image type.
[####################] 100% — SUCCESS
Preparing “nxos” version info using image bootflash:/nxos.9.2.1.bin.
[####################] 100% — SUCCESS
Preparing “bios” version info using image bootflash:/nxos.9.2.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 for ISSU |
Images will be upgraded according to following table:
| Module | Image | Running-Version(pri:alt) | New-Version | Upg-Required |
| 1 yes | nxos | 7.0(3)I7(3) | 9.2(1)I9(1) | |
| 1 no | bios | v05.31(05/17/2018):v05.26(11/06/2017) | v05.31(05/17/2018) |
Switch will be reloaded for disruptive upgrade.
Do you want to continue with the installation (y/n)? [n] y
- Cisco Nexus 3548 and 3548-X switches must run a compact NX-OS software image due to limited bootflash space. This compact image can be created using the NX-OS Compact Image procedure; alternatively, a compact NX-OS software image can be downloaded directly from Cisco’s Software Download website. This requirement does not apply to the Cisco Nexus 3548-XL switch.
• The MD5/SHA512 checksum published on Cisco’s Software Download website for a compact NX-OS software image may not match the MD5/SHA512 checksum of a compact image created through the NX-OS Compact Image procedure. - In Cisco NX-OS Release 9.2(2) Flexlink is supported on Cisco N3K-C3548P-XL (MTC/MTC-CR/MTC-XL) Platform switches.
- In Cisco NX-OS Release 9.2(3) and 9.2(4), Flexlink is not supported on Cisco N3K-C3548P-XL (MTC/MTC-CR/MTC-XL) Platform switches.
The following limitations are applicable when you upgrade from Cisco NX-OS Releases 6.0(2)A8(7b), 6.0(2)A8(8), or 6.0(2)A8(9):
- If Cisco Catalyst devices are connected via a vPC to a pair of Nexus 3500 switches with the vPC peer switch feature enabled, a partial or complete network outage may be caused as a result of the Cisco Catalyst devices error-disabling their port-channel interfaces due to EtherChannel Guard. To prevent thisfrom happening, it isrecommended that you must temporarily disable the EtherChannel Guard feature on vPC-connected Cisco Catalyst devices while the Nexus 3500 devices are being upgraded. For more information, see CSCvt02249.
Cisco NX-OS Software Downgrade Guidelines
Before attempting to downgrade to an earlier software release, follow these guidelines:
- The supervisor module must have connection on the console ports to maintain connectivity when switchovers occur during a software downgrade. See the Hardware Installation Guide for your specific chassis.
- Cisco NX-OS automatically installs and enables the guest shell by default. However, if the device is reloaded with a Cisco NX-OS image that does not provide guest shell support, the existing guest shell is automatically removed and a %VMAN-2-INVALID_PACKAGE message is issued. As a best practice, remove the guest shell with the guestshell destroy command before downgrading to an earlier Cisco NX-OS image.
Compact Image for Cisco Nexus 3000, 3100, and 3500
Early models of Cisco Nexus 3000, 3100, and 3500 Series switches with a model number that does not end in –XL have 1.4 to 1.6 gigabytes of storage space allocated to the bootflash. Over time, the file size of NX-OS software images has steadily increased to be over 1 gigabyte. As a result, it is difficult for Nexus 3000, 3100, and 3500 Series switches with a model number that does not end in –XL to simultaneously store more than one full NX-OSbinary image at a time. Therefore, administrators cannot follow the standard NX-OSsoftware upgrade procedure on Nexus 3000, 3100, and 3500 Series switches with a model number that does not end in –XL that is used for other Nexus platforms, such as Nexus 5000, 6000, 7000, and 9000 Series switches.
Starting with NX-OS software release 7.0(3)I3(1), the file size of NX-OS software images can be reduced through the NX-OS Compact Image procedure. This is a non-disruptive procedure that does not affect the switch’s control plane or ability to forward data plane traffic.
Compact NX-OS Software Images on Cisco’s Software Download Website
Compact NX-OS software images are available for download on Cisco’s Software Download website for a few NX-OS software releases. These compact images have a published MD5/SHA512 checksum that can be used to verify the integrity of the NX-OS binary image file. The compact NX-OS software images can be downloaded from Cisco’s Software Download website for the following NX-OS software releases:
- 9.3(4) and later
- 9.2(4)
- 7.0(3)I7(8) and later
Note The MD5/SHA512 checksum published on Cisco’sSoftware Download website for a compact NX-OSsoftware image may not match the MD5/SHA512 checksum of a compact image created through the NX-OS Compact Image procedure.
Compact Image to be Run for Different Switch Models
The following table describes the appropriate compact image to be run for each applicable model of switch, using NX-OS software release 9.2(4) as an example.
Table 2: Compact Image Table for Each Cisco Nexus 3000, 3100, and 3500 Series Platform
| Switch Model Number | Compact NX-OS Software Image Filename |
| N3K-C3016Q-40GE | n3000-compact.9.2.4.bin |
| N3K-C3048TP-1GE | n3000-compact.9.2.4.bin |
| N3K-C3064PQ-10GX | n3000-compact.9.2.4.bin |
| N3K-C3064TQ-10GT | n3000-compact.9.2.4.bin |
| N3K-C3064TQ-32T | n3000-compact.9.2.4.bin |
| N3K-C3132Q-40GE | n3100-compact.9.2.4.bin |
| N3K-C3132Q-40GX | n3100-compact.9.2.4.bin |
| N3K-C3172PQ-10GE | n3100-compact.9.2.4.bin |
| N3K-C3172TQ-10GT | n3100-compact.9.2.4.bin |
| N3K-C3172TQ-32T | n3100-compact.9.2.4.bin |
| N3K-C3524P-10G | n3500-compact.9.2.4.bin |
| N3K-C3524P-10GX | n3500-compact.9.2.4.bin |
| N3K-C3548P-10G | n3500-compact.9.2.4.bin |
| N3K-C3548P-10GX | n3500-compact.9.2.4.bin |
NX-OS Compact Image Procedure
There are two ways to initiate the NX-OS Compact Image procedure. The following subsections describe each option in further detail.
NX-OS Compact Image Procedure on Bootflash/USB
Starting with NX-OS software release 7.0(3)I3(1), you can use the install all command with the compact option to initiate the NX-OS Compact Image procedure on an image stored in the switch’s bootflash or an attached USB drive. This can also be performed on an NX-OS software image that the switch is currently booted from – however, a minimum of 750MB of free space on the switch’s bootflash is required to compact the currently booted image.
An example of how to initiate the NX-OS Compact Image procedure on an NX-OS software image stored on the switch’s bootflash is as follows:
switch# install all nxos booftflash:nxos.7.0.3.I7.8.bin compact
NX-OS Compact Image Procedure Through SCP
Starting with NX-OS software release 7.0(3)I5(2), the NX-OS Compact Image procedure can be initiated while copying the image to the switch’s bootflash or an attached USB drive with SCP (Secure Copy Protocol) using an additional option in the copy command. The compact option in the copy command overrides the bootflash space limitation as the image is compacted at the time of transferring the image to the switch’s bootflash or an attached USB drive. This option is only supported with SCP – other protocols (such as SFTP [Secure File Transfer Protocol] and FTP [File Transfer Protocol]) are not supported.
An example of how to initiate the NX-OS Compact Image procedure while copying an NX-OSsoftware image to the switch’s bootflash through SCP is as follows:
switch# copy scp://username@192.0.2.100/nxos.7.0.3.I7.8.bin bootflash:nxos.7.0.3.I7.8.bin compact vrf management
NX-OS Compact Image Procedure Sequence
The sequence of compacting NX-OS software images is important. You cannot compact the currently loaded NX-OSsoftware image if you have another NX-OSsoftware image present on the bootflash due to the limited bootflash size of the switch.
First, you should compact the currently booted image on the bootflash using the NX-OS Compact Image Procedure on Bootflash/USB method previously described. Next, you should copy the desired NX-OSsoftware image to the switch’s bootflash using the NX-OS Compact Image Procedure through SCP method previously described, if possible. If this option is not possible, because you are upgrading to an NX-OS software release prior to 7.0(3)I5(2), you should copy the desired NX-OS software image to the switch’s bootflash normally, then use the NX-OS Compact Image Procedure on Bootflash/USB method previously described to compact the image.
The minimum required free space to compact a non-booted image is 450MB of free space on the switch’s bootflash. If the free space available on the switch’s bootflash is less than 450MB after copying the target image, then the target image needs to be compacted using an attached USB drive or through the NX-OS Compact Image Procedure through SCP method previously described.
NX-OS Compact Image Platform Groups
The NX-OS Compact Image procedure described in this document is applicable to three separate platform groups:
- Nexus 3000 devices (N3K-C3048, N3K-C3064, and so on)
- Nexus 3100 devices (N3K-C3132, N3K-C3172, and so on)
- Nexus 3500 devices (N3K-C3524, N3K-C3548, and so on)
A compacted NX-OS binary image file can be re-used among other devices within the same platform group. However, a compact NX-OS binary image file cannot be used on devices that belong to a different platform group.
For example, consider a scenario where you have four Nexus 3000 devices of the following models:
- N3K-C3048TP-1GE
- N3K-C3064PQ-10GE
- N3K-C3172PQ-40GX
- N3K-C3548P-10G
An NX-OSbinary image file compacted on the N3K-C3048TP-1GE can be transferred directly to the bootflash of the N3K-C3064PQ-10GE through a file transfer protocol of your choice (provided there is enough room on the N3K-C3064PQ-10GE). Furthermore, the N3K-C3064PQ-10GE can be upgraded with the use of this compact NX-OS binary image file through a supported method. However, the same compact NX-OS binary image file cannot be used to upgrade the N3K-C3172PQ-40GX and N3K-C3548P-10G devices. The NX-OS Compact Image procedure must be executed on both N3K-C3172PQ-40GX and N3K-C3548P-10G devices separately.
This compatibility between Nexus devices within the same platform group can be used to optimize the NX-OS software upgrade of a large number of devices. For example, if you have 100 N3K-C3048TP-1GE devices, you can use the NX-OS Compact Image procedure on a single device, then transfer the compact NX-OS binary image file to the resulting 99 devices. There is no need to perform the NX-OS Compact Image procedure on all 100 devices.
Booting the Switch from the USB
You can optionally choose to boot the switch from an external flash memory drive at the loader prompt. The supported BIOSversion for the Cisco Nexus 3548P-10GX switch is 2.0.8 and for the Cisco Nexus 3548P-10G switch, it is 1.0.11. Following are the various options for loading the image from an external flash memory drive:
- You can load the image from USB1 when either the USB1 slot is occupied or when both the USB slots are occupied.
Loader> boot usb1: <image> - You can load the image from USB2 only when the USB2 slot is occupied.
Loader> boot usb2: <image> - You can load the image from USB2 when both the USB slots are occupied.
Loader> boot usb2: <image> - You can load the image from USB1 when only the USB1 slot is occupied or when both the USB slots are occupied.
- You can load the image from USB2 when only the USB2 slot is occupied.
- You can load the image from USB2 when both the USB slots are occupied.
Upgrading the Cisco NX-OS Software
Note If an error message appears during the upgrade, the upgrade will fail because of the reason indicated.
SUMMARY STEPS
- Read the release notes for the software image file for any exceptions to this upgrade procedure. See the Cisco Nexus 3500 Series NX-OS Release Notes.
- Log in to the device on the console port connection.
- Ensure that the required space is available for the image files to be copied.
- If you need more space on the device, delete unnecessary files to make space available.
- Upgrade the Cisco NX-OS software to new Cisco NX-OS Release.
- Copy the software images to the device using a transfer protocol. You can use FTP, TFTP, SCP, or SFTP.
- Check the impact of upgrading the software before actually performing the upgrade.
- Save the running configuration to the startup configuration.
- Upgrade the Cisco NX-OS software using the install all nxos bootflash:filename [no-reload | non-disruptive | non-interruptive | serial] command.
- (Optional) Log in and verify that the device is running the required software version.
- (Optional) Verify the entire upgrade process.
- (Optional) If necessary, install any licenses to ensure that the required features are available on the device. See the Cisco NX-OS Licensing Guide.
DETAILED STEPS
Step 1 Read the release notes for the software image file for any exceptions to this upgrade procedure. See the Cisco Nexus 3500 Series NX-OS Release Notes.
Step 2 Log in to the device on the console port connection.
Step 3 Ensure that the required space is available for the image files to be copied.
switch# dir bootflash:
Note We recommend that you have the image filesfor at least one previousrelease of the Cisco NX-OSsoftware on the device to use if the new image files do not load successfully.
Step 4 If you need more space on the device, delete unnecessary files to make space available.
Step 5 Upgrade the Cisco NX-OS software to new Cisco NX-OS Release.
Step 6 Copy the software images to the device using a transfer protocol. You can use FTP, TFTP, SCP, or SFTP.
switch# copy scp://user@server-ip/path/to/image bootflash: compact vrf management
switch# copy scp://user@scpserver.cisco.com//download/nxos.9.2.1.bin bootflash: compact vrf management
The compact option compresses the image while copying it to the switch’s bootflash or USB drive. SCP is the only protocol that supports the compact option.
Note For Cisco Nexus 3548-XL platform switches, the compact option is not supported. Therefore, copy the software image without the compact image.
Step 7 Check the impact of upgrading the software before actually performing the upgrade.
switch# show install all impact kickstart bootflash:nxos.9.2.1.bin
Note In order to accommodate upgrade compatibility from an oldersoftware version that is expecting a platform designator, the version string in the output of this command will appear as “9.2(1)I9(1)”. The “I9(1)” portion of the string can be safely ignored, and it will disappear post upgrade to 9.2(1). In addition, the compatibility check will show “Wrong image.”
Note Do not use the show install all system bootflash:nxos.9.2.1.bin command. It returns the following error: 0% — FAIL. Return code 0x404F0003 (SRG file not present/cannot be opened).
Step 8 Save the running configuration to the startup configuration.
switch# copy running-config startup-config
Step 9 Upgrade the Cisco NX-OS software using the install all nxos bootflash:filename [no-reload | non-disruptive | non-interruptive | serial] command.
switch# install all nxos bootflash:nxos.9.2.1.bin
Note If you enter the install all command without specifying a filename, the command performs a compatibility check, notifies you of the modules that will be upgraded, and confirms that you want to continue with the installation. If you choose to proceed, it installs the NXOS software image that is currently running on the switch and upgrades the BIOS of various modules from the running image if required.
Step 10 (Optional) Log in and verify that the device is running the required software version.
switch# show version
Step 11 (Optional) Verify the entire upgrade process.
switch# show install all status
Step 12 (Optional) If necessary, install any licenses to ensure that the required features are available on the device. See the Cisco NX-OS Licensing Guide.
Downgrading to an Earlier Software Release
Note If an error message appears during the downgrade, the downgrade will fail because of the reason indicated.
SUMMARY STEPS
- Read the release notes for the software image file for any exceptions to this downgrade procedure. See the Cisco Nexus 3500 Series NX-OS Release Notes.
- Log in to the device on the console port connection.
- Verify that the image files for the downgrade are present on the device bootflash:.
- If the software image file is not present, log in to Cisco.com, choose the software image file for your device from the following URL, and download it to a file server: http://software.cisco.com/download/navigator.html.
- Copy the software images to the device using a transfer protocol. You can use FTP, TFTP, SCP, or SFTP.
- Check for any software incompatibilities.
- Disable any features that are incompatible with the downgrade images.
- Save the running configuration to the startup configuration.
- Downgrade the Cisco NX-OS software. See the following examples for downgrading to 6.x and 7.x releases.
- (Optional) Log in and verify that the device is running the required software version.
- (Optional) Display the entire downgrade process.
DETAILED STEPS
Step 1 Read the release notes for the software image file for any exceptions to this downgrade procedure. See the Cisco Nexus 3500 Series NX-OS Release Notes.
Step 2 Log in to the device on the console port connection.
Step 3 Verify that the image files for the downgrade are present on the device bootflash:.
switch# dir bootflash:
…
Step 4 If the software image file is not present, log in to Cisco.com, choose the software image file for your device from the following URL, and download it to a file server: http://software.cisco.com/download/navigator.html.
Note If you need more space on the device bootflash:, use the delete command to remove unnecessary files.
Step 5 Copy the software images to the device using a transfer protocol. You can use FTP, TFTP, SCP, or SFTP.
switch# copy scp://user@scpserver.cisco.com//download/nxos.7.0.3.I7.4.bin
bootflash:nxos.7.0.3.I7.4.bin
switch#copy scp://user@scpserver.cisco.com//download/n3500-uk9-kickstart.6.0.2.A6.7.bin
bootflash:n3500-uk9-kickstart.6.0.2.A6.7.bin
switch#copy scp://user@scpserver.cisco.com//download/n3500-uk9.6.0.2.A6.7.bin bootflash:
Step 6 Check for any software incompatibilities.
switch# show incompatibility nxos bootflash:nxos.7.0.3.I7.4.bin
Checking incompatible configuration(s)
No incompatible configurations
switch#show incompatibility system bootflash:n3500-uk9.6.0.2.A6.7.bin
The resulting output displays any incompatibilities and remedies.
Step 7 Disable any features that are incompatible with the downgrade images.
Step 8 Save the running configuration to the startup configuration.
switch# copy running-config startup-config
Step 9 Downgrade the Cisco NX-OS software. See the following examples for downgrading to 6.x and 7.x releases.
Note Use the no-save and bios-force options when performing the downgrade to 6.x release. The no-save and bios-force options are not required when performing the downgrade to 7.x release.
switch# install all nxos bootflash:nxos.7.0.3.I7.4.bin
switch#install all kickstart bootflash:n3500-uk9-kickstart.6.0.2.A8.9.bin system
n3500-uk9.6.0.2.A8.9.bin no-save bios-force
Note If you enter the install all command without specifying a filename, the command performs a compatibility check, notifies you of the modules that will be upgraded, and confirms that you want to continue with the installation. If you choose to proceed, it installs the NXOS software image that is currently running on the switch and upgrades the BIOS of various modules from the running image if required.
Step 10 (Optional) Log in and verify that the device is running the required software version.
switch# show version
Step 11 (Optional) Display the entire downgrade process.
Example:
switch# show install all status
Documents / Resources
 |
CISCO 3500 Series Wireless LAN Controller [pdf] User Guide 3500, 3500 Series Wireless LAN Controller, 3500 Series, Wireless LAN Controller, LAN Controller, Controller |
