PDF(1.1 MB) View with Adobe Reader on a variety of devices
ePub(123.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(227.3 KB) View on Kindle device or Kindle app on multiple devices
Bias-Free Language
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.
Cisco MDS 9000 Software Upgrade and Downgrade Guide, Release 8.x
First Published: May 4, 2017
Updated: August 18, 2023
This document describes how to upgrade or downgrade the Cisco MDS NX-OS software for Cisco MDS 9000 Series Multilayer Switches.
Note 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.
Updated the nondisruptive ISSU and ISSD paths for the Cisco MDS NX-OS Release 8.4(2d).
August 26, 2021
Added ISSD guideline for OBFL TxWait.
May 18, 2021
Updated the nondisruptive ISSU and ISSD paths for the Cisco MDS NX-OS Release 8.4(2c) and Cisco MDS NX-OS Release 8.5(1).
March 4, 2021
Updated the nondisruptive ISSU and ISSD paths for the Cisco MDS NX-OS Release 8.5(1).
November 26, 2020
Updated the nondisruptive ISSU and ISSD paths for the Cisco MDS NX-OS Release 8.4(2b).
July 1, 2020
Updated the nondisruptive ISSU and ISSD paths for the Cisco MDS NX-OS Release 8.4(2a).
May 4, 2020
Updated the nondisruptive ISSU and ISSD paths for the Cisco MDS NX-OS Release 8.4(2).
December 12, 2019
Updated the nondisruptive ISSU and ISSD paths for the Cisco MDS NX-OS Release 8.4(1a).
August 29, 2019
Updated the nondisruptive ISSU and ISSD paths for the Cisco MDS NX-OS Releases 8.3(2), 8.3(1), 8.2(2), 8.2(1), and 8.1(1b).
June 22, 2019
Added guidelines for upgrading to Cisco MDS NX-OS Release 8.4(1).
December 17, 2018
Added guidelines for upgrading to Cisco MDS NX-OS Release 8.3(2).
October 22, 2018
Added guidelines for upgrading to Cisco MDS NX-OS Release 8.1(1b).
July 13, 2018
Added guidelines for upgrading to Cisco MDS NX-OS Release 8.3(1).
March 9, 2018
Added guidelines for upgrading to Cisco MDS NX-OS Release 8.2(2).
February 28, 2018
Added guidelines for upgrading to Cisco MDS NX-OS Release 8.1(1a).
September 28, 2017
Added guidelines for upgrading to Cisco MDS NX-OS Release 8.2(1).
May 04, 2017
Added guidelines for upgrading to Cisco MDS NX-OS Release 8.1(1).
Introduction
The Cisco MDS 9000 Series of Multilayer Directors and Fabric Switches provide best-in-class high availability, scalability, security, and management, allowing you to deploy high-performance storage area networks. Layering a rich set of intelligent features onto a high-performance switch fabric, the Cisco MDS 9000 Series addresses the stringent requirements of large data center storage environments: high availability, security, scalability, ease of management, and seamless integration of new technologies.
About Software Images
Cisco MDS switch is shipped with the Cisco MDS NX-OS operating system for the Cisco MDS 9000 Series Multilayer Directors and Fabric Switches. The Cisco MDS NX-OS software consists of two images: the kickstart image and the system image.
To select the kickstart image, use the KICKSTART variable.
To select the system image, use the SYSTEM variable.
The images and variables are important factors in any install procedure. Specify the variable and the respective image to upgrade or downgrade your switch. You do not always need both the kickstart and system images for installing the operating system.
Note Do not rename the standard image filenames.
Note To download a new Cisco MDS 9000 Series software, including Cisco NX-OS and Cisco DCNM management software, go to the Storage Networking Software download website at http://www.cisco.com/cisco/software/navigator.html
Release notes are sometimes updated with the new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Series Release Notes.
Dependent Factors for Software Installation
The software image install procedure depends on the following factors:
Software images — The kickstart and system image files reside in directories or folders that can be accessed from the Cisco MDS 9000 Series Multilayer switch prompt.
Image version — Each image file has a version.
Flash disks on the switch — The bootflash: resides on the supervisor module, and the CompactFlash disk is inserted into the slot0: device.
Supervisor modules — Either single or dual supervisor modules are present.
To determine the version of the Cisco MDS NX-OS software that is currently running on a Cisco MDS 9000 switch using the CLI, log in to the switch and run the show version command in privileged EXEC mode.
To determine the version of the Cisco MDS NX-OS software currently running on a Cisco MDS 9000 switch using Cisco DCNM for SAN, click the Switches tab in the Information pane, locate the relevant switch using the corresponding IP address, logical name, or worldwide name (WWN), and check its version in the Release column.
Downloading Software
The Cisco MDS NX-OS software is designed for mission-critical high-availability environments. To realize the benefits of nondisruptive upgrade on the Cisco MDS 9700 Series Multilayer Directors, we recommend that you install dual supervisor modules.
Note All the CLI session examples that are provided in this document are intended only for reference. The actual switch output differs based on your switch model.
To download the latest Cisco MDS NX-OS software, access the Software Center at:
Use the show incompatibility-all system bootflash : system image filename command to determine which features are incompatible with the destination upgrade release.
switch(config)# show incompatibility-all system bootflash:m9700-sf4ek9-mz.8.4.1.bin
Checking incompatible configuration(s):
No incompatible configurations
Checking dynamic incompatibilities:
No incompatible configurations
To request a copy of the source code under the terms of either GPL (General Public License) or LGPL (Lesser General Public License), email mds-software-disclosure@cisco.com.
Selecting the Software Image for a Cisco MDS Switch
Table 2 lists the system and kickstart image that you can use for a Cisco MDS switch.
Table 2 Software Images for Cisco MDS Switches
Cisco MDS Switch
Naming Convention
Cisco MDS 9396T
Filenames begin with m9300-s2ek9
Cisco MDS 9148T
Filenames begin with m9148-s6ek9
Cisco MDS 9132T
Filenames begin with m9100-s6ek9
Cisco MDS 9148S
Filenames begin with m9100-s5ek9
Cisco MDS 9220i
Filenames begin with m9220-s7ek9
Cisco MDS 9250i
Filenames begin with m9250-s5ek9
Cisco MDS 9396S
Filenames begin with m9300-s1ek9
Cisco MDS 9718, 9710, and 9706
Filenames begin with m9700-sf3ek91 Filenames begin with m9700-sf4ek92
1.The m9700-sf3ek9 filename images are supported only on Cisco MDS 9700 Series Supervisor-1 Module on Cisco MDS 9710 and 9706 Director Switches, and Cisco MDS 9700 Series Supervisor-1E Module on Cisco MDS 9718 Director Switches.
2.The m9700-sf4ek9 filename images are supported only on Cisco MDS 9700 Series Supervisor-4 Module on Cisco MDS 9710 and 9706 Director Switches.
No Payload Encryption Software Images
No payload encryption (NPE) images are available with the Cisco MDS NX-OS Release 8.5(1) software. The NPE images are intended for countries that have import restrictions on products that encrypt payload data.
To differentiate an NPE image from a standard software image, the letters npe are included in the image name as follows:
m9100-s6ek9-kickstart-mz-npe.8.5.1.bin
m9100-s6ek9-mz-npe.8.5.1.bin
m9100-s6ek9-kickstart-mz-npe.8.5.1.bin
m9100-s6ek9-mz-npe.8.5.1.bin
m9100-s5ek9-kickstart-mz-npe.8.5.1.bin
m9100-s5ek9-mz-npe.8.5.1.bin
m9148-s6ek9-kickstart-mz-npe.8.5.1.bin
m9148-s6ek9-mz-npe.8.5.1.bin
m9300-s2ek9-kickstart-mz-npe.8.5.1.bin
m9300-s2ek9-mz-npe.8.5.1.bin
m9220-s7ek9-kickstart-mz-npe.8.5.1.bin
m9220-s7ek9-mz-npe.8.5.1.bin
m9250-s5ek9-kickstart-mz-npe.8.5.1.bin
m9250-s5ek9-mz-npe.8.5.1.bin
m9300-s1ek9-kickstart-mz-npe.8.5.1.bin
m9300-s1ek9-mz-npe.8.5.1.bin
m9700-sf3ek9-kickstart-mz-npe.8.5.1.bin
m9700-sf3ek9-mz-npe.8.5.1.bin
m9700-sf4ek9-kickstart-mz-npe.8.5.1.bin
m9700-sf4ek9-mz-npe.8.5.1.bin
Note When downloading software, ensure that you select the correct software image for your Cisco MDS 9000 Series Multilayer switch. Nondisruptive software upgrades or downgrades between NPE images and non-NPE images are not supported.
Installing Cisco MDS NX-OS Release 8.x Software on a Cisco MDS Switch
To install the latest Cisco MDS NX-OS Release 8.x software images on a new Cisco MDS 9000 Series Multilayer switch, perform the following steps:
Step 1 Log in to Cisco.com and click Log In at the top of the page. Enter your Cisco username and password.
Note Use your registered Cisco username and password to access the links provided in this document.
Step 2 Verify the following physical connections for the new Cisco MDS 9000 Series Multilayer switch:
The console port is physically connected to a computer terminal (or terminal server).
The management 10/100/1000 Ethernet port (mgmt0) is connected to an external hub, switch, or a router.
For more information about physical connections, see the Cisco MDS 9000 Series Hardware Installation guides.
Note On switches with dual supervisor modules, both the supervisor modules must have Ethernet connections on the management interfaces (mgmt 0) to maintain connectivity when switchovers occur during upgrades and downgrades.
Note If the management 10/100/1000 Ethernet port (mgmt0) interface of the Cisco MDS 9700 Series Multilayer Directors has a preconfigured “/0” IPv6 address that cannot be removed, use the write erase boot command to clear the complete configuration of the device and reload the device using the reload command. Perform this process before commissioning the device into production, because this process is disruptive to the user traffic if it is applied to the active supervisor of a system. Ensure that there is an active console connection to the supervisor, because this process removes the IPv4 address of the mgmt0 interface.
Tip Save the host ID information for future use, for example, to enable licensed features. The host ID information is provided in the Proof of Purchase document that accompanies the switch.
Step 3 Verify that the default console port parameters listed below are identical to the parameters of the computer terminal (or terminal server) attached to the switch console port:
Step 4 Power up the Cisco MDS 9000 Series Multilayer switch. The switch boots up automatically after powering on the switch.
Step 5Obtain the IP address, subnet mask, and default gateway information that is required for the Cisco MDS 9000 Series Multilayer switch to communicate over the supervisor module Ethernet interface. This information is required to configure and manage the switch.
Step 6 Complete the System Admin Account Setup process. If you create a short, easy-to-decipher password, your password will be rejected. Configure a strong password, as shown in the sample configuration. Passwords are case-sensitive. Explicitly create a password that meets the requirements that are listed in the “Characteristics of Strong Passwords” section in the “Configuring Users and Common Roles” chapter in the Cisco MDS 9000 Series NX-OS Security Configuration Guide.
Note You can change the default password during the initial setup process. All Cisco MDS 9000 Series Multilayer switches have the network administrator as the default user (admin) with a default password (admin). You cannot change the default user.
---- System Admin Account Setup ----
Do you want to enforce secure password standard (yes/no) [y]: no
Enter the password for "admin":
Confirm the password for "admin":
Step 7 Enter yes to when prompted, to set up a mode and assign the information that is obtained in Step 5.
Note Press Ctrl-C at prompts to skip the remaining configuration options and proceed with what is configured until that point.
Tip If you do not want to answer a previously configured question, or if you want to skip answers to any questions, press Enter. If a default answer is not available (for example, a switch name), the switch uses the previously configured settings and moves to the next question.
The CLI configuration step (using factory defaults) is as follows:
---- Basic System Configuration Dialog ----
This setup utility will guide you through the basic configuration of
the system. Setup configures only enough connectivity for management
of the system.
Press Enter incase you want to skip any dialog. Use ctrl-c at anytime
to skip remaining dialogs.
Would you like to enter the basic configuration dialog (yes/no): yes
By default, two roles exist in all the switches:
Network operator (network-operator) — Has permission to view only the configuration. The operator cannot make any configuration changes.
Network administrator (network-admin) — Has permission to execute all commands and make configuration changes. The administrator can also create and customize up to 64 additional roles. One of these 64 additional roles can be configured during the initial setup process.
Create another login account (yes/no) [n]: yes
Note While configuring your initial setup, you can create an additional user account (if you are in the network-admin role) besides the administrator’s account. The username must contain only non-numeric characters. See the “Configuring User Accounts” section in the “Configuring Users and Common Roles” chapter in the Cisco MDS 9000 Series NX-OS Security Configuration Guide.
IPv4 address of the default gateway : 10.104.122.1
Configure advanced IP options? (yes/no) [n]: yes
Continue with In-band (vsan1) management configuration? (yes/no) [n]: yes
Enable IP routing? (yes/no) [n]: yes
Configure static route? (yes/no) [n]: n
Note Ensure that you have configured the IP route, IP default network address, and IP default gateway address to enable the SNMP access. If IP routing is enabled, the switch uses the IP route and the default network IP address. If IP routing is disabled, the switch uses the default gateway IP address.
Configure the default-network: (yes/no) [y]: yes
Note The default network address is Destination prefix: dest_prefix provided in Mgmt0 IPv4 netmask: subnet_mask.
Default network IPv4 address: dest_prefix
Configure the DNS IPv4 address? (yes/no) [y]: yes
DNS IP address: name_server_ip_address
Configure the default domain name? (yes/no) [n]: yes
Default domain name: domain_name
Enable the ssh service? (yes/no) [y]:
Type of ssh key you would like to generate (dsa/rsa) [rsa]:
Number of rsa key bits <1024-4096> [1024]:
Enable the telnet service? (yes/no) [n]: y
Configure congestion/no_credit drop for fc interfaces? (yes/no) [y]: n
Enable the http-server? (yes/no) [y]:
Configure clock? (yes/no) [n]:
Configure timezone? (yes/no) [n]: yes
Enter timezone config [PST/MST/CST/EST] :PST
Enter Hrs offset from UTC [-23:+23] :
Enter Minutes offset from UTC [0-59] :+23
Configure summertime? (yes/no) [n]: yes
summer-time config :PDT 2 sunday march 02:00 1 sunday november 02:00 59
Configure NTP server? (yes/no) [n]: yes
NTP server IP address: ntp_server_IP_address
Configure default switchport interface state (shut/noshut) [shut]: shut
Note The mgmt0 interface is not shut down at this point. Only the Fibre Channel, iSCSI, FCIP, and Gigabit Ethernet interfaces are shut down.
Configure default switchport trunk mode (on/off/auto) [on]: on
Configure default switchport port mode F (yes/no) [n]: yes
Configure default zone policy (permit/deny) [deny]: deny
Enable full zoneset distribution (yes/no) [n]: yes
Configure default zone mode (basic/enhanced) [basic]: basic
username admin password admin_pass role network-admin
username user_name password user_pass role network-admin
snmp-server community snmp_community role
switchname switch
interface mgmt0
ip address ip_address subnet_mask
no shutdown
ip routing
ip route dest_prefix dest_mask dest_address
ip default-network dest_prefix
ip default-gateway default_gateway
ip name-server name_server
ip domain-name domain_name
telnet server disable
ssh key rsa 2048 force
ssh server enable
ntp server ipaddr ntp_server
system default switchport shutdown
system default switchport trunk mode on
system default switchport mode F
system default port-channel auto-create
zone default-zone permit vsan 1-4093
zoneset distribute full vsan 1-4093
system default zone mode enhanced
Would you like to edit the configuration? (yes/no) [n]: no
Would you like to edit the configuration? (yes/no) [n]: no
Use this configuration and save it? (yes/no) [y]: yes
Caution If you do not save the configuration at this point, your changes will not be updated the next time the switch is rebooted. Type
yes in order to save the new configuration. This process ensures that the kickstart and system boot images are also automatically configured.
Tip Up to this point, you can only configure the switch using the CLI. Post this point, continue to configure the switch using either the CLI or the Cisco DCNM application. For more information on using the Cisco DCNM application to configure a switch, see the Cisco DCNM Fundamentals Configuration Guide.
Would you like to save the running-config to startup-config? (yes/no) [n]: y
[########################################] 100%
Copy complete.
If you continue to use the CLI, the login prompt is automatically displayed on your terminal:
Step 8 Log in to the switch using the new username and password.
Step 9 Verify that the required licenses are installed in the switch using the show license command.
Note The switch is initially shipped with the required licenses installed in the system. However, the initial license file does not cover unlicensed features that may be used during the grace period. For more information on licensing, see the Cisco MDS 9000 Series NX-OS Licensing Guide.
The following example shows the CLI output for a valid license:
Step 10 Verify that the switch is running the latest Cisco MDS NX-OS Release 8.x software, depending on which version you have installed, by using the show version command:
If the latest Cisco MDS NX-OS Release 8.x software is not displayed, continue upgrading or downgrading the switch, as required, to install the correct version.
Step 11 Verify the status of the modules on the switch, using the show module command.
Supported Nondisruptive Upgrade Paths for Cisco MDS NX-OS Releases
This section provides information on nondisruptive upgrade paths that are supported for Cisco MDS NX-OS software Release 8.x. It includes the following topics:
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.5(1)
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.5(1).
1. Downgrade directly to MDS NX-OS Release 8.4(2b)
2. Upgrade to MDS NX-OS Release 8.5(1)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.5(1)
6.2(29) and above releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b), Release 8.4(2), Release 8.4(2a), or Release 8.4(2b)
2. Upgrade to MDS NX-OS Release 8.5(1)
6.2(13a) until 6.2(27)
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.5(1)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.5(1)
3.Upgrading from Cisco MDS NX-OS Release 8.4(2c) directly to Cisco MDS NX-OS Release 8.5(1) is not supported. To perform this upgrade, set the boot variables and reload the switch - this process is disruptive. To upgrade nondisruptively, first downgrade from Cisco MDS NX-OS Release 8.4(2c) to an earlier release and from there upgrade to Cisco MDS NX-OS Release 8.5(1). For more information, see CSCvx99164.
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(2f)
If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(2f).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.4(2f)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2f)
6.2(29) and above releases
Upgrade directly to MDS NX-OS Release 8.4(2f)
6.2(13a) until 6.2(27)
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2f)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.4(2f)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(2e)
If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(2e).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.4(2e)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2e)
6.2(29) and above releases
Upgrade directly to MDS NX-OS Release 8.4(2e)
6.2(13a) until 6.2(27)
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2e)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.4(2e)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(2d)
If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(2d).
4.If the SAN Analytics feature is enabled, then disable the SAN Analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS 8.2(x) or Cisco MDS NX-OS 8.3(x) to Cisco MDS NX-OS Release 8.4(2) or later. However, you can upgrade from Cisco MDS NX-OS Release 8.4(1) and above releases to Cisco MDS NX-OS Release 9.2(1) or later without disabling the feature.
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(2c)
If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(2c).
5.If the SAN Analytics feature is enabled, then disable the SAN Analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS 8.2(x) or Cisco MDS NX-OS 8.3(x) to Cisco MDS NX-OS Release 8.4(2) or later. However, you can upgrade from Cisco MDS NX-OS Release 8.4(1) and above releases to Cisco MDS NX-OS Release 9.2(1) or later without disabling the feature.
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(2b)
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(2b).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.4(2b)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2b)
6.2(29) and above releases
Upgrade directly to MDS NX-OS Release 8.4(2b)
6.2(13a) until 6.2(27)
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2b)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.4(2b)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(2a)
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(2a).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.4(2a)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2a)
6.2(29) and above releases
Upgrade directly to MDS NX-OS Release 8.4(2a)
6.2(13a) until 6.2(27)
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2a)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.4(2a)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(2)
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(2).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.4(2)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2)
6.2(29) and above releases
Upgrade directly to MDS NX-OS Release 8.4(2)
6.2(13a) until 6.2(27)
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(2)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.4(2)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(1a)
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(1a).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.4(1a)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(1a)
All 6.2(13a) and above releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(1a)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.4(1a)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(1)
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS Release 8.2(x) to Cisco MDS NX-OS Release 8.4(1).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.4(1)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(1)
All 6.2(13a) and above releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.4(1)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.4(1)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.3(2)
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS 8.2(x) to Cisco MDS NX-OS Release 8.3(2).
Note When upgrading to Cisco MDS NX-OS Release 8.3(2) from release 8.3(1), any remote logging servers that are configured will be lost after the upgrade. After the upgrade is complete, reconfigure the remote logging server(s) using the logging server {host-name | ipv4-address | ipv6-address} command. For more information, see CSCvn07339.
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.3(2)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.3(2)
All 6.2(13a) and above releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.3(2)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.3(2)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.3(1)
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading from Cisco MDS NX-OS 8.2(x) to Cisco MDS NX-OS Release 8.3(1).
Note Cisco MDS 9718 Multilayer Director Switches are not supported on Cisco MDS NX-OS Release 8.3(1).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.3(1)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.3(1)
All 6.2(13a) and above releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.3(1)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.3(1)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.2(2)
Note Prior to upgrading any Cisco MDS 9706 and Cisco MDS 9710 switches to Cisco MDS NX-OS Release 8.2(2), the switches should be checked if they are affected by CSCvf99665. This defect manifests as a corrupt IPv6 address with a zero length mask (/0) on the mgmt0 interface. The actual IPv6 address itself is not important but if it has a /0 mask then it is invalid. This invalid IPv6 address cannot be removed by normal configuration. Refer to the following example: show interface mgmt0 mgmt0 is up Internet address is 1.2.3.4/24 ... ::148.173.170.255/0 fe80::2e31:24ff:fe51:b834/64 If a switch is found to be affected, there are specific steps that must be taken after upgrading to Cisco MDS NX-OS Release 8.2(2). For information on these specific steps, see the Resolution Summary section in CSCvf99665.
Note If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before upgrading to Cisco MDS NX-OS Release 8.2(2).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.2(2)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.2(2)
All 6.2(13a) and above releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.2(2)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.2(2)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.2(1)
Note Before upgrading any Cisco MDS 9706 and Cisco MDS 9710 switches to Cisco MDS NX-OS Release 8.2(1), the switches should be checked if they are affected by CSCvf99665. This defect manifests as a corrupt IPv6 address with a zero length mask (/0) on the mgmt0 interface. The actual IPv6 address itself is not important but if it has a /0 mask then it is invalid. This invalid IPv6 address cannot be removed by normal configuration. Refer to the following example: show interface mgmt0 mgmt0 is up Internet address is 1.2.3.4/24 ... ::148.173.170.255/0 fe80::2e31:24ff:fe51:b834/64 If a switch is found to be affected, there are specific steps that must be taken after upgrading to Cisco MDS NX-OS Release 8.2(1). For information on these specific steps, see the Resolution Summary section in CSCvf99665.
Note Upgrading to Cisco MDS NX-OS Release 8.2(1) on a device with the esp-aes-xcbc-mac algorithm is not supported. In such a scenario, we recommend that you first change the algorithm, and then upgrade to Cisco MDS NX-OS Release 8.2(1).
Note We recommend that you delete existing IP ACLs on the management interface before upgrading to Cisco MDS NX-OS Release 8.2(1). You can reconfigure the IP ACLs after the upgrade is complete. For more information, see CSCvh30932.
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.2(1)
All 7.3(x) releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.2(1)
All 6.2(13a) and above releases
1. Upgrade directly to MDS NX-OS Release 8.1(1b)
2. Upgrade to MDS NX-OS Release 8.2(1)
All 6.2(x) releases prior to 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
3. Upgrade to MDS NX-OS Release 8.2(1)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.1(1b)
Note Before upgrading any Cisco MDS 9706 and Cisco MDS 9710 switches to Cisco MDS NX-OS Release 8.1(1b), the switches should be checked if they are affected by CSCvf99665. This defect manifests as a corrupt IPv6 address with a zero length mask (/0) on the mgmt0 interface. The actual IPv6 address itself is not important but if it has a /0 mask then it is invalid. This invalid IPv6 address cannot be removed by normal configuration. Refer to the following example: show interface mgmt0 mgmt0 is up Internet address is 1.2.3.4/24 ... ::148.173.170.255/0 fe80::2e31:24ff:fe51:b834/64 If a switch is found to be affected, there are specific steps that must be taken after upgrading to Cisco MDS NX-OS Release 8.1(1b). For information on these specific steps, see the Resolution Summary section in CSCvf99665.
Note The Cisco MDS 9700 HVDC PSU (DS-CHV-3.5KW) is not supported in this release. When upgrading a device equipped with these units from any Cisco MDS NX-OS 6.x release do not use this release.
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.1(1b)
All 7.3(x) releases
Upgrade directly to MDS NX-OS Release 8.1(1b)
6.2(13a) and above releases
Upgrade directly to MDS NX-OS Release 8.1(1b)
All 6.2(x) releases before 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1b)
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.1(1a)
Note Before upgrading any Cisco MDS 9706 and Cisco MDS 9710 switches to Cisco MDS NX-OS Release 8.2(2), the switches should be checked if they are affected by CSCvf99665. This defect manifests as a corrupt IPv6 address with a zero length mask (/0) on the mgmt0 interface. The actual IPv6 address itself is not important but if it has a /0 mask then it is invalid. This invalid IPv6 address cannot be removed by normal configuration. Refer to the following example: show interface mgmt0 mgmt0 is up Internet address is 1.2.3.4/24 ... ::148.173.170.255/0 fe80::2e31:24ff:fe51:b834/64 If a switch is found to be affected, there are specific steps that must be taken after upgrading to Cisco MDS NX-OS Release 8.1(1a). For information on these specific steps, see the Resolution Summary section in CSCvf99665.
Note The Cisco MDS 9700 HVDC PSU (DS-CHV-3.5KW) is not supported in this release. When upgrading a device equipped with these units from any Cisco MDS NX-OS 6.x release do not use this release.
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 8.x releases
Upgrade directly to MDS NX-OS Release 8.1(1a)
All 7.3(x) releases
Upgrade directly to MDS NX-OS Release 8.1(1a)
6.2(21)1
1. Upgrade directly to MDS NX-OS Release 6.2(23)
2. Upgrade to MDS NX-OS Release 8.1(1a) 2
All 6.2(13a) and above releases except 6.2(21)
Upgrade directly to MDS NX-OS Release 8.1(1a) 2
All 6.2(x) releases before 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1a) 2
1. Upgrading specifically from MDS NX-OS Release 6.2(21) to MDS NX-OS Release 8.1(1a) is disruptive. For more information, see CSCvj40760.
2. The Cisco MDS 9700 HVDC PSU (DS-CHV-3.5KW) is not supported in this release. Such devices must be upgraded directly to Cisco MDS NX-OS Release 8.2(x) or later via a disruptive reload.
Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.1(1)
Note Before upgrading the Cisco MDS 9706 and Cisco MDS 9710 switches to Cisco MDS NX-OS Release 8.1(1), ensure that they are not affected by CSCvg05230. This defect manifests as a corrupt IPv6 address and mask on the mgmt0 interface. An affected switch cannot be upgraded or downgraded while running the Cisco MDS NX-OS Release 8.1(1). Because this issue cannot be resolved through normal methods, we recommend that you contact the Cisco TAC for help in purging the IPv6 NVRAM fields nondisruptively. This process is simpler if performed before upgrading to Cisco MDS NX-OS Release 8.1(1). For more information, including how to determine if a switch is affected, see CSCvg05230 and CSCvf99665.
Note We recommend that you delete existing IP ACLs on the management interface before upgrading to Cisco MDS NX-OS Release 8.1(1). You can reconfigure the IP ACLs after the upgrade is complete. For more information, see CSCvh30932.
Note The Cisco MDS 9700 HVDC PSU (DS-CHV-3.5KW) is not supported in this release. When upgrading a device equipped with these units from any Cisco MDS NX-OS 6.x release do not use this release.
Nondisruptive Upgrade Path and Ordered Upgrade Steps
NX-OS:
All 7.3(x) releases
Upgrade directly to MDS NX-OS Release 8.1(1)
6.2(13a) and above releases
Upgrade directly to MDS NX-OS Release 8.1(1)
All 6.2(x) releases before 6.2(13a)
1. Upgrade directly to MDS NX-OS Release 6.2(13a)
2. Upgrade to MDS NX-OS Release 8.1(1)
Supported FICON Upgrade Paths for Cisco MDS NX-OS Releases
This section provides information on FICON upgrade paths that are supported for Cisco MDS NX-OS software Release 8.x. It includes the following topics:
We recommend that you do not perform an In-Service Software Upgrade (ISSU) concurrently on switches that are connected via FCIP ISLs. Rather perform the ISSU on one switch and after the ISSU is complete perform the ISSU on the adjacent switch. However, you can perform ISSUs concurrently on switches that are connected via Fibre Channel ISLs.
Smartoptics is supported from Cisco MDS NX-OS Release 8.2(1) or later releases and are not supported on Cisco MDS NX-OS Release 8.1(1b) or earlier releases. If you insert the smartoptics on a switch running an unsupported release and upgrade to a supported release version, the ports will be error disabled and the ports will only come up after removing and inserting the SFP back to their ports.
To upgrade or downgrade to a Cisco MDS NX-OS release version, the same release version of the kickstart and system images in the install all command must be used.
If you copy firmware using the SFTP or SCP clients after enabling the feature scp-server or feature sftp-server command on your switch, ensure that you close the SFTP or SCP connection using the no feature scp-server or no feature sftp-server command before performing ISSU. Otherwise, ISSU will be disruptive. To avoid this issue, we recommend that you transfer files to the switch using the copy command instead or using the DCNM client.
Upgrade Process for a Cisco MDS 9700 Series Multilayer Director
On a Cisco MDS 9700 Series Multilayer Director, the high-level process to upgrade to Cisco MDS NX-OS Release 8.x is as follows:
Upgrading to Cisco MDS NX-OS Release 8.x on a Cisco MDS 9700 Series Multilayer Director
Note Use the console connection for firmware upgrades. If you are upgrading through the management interface, you must have a working connection to both supervisors because this process causes a switchover and the current standby supervisor will be active after the upgrade.
Note Cisco MDS 9718 Multilayer Director supports only Cisco MDS NX-OS Release 7.3(0)D1(1) and later.
Note When the system auto-collect tech-support command is enabled, there is a delay of 600 seconds for the standby switch to reload and become HA-Standby in Cisco MDS 9700 Series Multilayer Directors.
To upgrade your switch to use the latest Cisco MDS NX-OS software on your Cisco MDS 9700 Series Multilayer Directors, perform the following steps:
Step 1 Go to http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco Systems username and password.
Note Unregistered Cisco.com users cannot access secure links that are provided in this document.
Step 2 Verify the following physical connections for the new Cisco MDS 9700 Series Multilayer switch:
The console port is physically connected to a computer terminal (or terminal server).
The management 10/100/1000 Ethernet port (mgmt0) is connected to an external hub, switch, or router.
Step 4 Run the copy running-config startup-config command to store your current running configuration. You can also create a backup of your existing configuration in a file by running the copy running-config bootflash:backup_config.txt command. See the “Using the Cisco NX-OS Setup Utility” chapter in the Cisco MDS 9000 Series NX-OS Fundamentals Configuration Guide.
Step 7Install licenses, if necessary, to ensure that the required features are available on the switch. Perform the following steps:
a. Use the show license host-id command to obtain the serial number of your switch. The host ID is also referred to as the switch serial number.
switch# show license host-id
License hostid: VDH=JAF1721AEQG
Tip Use the entire ID that appears after the colon (:). In this example, the host ID is VDH=JAF1721AEQG.
b. Obtain your Claim Certificate or Proof of Purchase document. This document accompanies every Cisco MDS switch.
c. Locate the Product Authorization Key (PAK) from the Claim Certificate or Proof of Purchase document.
d. A URL is provided in the Claim Certificate or Proof of Purchase document for your product.
e. Locate and access the specified URL that applies to your switch’s and enter the switch serial number and PAK. The license key file is sent to you by email. The license key file is digitally signed to be used only on the switch for which it was requested. The requested features are also enabled after the Cisco MDS NX-OS software on the specified switch accesses the license key file.
Note Install the license file in the specified Cisco MDS 9000 Series Multilayer switch without modifying the key.
Note If you provide a target name for the license key file, the file is installed with the specified name. Otherwise, the filename specified in the license key file is used to install the license.
Step 9Ensure that the required space is available in the bootflash: directory for the image files to be copied using the dir bootflash: command. Use the delete bootflash: filename command to remove unnecessary files.
switch# dir bootflash:
4096 Nov 23 10:47:46 2018.patch/
68230 Dec 10 11:27:20 2018 backup_10_12_2018
4096 Dec 12 10:23:54 2018 bootflash/
52692992 Aug 24 06:18:35 2018 diag-bz-npu-F26
82725888 Aug 24 06:18:24 2018 diag-sup3dc3-bz-F26.bin
1048576 Aug 24 05:47:10 2018 diag_test_file
34646 Jan 28 14:45:50 2019 ethpm_act_logs.log
270463 Jan 28 14:47:51 2019 ethpm_im_tech.log
30627 Jan 28 14:46:50 2019 ethpm_mts_details.log
73 Jan 28 14:46:50 2019 ethpm_syslogs.log
1935271 Jan 28 14:47:50 2019 ethpm_tech.log
12831 Dec 07 15:57:20 2018 log1
4096 Feb 07 13:13:47 2019 lost+found/
4421896 May 02 19:32:22 2019 m9700-sf4ek9-dplug-mz.8.4.1.bin
4421857 May 07 12:18:16 2019 m9700-sf4ek9-dplug-mz.8.4.1.bin
433304076 May 02 19:47:52 2019 m9700-sf4ek9-mz.8.4.1.bin
1548886 May 02 19:47:58 2019 m9700-sf4ek9-mz.8.4.1.tar.gz
433423429 May 07 12:33:27 2019 m9700-sf4ek9-mz.8.4.1.bin
1548937 May 07 12:33:35 2019 m9700-sf4ek9-mz.8.4.1.tar.gz
4096 Mar 26 09:54:14 2019 scripts/
1286622 Mar 21 15:53:25 2019 sysmgrconfig
11082 Aug 24 06:14:41 2018 temp.log
Usage for bootflash://sup-local
3213733888 bytes used
500277248 bytes free
3714011136 bytes total
Note Before downloading and installing Cisco MDS NX-OS software, verify that the release is supported by your Cisco MDS reseller. If you purchased support from a Cisco reseller, contact them directly for more information. Otherwise, contact Cisco Technical support: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
Step 10 If you need more space on the active supervisor module bootflash, delete the files that are not required to make space available:
433304076 May 02 19:47:52 2019 m9700-sf4ek9-mz.8.4.1.bin
1548886 May 02 19:47:58 2019 m9700-sf4ek9-mz.8.4.1.tar.gz
433423429 May 07 12:33:27 2019 m9700-sf4ek9-mz.8.4.1.bin
1548937 May 07 12:33:35 2019 m9700-sf4ek9-mz.8.4.1.tar.gz
4096 Mar 26 09:54:14 2019 scripts/
1286622 Mar 21 15:53:25 2019 sysmgrconfig
11082 Aug 24 06:14:41 2018 temp.log
Usage for bootflash://sup-local
3213733888 bytes used
500277248 bytes free
3714011136 bytes total
switch(standby)# exit (to return to the active supervisor)
Step 12 If you need more space on the standby supervisor module bootflash on a Cisco MDS 9700 Series Multilayer switch, delete the files that are not required to make space available:
Reason: Reset triggered due to Switchover**************************************************************
Step 19 Verify that your switch is running compatible hardware. For more information, see the corresponding version of the Cisco MDS 9000 Series Release Notes.
Step 20 Perform the upgrade by running the install all command.
The following example displays the result of the install all command if the system and kickstart files are specified locally. The example shows the command issued on a Cisco MDS 9700 Series Multilayer switch.
switch# install all kickstart m9700-sf4ek9-kickstart-mz.8.4.1.bin system m9700-sf4ek9-mz.8.4.1.bin
Installer will perform compatibility check first. Please wait.
Verifying image bootflash:/m9700-sf4ek9-kickstart-mz.8.4.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9700-sf4ek9-mz.8.4.1.bin for boot variable "system".
[####################] 100% -- SUCCESS
Performing module support checks.
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "lctsh" version from image bootflash:/m9700-sf4ek9-mz.8.4.1.bin
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9700-sf4ek9-mz.8.4.1.bin
[####################] 100% -- SUCCESS
Extracting "lc2dce-mds" version from image bootflash:/m9700-sf4ek9-mz.8.4.1.bin
[####################] 100% -- SUCCESS
Extracting "slc4xb" version from image bootflash:/m9700-sf4ek9-mz.8.4.1.bin
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9700-sf4ek9-mz.8.4.1.bin
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9700-sf4ek9-kickstart-mz.8.4.1.bin
[####################] 100% -- SUCCESS
Extracting "slcf32" version from image bootflash:/m9700-sf4ek9-mz.8.4.1.bin
Kickstart digital signature verification Successful
Image verification OK
INIT: version 2
boot device node /dev/sda
obfl flash device node /dev/sdb
log flash device node /dev/sdc
Checking obfl filesystem.
Checking all filesystems..r.r.r..r done.
Mounting Log Dir /logflash
mounting Log 0
Starting mcelog daemon
reCreating logflash directories
Loading system software
/bootflash//m9700-sf4ek9-mz.8.4.1.bin read done
System image digital signature verification successful.
Uncompressing system image: bootflash:/m9700-sf4ek9-mz.8.4.1.bin Fri Mar 23 15:40:22 IST 2019
blogger: nothing to do.
C
..done Fri Mar 23 15:40:27 IST 2019
INIT: Entering runlevel: 3
Starting portmap daemon...
starting statd: done
starting 8 nfsd kernel threads: done
starting mountd: done
2019 Mar 23 15:40:58 switch %USBHSD-2-MOUNT: logflash: online
2019 Mar 23 15:41:12 switch %LICMGR-2-LOG_LIC_NO_LIC: No license(s) present for feature ENTERPRISE_PKG. Application(s) shut down in 96 days.
Continuing with installation, please wait
Module 6: Waiting for module online.
-- SUCCESS
2019 Mar 23 15:42:35 switch %KERN-2-SYSTEM_MSG: [ 203.622504] Switchover started by redundancy driver - kernel
2019 Mar 23 15:42:36 switch %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active (pre-start phase).
2019 Mar 23 15:42:36 switch %SYSMGR-2-HASWITCHOVER_START: Supervisor 6 is becoming active.
2019 Mar 23 15:42:36 switch %SYSMGR-2-SWITCHOVER_OVER: Switchover completed.
2019 Mar 23 15:42:37 switch %PLATFORM-1-PFM_ALERT: Disabling ejector based shutdown on sup in slot 6
2019 Mar 23 15:42:41 switch %LICMGR-2-LOG_LIC_NO_LIC: No license(s) present for feature ENTERPRISE_PKG. Application(s) shut down in 96 days.
2019 Mar 23 15:42:41 switch %LICMGR-2-LOG_LIC_NO_LIC: No license(s) present for feature MAINFRAME_PKG. Application(s) shut down in 120 days.
2019 Mar 23 15:42:41 switch %LICMGR-2-LOG_LICAPP_NO_LIC: Application Fabric Binding running without MAINFRAME_PKG license, shutdown in 120 days
2019 Mar 23 15:42:42 switch %CALLHOME-2-EVENT: LICENSE_ALERT
Module 2: Non-disruptive upgrading.
[# ] 0%2019 Mar 23 15:49:27 switch %PLATFORM-1-PFM_ALERT: Enabling ejector based shutdown on sup in slot 6
2019 Mar 23 15:52:05 switch %PMON-SLOT2-2-PMON_CRIT_INFO: Port Monitor Critical Information: Config download success.
[####################] 100% -- SUCCESS
Module 3: Non-disruptive upgrading.
[####################] 100% -- SUCCESS
Module 4: Non-disruptive upgrading.
[# ] 0%2019 Mar 23 15:57:44 switch %PMON-SLOT4-2-PMON_CRIT_INFO: Port Monitor Critical Information: Config download success.
[####################] 100% -- SUCCESS
Module 10: Non-disruptive upgrading.
[# ] 0%2019 Mar 23 16:00:00 switch %PMON-SLOT10-2-PMON_CRIT_INFO: Port Monitor Critical Information: Config download success.
[####################] 100% -- SUCCESS
Install has been successful.
switch# You have now upgraded the Cisco NX-OS software in your switch.
Upgrading to Cisco MDS NX-OS Release 8.x on a Cisco MDS Fabric Switch
This section describes how to perform nondisruptive upgrades on the following Cisco MDS fabric switches:
Cisco MDS 9132T Multilayer Fabric Switch
Cisco MDS 9148T Multilayer Fabric Switch
Cisco MDS 9148S Multilayer Fabric Switch
Cisco MDS 9220i Multilayer Fabric Switch
Cisco MDS 9250i Multiservice Fabric Switch
Cisco MDS 9396S Multilayer Fabric Switch
Cisco MDS 9396T Multilayer Fabric Switch
Guidelines and Limitations for a Nondisruptive Upgrade on a Cisco MDS Fabric Switch
Before attempting to upgrade software images on the fabric switches, follow these guidelines:
During the upgrade, the fabric must be stable.
Do not perform the following configuration activities during an upgrade:
– Zoning changes
– Telnet sessions
– Schedule changes
– Switch cabling
– Addition or removal of physical devices
Configure the Fabric Shortest Path First (FSPF) timers to the default value of 20 seconds.
If Cisco Fabric Services commits are pending in the fabric, the upgrade is aborted.
If a zone server merge is in progress, the upgrade is aborted.
If the upgrade is aborted due to a service not being ready for an upgrade, you are prompted to enter the show install all failure-reason command to identify the reason.
Use the Software Install wizard to check whether sufficient space is available in the system to load the new images. Depending on the available space, you must either terminate the upgrade or proceed with a disruptive upgrade.
Prior to upgrade or downgrade, reset the switch's logging levels to the system defaults via the no logging level all configuration command. If this is not done, the upgrade or downgrade may be disruptive due to excessive logging causing control plane downtime exceeding 80 seconds. Before entering the no logging level all command, ensure that the switch's current logging configuration is saved. This will need to restored after the upgrade or downgrade. Follow these steps:
1. Enter the show running-config | i “logging level” command and save the output. These are the switch's current settings.
2. Enter the no logging level all command in configuration mode.
3. Perform upgrade or downgrade.
4. Restore logging level configuration using the output that was saved from Step 1.
When the installation is completed, the supervisor kickstart image, supervisor system image, module image, and the system BIOS are all updated.
Nondisruptive upgrade on fabric switches disrupt the control plane for about 80 seconds. The software upgrade can be disruptive, if the upgrade process goes beyond the period it can be stopped gracefully, or if a failure occurs.
If Virtual Router Redundancy Protocol (VRRP) is running on the mgmt0 interface, and the switch being upgraded is the master, a new master is selected. This situation cannot be avoided because the mgmt0 interface goes down when the control plane goes down.
On the Cisco MDS 18/4-port Multiservice Module, upgrading the 4-Gigabit Ethernet ports for the hybrid Supervisor 18/4 module is disruptive.
Perform the upgrade process by using the console port. This method enables you to log your session to a file (in case you need it later for troubleshooting). Telnet sessions are lost when the switch is rebooted. Therefore, if you want to view the process in its entirety, ensure that you use the console port.
Before performing an upgrade, use the show install all impact command to view the effect of updating the system from the running image to another specified image.
To upgrade to Cisco MDS NX-OS Release 8.4(1) from an earlier 8.x release, on a Cisco MDS fabric switch, perform the following steps:
Step 1 Verify that the system image files for the upgrade are present on the active supervisor module bootflash:
25947136 Nov 09 13:41:43 2018 m9250-s5ek9-kickstart-mz.8.3.1.bin
25970176 Jan 17 14:10:47 2019 m9250-s5ek9-kickstart-mz.8.3.2.bin
26126848 May 07 11:51:20 2019 m9250-s5ek9-kickstart-mz.8.4.1.bin
Usage for bootflash://sup-local
2838728704 bytes used
520916992 bytes free
3359645696 bytes total
Step 2 If the software image file is not present, download it from an FTP or TFTP server to bootflash. You can obtain the software image file from the Cisco.com Software Download Center at http://www.cisco.com/cisco/software/navigator.html
Step 5 Save the configuration using the copy running-config startup-config command:
switch# copy running-config startup-config
You can also back up your existing configuration to a file, using the copy running-config bootflash:backup_config.txt command. You can add a date reference to the.txt filename to identify the file later.
1 b8-38-61-4a-25-c0 to b8-38-61-4a-25-cf JAF1804AAFG
Step 11 To display the status of a nondisruptive upgrade on a fabric switch, use the show install all status command. The command output displays the status only after the switch has rebooted with the new image. All the actions preceding the reboot are not captured in this output because when you enter the install all command using a Telnet session, the session is disconnected when the switch reboots. When you reconnect to the switch through a Telnet session, the upgrade may already be complete, in which case, the output displays the status of the upgrade.
switch# show install all status
This is the log of last installation.
Continuing with installation process, please wait.
The login will be disabled until the installation is completed.
Status for linecard upgrade.
-- SUCCESS
Performing supervisor state verification.
-- SUCCESS
Install has been successful
Troubleshooting a Nondisruptive Upgrade on a Fabric Switch
When a nondisruptive upgrade begins, the system notifies all the services that an upgrade is about to start, and finds out whether the upgrade can proceed. If a service cannot allow the upgrade to proceed immediately, for example, if Fabric Shortest Path First (FSPF) timers are not configured to the default value, or a Cisco Fabric Services operation is in progress, the service terminates the upgrade. If such a situation occurs, you are prompted to enter the show install all failure-reason command to determine the reason why the upgrade cannot proceed.
Do you want to continue with the installation (y/n)? [n] y
Please issue "show install all failure-reason" to find the cause of the failure.<---system prompt to enter the show all failure-reason command.
Install has failed. Return code 0x401E0066 (request timed out).
Please identify the cause of the failure, and try 'install all' again.
switch# show install all failure-reason
Service: "cfs" failed to respond within the given time period.
When the upgrade is in progress, if any failures occur, for example, if a save runtime state failure or module upgrade failure occurs, the switch is rebooted disruptively because the changes cannot be rolled back. In this case, the upgrade fails, but you are not prompted to enter the show install all failure-reason command because the command does not yield any useful information.
If you need additional information to determine why an upgrade is unsuccessful, you can obtain the details by using the show tech-support command output, and from the console output from the installation, if available.
Moving From an NPE Image to a non-NPE Image and Vice Versa
The following section describes how to upgrade from a no payload encryption (NPE) image to a non-NPE image and vice versa.
Note ● If the image file name includes npe text, the image is an NPE image. If the image file name does not include npe text, the image is a non-NPE image.
If you are moving from using an NPE image to a non-NPE image, we recommend that you use the corresponding non-NPE Cisco MDS NX-OS release image and vice versa. If you are upgrading from one release of Cisco MDS NX-OS to a newer release, and as part of this activity, you are moving from using an NPE image to a non-NPE image, we recommended that you first upgrade the existing NPE Cisco MDS NX-OS release image and then upgrade to the respective non-NPE Cisco MDS NX-OS release image and vice versa.
Use the console connection for firmware upgrades. Be aware that if you are upgrading through the management interface, you must have a working connection to both supervisors, as this process causes a switchover and the current standby supervisor will be active after the upgrade.
Step 1 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 Systems user name and password.
Note Unregistered Cisco.com users cannot access the links provided in this document.
Step 2 Verify the following physical connections for the switch:
The console port is physically connected to a computer terminal (or terminal server).
The management 10/100/1000 Ethernet port (mgmt0) is connected to an external hub, switch, or router.
On switches with dual supervisor modules, both supervisor modules must have the management 10/100/1000 Ethernet ports (mgmt0) connected to an external hub, switch, or router.
These procedures are specified in the hardware installation guide for the required product.
Step 3 Log in to the switch.
Step 4 Issue the copy running-config startup-config command to store your current running configuration. You can also create a backup of your existing configuration to a file by issuing the copy running-config bootflash:backup_config.txt command.
Step 5 Verify that the requested license files installed in the switch are displayed in response to the show license usage command.
Note The switch is initially shipped with the required licenses installed in the system; however, the initial license file will not cover unlicensed features that may be used during the grace period. If no license is displayed at this point, perform Step 6 and Step 7 to install the required licenses. If the required licenses are displayed at this point, skip Step 6 and Step 7 and move to Step 8.
The example CLI output for a valid license follows:
Step 6Install licenses (if necessary) to ensure that the required features are available on the switch. Perform the following steps:
a. Use the show license host-id command to obtain the serial number for your switch. The host ID is also referred to as the switch serial number.
switch# show license host-id
License hostid: VDH=JAF1721AEQG
Tip Use the entire ID that appears after the colon (:) sign. In this example, the host ID is VDH=JAF1721AEQG.
b. Obtain your Claim Certificate or the Proof of Purchase document. This document accompanies every Cisco MDS switch.
c. Locate the Product Authorization Key (PAK) from the Claim Certificate or Proof of Purchase document.
d. Locate the website URL from the Claim Certificate or Proof of Purchase document.
e. Access the specified URL that applies to your switch and enter the switch serial number and the PAK. The license key file is sent to you by email. The license key file is digitally signed to authorize its use only on the switch for which it was requested. The requested features are also enabled once the NX-OS software on the specified switch accesses the license key file.
Caution Install the license file in the specified Cisco MDS 9000 Family switch without making any modifications.
Step 7Install the license key file when you receive it by email. Perform the following steps:
a. Copy the license file to bootflash using TFTP or SCP.
b. Perform the installation by issuing the install license command on the active supervisor module from the switch console.
Note If you provide a target name for the license key file, the file is installed with the specified name. Otherwise, the file name specified in the license key file is used to install the license.
c. Exit the switch console.
Step 8Ensure that the required space is available in the bootflash: directory for the image file(s) to be copied using the dir bootflash: command. Use the delete bootflash: filename command to remove unnecessary files.
Note Before downloading and installing Cisco NX-OS software, verify that the release is supported by your Cisco System MDS reseller. If you purchased support through a Cisco Systems reseller, contact them directly for more information. Otherwise, contact Cisco Technical support at this URL: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
switch(standby)# exit (to return to the active supervisor)
Step 11 For switches with dual supervisor modules, if you need more space on the standby supervisor module bootflash on a switch, delete unnecessary files to make space available.
Step 17 Issue the boot kickstart bootflash : filename and boot system bootflash : filename commands to change the boot variables to point to the new image.
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.5(1)
Note Before downgrading to releases prior to Cisco MDS NX-OS Release 8.5(1), ensure that you clear the OBFL log using the clear logging onboard error-stats command.
Table 26 Nondisruptive Downgrade Paths from NX-OS Release 8.5(1)
To MDS NX-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
1. Downgrade directly to MDS NX-OS Release 8.4(2b)
2. Upgrade to MDS NX-OS Release 8.4(2c)
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
6.2(29) and above releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b), Release 8.4(2), Release 8.4(2a), or Release 8.4(2b)
2. Downgrade to the target release
6.2(13a) until 6.2(27)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
6.Downgrading from Cisco MDS NX-OS Release 8.5(1) directly to Cisco MDS NX-OS Release 8.4(2c) is not supported. To perform this downgrade, set the boot variables and reload the switch - this process is disruptive. To downgrade nondisruptively, first downgrade from Cisco MDS NX-OS Release 8.5(1) to Cisco MDS NX-OS Release 8.4(2b) and from there upgrade to Cisco MDS NX-OS Release 8.4(2c). For more information, see CSCvx99164.
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.4(2d)
Table 27 Nondisruptive Downgrade Paths from NX-OS Release 8.4(2d)
To MDS NX-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases except 8.5(1)
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
6.2(29) and above releases
Downgrade to the target release
6.2(13a) until 6.2(27)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.4(2c)
Table 28 Nondisruptive Downgrade Paths from NX-OS Release 8.4(2c)
To MDS NX-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases except 8.5(1)
Downgrade directly from MDS NX-OS 8.4(2c)
MDS NX-OS Release 8.1(1a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
MDS NX-OS Release 6.2(11e)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 8.1(1a)
3. Downgrade to the target release
MDS NX-OS Release 6.2(11d)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 8.1(1a)
3. Downgrade to the target release
MDS NX-OS Release 6.2(11c)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 8.1(1a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.4(2b)
Table 29 Nondisruptive Downgrade Paths from NX-OS Release 8.4(2b)
To MDS NX-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade directly from MDS NX-OS 8.4(2b)
MDS NX-OS Release 8.1(1a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
MDS NX-OS Release 6.2(11e)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 8.1(1a)
3. Downgrade to the target release
MDS NX-OS Release 6.2(11d)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 8.1(1a)
3. Downgrade to the target release
MDS NX-OS Release 6.2(11c)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 8.1(1a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.4(2a)
Table 30 Nondisruptive Downgrade Paths from NX-OS Release 8.4(2a)
To MDS NX-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
6.2(29) and above releases
Downgrade to the target release
6.2(13a) until 6.2(27)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.4(2)
Table 31 Nondisruptive Downgrade Paths from NX-OS Release 8.4(2)
To MDS NX-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
6.2(29) and above releases
Downgrade to the target release
6.2(13a) until 6.2(27)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.4(1a)
Table 32 Nondisruptive Downgrade Paths from NX-OS Release 8.4(1a)
To MDS NX-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(13a) and above releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.4(1)
Table 33 Nondisruptive Downgrade Paths from NX-OS Release 8.4(1)
To MDS NX-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(13a) and above releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.3(2)
Table 34 Nondisruptive Downgrade Paths from NX-OS Release 8.3(2)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(13a) and above releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.3(1)
Table 35 Nondisruptive Downgrade Paths from NX-OS Release 8.3(1)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(13a) and above releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.2(2)
If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before downgrading to Cisco MDS NX-OS Release 8.2(2).
Table 36 Nondisruptive Downgrade Paths from NX-OS Release 8.2(2)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(13a) and above releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.2(1)
If you have the SAN analytics feature enabled, ensure that you disable the SAN analytics feature using the no feature analytics command before downgrading to Cisco MDS NX-OS Release 8.2(1).
Table 37 Nondisruptive Downgrade Paths from NX-OS Release 8.2(1)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(13a) and above releases
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 8.1(1b)
2. Downgrade to MDS NX-OS Release 6.2(13a)
3. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.1(1b)
Table 38 Nondisruptive Downgrade Paths from NX-OS Release 8.1(1b)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
Downgrade to the target release
All 6.2(13a) and above releases
Downgrade to the target release
All 6.2(x) releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 6.2(13a)
2. Downgrade to the target release
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.1(1a)
Table 39 Nondisruptive Downgrade Paths from NX-OS Release 8.1(1a)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Paths and Ordered Downgrade Steps
NX-OS:
All 8.x releases
Downgrade to the target release
All 7.3(x) releases
Downgrade to the target release
All 6.2(13a) and above releases except 6.2(21)
Downgrade to the target release
6.2(21) 1
1. Downgrade directly to MDS NX-OS Release 6.2(23)
2. Downgrade to the target release
All releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 6.2(13a)
2. Downgrade to the target release
1. Downgrading specifically from MDS NX-OS Release 8.1(1a) to MDS NX-OS Release 6.2(21) is disruptive. For more information, see CSCvj40760.
Nondisruptive Downgrade Paths from Cisco MDS NX-OS Release 8.1(1)
Table 40 Nondisruptive Downgrade Paths from NX-OS Release 8.1(1)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Path and Ordered Downgrade Steps
NX-OS:
All 7.3(x) releases
Downgrade to the target release
All 6.2(13a) and above releases
Downgrade to the target release
All releases prior to 6.2(13a)
1. Downgrade directly to MDS NX-OS Release 6.2(13a)
2. Downgrade to the target release
Supported FICON Downgrade Paths for Cisco MDS NX-OS Releases
This section provides information on FICON downgrade paths that are supported for Cisco MDS NX-OS software Release 8.x. It includes the following topics:
Downgrading directly from Cisco MDS NX-OS Release 8.1(1) to releases before Cisco MDS NX-OS Release 6.2(9) is not supported. In such a scenario, we recommend that you first downgrade to Cisco MDS NX-OS Release 6.2(13a) or higher and then downgrade to the required release.
Downgrading directly from Cisco MDS NX-OS Release 8.1(1) to Cisco MDS NX-OS Release 7.3(0)DY(1) is not supported. In such a scenario, we recommend that you first downgrade to Cisco MDS NX-OS Release 7.3(0)D1(1) and then upgrade to 7.3(0)DY(1).
Downgrading directly from Cisco MDS NX-OS Release 8.1(1) to Cisco MDS NX-OS Release 7.3(1)DY(1) is not supported. In such a scenario, we recommend that you first downgrade to Cisco MDS NX-OS Release 7.3(0)D1(1) and then upgrade to 7.3(1)DY(1).
Downgrading from Cisco MDS NX-OS Release 8.1(1) is not supported if the FLOGI Scale Optimization feature is enabled on Cisco MDS 9718 Switches.
We do not recommend parallel In-Service Software Downgrade (ISSD) on Cisco MDS 9148S, Cisco MDS 9250i, and Cisco MDS 9396S fabric switches when these fabric switches are each other’s peers.
If you copy firmware using the SFTP or SCP clients after enabling the feature scp-server or feature sftp-server command on your switch, ensure that you close the SFTP or SCP connection using the no feature scp-server or no feature sftp-server command before performing ISSD. Otherwise, ISSD will be disruptive. To avoid this issue, we recommend that you transfer files to the switch using the copy command instead or using the DCNM client.
Prior to upgrade or downgrade, reset the switch's logging levels to the system defaults via the no logging level all configuration command. If this is not done, the upgrade or downgrade may be disruptive due to excessive logging causing control plane downtime exceeding 80 seconds. Before entering the no logging level all command, ensure that the switch's current logging configuration is saved. This will need to restored after the upgrade or downgrade. Follow these steps:
1. Enter the show running-config | i “logging level” command and save the output. These are the switch's current settings.
2. Enter the no logging level all command in configuration mode.
3. Perform upgrade or downgrade.
4. Restore logging level configuration using the output that was saved from Step 1.
To determine if high-bandwidth capability is enabled, use the show hardware fabric-mode command. The following example shows that the higher bandwidth capability is not activated:
switch# show hardware fabric-mode
Fabric mode supports only one configuration of 8G FC modules - 4/44 Host-Optimized 8G FC module.
switch#
The following example shows that the higher bandwidth capability is activated:
switch# show hardware fabric-mode
fabric mode supports FCoE, Gen2 and above linecards
Note If you are downgrading from Cisco MDS NX-OS Release 9.2(1) or later releases to a release prior to Cisco MDS NX-OS Release 9.2(1), ensure that you use the clear logging onboard txwait command after downgrading. Otherwise, logging to the OBFL TxWait file may cease with an error. For more information, see the Cisco MDS 9000 Series Interfaces Configuration Guide, Release 9.x.
Downgrade Guidelines for Cisco MDS 9396S Switch
Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(0)D1(1) or Cisco MDS NX-OS Release 6.2(13a) is not supported on a Cisco MDS 9396S Switch which has DS-CAC-1200W as a power supply unit (PSU) and DS-C96S-FAN-I as port side intake fan tray.
Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 6.2(13) is not supported on the Cisco MDS 9396S Multilayer Fabric Switch. The minimum recommended image for Cisco MDS 9396S Multilayer Fabric Switch is 6.2(13a).
To downgrade from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(x) on a Cisco MDS 9396S Series switch, you must first disable the extended receive BB_credit configuration using the no feature fcrxbbcredit extended command. After the downgrade process is complete, enable the extended receive BB_credit configuration using the feature fcrxbbcredit extended command.
If you are downgrading from Cisco MDS NX-OS 8.3(x) release to Cisco MDS NX-OS 8.2(x) release, disable the SAN analytics feature using the no feature analytics command.
Downgrade Guidelines for Cisco MDS 9250i Switch
Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(0)D1(1), or 6.2(13a) and lower is not supported on a Cisco MDS 9250i Switch which has only one online PSU.
Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(0)D1(1), or 6.2(13a) and lower on a Cisco MDS 9250i Switch with two online PSUs results in loss of N:N grid redundancy. The switch will run in non-redundant mode.
Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(0)D1(1), or 6.2(13a) and lower on a Cisco MDS 9250i Switch with three online PSUs results in loss of N:N grid redundancy. The switch will run in N+1 power redundant mode.
Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.x
To downgrade from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(x) or an earlier release, perform the following steps:
Step 1 Verify that the system image files for the downgrade are present in the active supervisor module bootflash:
switch# dir bootflash:
26126848 May 07 11:51:20 2019 m9250-s5ek9-kickstart-mz.8.4.1.bin
107587249 Mar 30 15:42:52 2014 m9250-s5ek9-mz.6.2.7.bin
Step 2 If the software image file is not present, download it from an FTP or TFTP server to the active supervisor module bootflash. You can obtain the software image file from the Cisco.com Software Download Center: http://www.cisco.com/cisco/software/navigator.html
Step 5 Run the show incompatibility system image-filename c ommand to determine if you must disable the features not supported by a release earlier than release to be installed.
switch# show incompatibility system bootflash:m9250-s5ek9-mz.7.3.0.D1.1.bin
Checking incompatible configuration(s):
.
..
...
no incompatible configurations
switch#
Step 6 Save the configuration using the copy running-config startup-config command:
switch# copy running-config startup-config
Step 7 Run the install all command to downgrade the software:
switch# install all kickstart m9250-s5ek9-kickstart-mz.7.3.0.D1.1.bin
system m9250-s5ek9-mz.7.3.0.D1.1.bin
install all kickstart m9250-s5ek9-kickstart-mz.8.1.1b.bin system m9250-s5ek9-mz.8.1.1b.
bin
Installer will perform compatibility check first. Please wait.
Verifying image bootflash:/m9250-s5ek9-kickstart-mz.8.1.1b.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9250-s5ek9-mz.8.1.1b.bin for boot variable "system".
[####################] 100% -- SUCCESS
Performing module support checks.
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9250-s5ek9-mz.8.1.1b.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9250-s5ek9-kickstart-mz.8.1.1b.bin.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9250-s5ek9-mz.8.1.1b.bin.
1 f0-f7-55-29-50-60 to f0-f7-55-29-50-6f JAF1626BCQH
* this terminal session
switch#
Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 6.2(x)
Cisco MDS 9700 Series Multilayer Director with a 48-Port 10-Gigabit FCoE Module and VLAN Configurations
To downgrade from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release, 6.2(9) and earlier release, perform the following steps:
Step 1 Use the purge module running-config command to remove FCoE-related configurations, if any, from each 48-port 10-Gigabit FCoE module that is removed.
Step 2 Remove all 48-port 10-Gigabit FCoE modules from the Cisco MDS 9710 chassis.
Step 3 Remove all the VLANs that you have created and verify that no VLAN or VSAN mapping exists in the switch, using the show vlan and show vlan fcoe commands.
Step 4 Remove all the Ethernet port channels and verify that no Ethernet port channel exists in the switch, using the show interface brief and show ethernet-port-channel database commands.
Step 5 Remove all the virtual Fiber Channels (vFCs) and verify that no vFC exists in the switch, using the show interface brief command.
Cisco MDS 9700 Series Multilayer Director with a 24-Port 40-Gigabit FCoE Module and VLAN Configurations
To downgrade from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 6.2(9) and earlier releases, perform the following steps:
Step 1 Remove all the 24-port 40-Gigabit FCoE modules from the Cisco MDS 9710 chassis.
Step 2 Use the purge module running-config command to remove FCoE-related configuration, if any, from each 24-port 40-Gigabit FCoE module that is removed.
Step 3Remove all the VLANs that you have created and verify that no VLAN or VSAN mapping exists in the switch, using the show vlan and show vlan fcoe commands.
Step 4 Remove all the Ethernet port channels and verify that no Ethernet port channel exists in the switch, using the show interface brief and show ethernet-port-channel database commands.
Step 5 Remove all the virtual fibre channels (vFCs) and verify that no vFC exists in the switch, using the show interface brief command.
Cisco MDS 9700 Series Multilayer Director with Cisco MDS 24/10-Port SAN Extension Module
To downgrade from Cisco MDS NX-OS Release 8.x with Cisco MDS 24/10-port SAN extension module to Cisco MDS NX-OS Release 6.2(9) and earlier releases, perform the following steps:
Step 1 Use the poweroff module number command to power off the module.
Step 2 Use the purge module slot running-config command for Cisco MDS 24/10-port SAN extension module to remove the configuration for the module from the running configuration.
Step 3 Use the no feature fcip command to disable Fibre Channel over IP (FCIP) on the switch.
Step 4 Remove the module and verify that the module does not exist in the switch, using the show module command.
Cisco MDS 9700 Series Multilayer Director with Cisco MDS 48-Port 32-Gbps Fibre Channel Switching Module
To downgrade from Cisco MDS NX-OS Release 8.x with MDS 48-port 32-Gbps Fibre Channel Switching Module to Cisco MDS NX-OS Release 6.2(x) and Cisco MDS NX-OS Release 7.3(x), perform the following steps:
Step 1 Use the poweroff module number command to power off the module.
Step 2 Use the purge module slot running-config command in the switch for Cisco MDS 48-port 32-Gbps Fibre Channel Switching Module to remove the module’s configuration from the running configuration.
Step 3 Remove the module and verify that the module does not exist on the switch, using the show module command.
Related Documentation
The documentation set for the Cisco MDS 9000 Series Multilayer switches is available at:
Cisco MDS 9000 Series I/O Acceleration Configuration Guide
Cisco MDS 9000 Series SANTap Deployment Guide
Cisco MDS 9000 Series Data Mobility Manager Configuration Guide
Cisco MDS 9000 Series Storage Media Encryption Configuration Guide
Troubleshooting and Reference
Cisco MDS 9000 Series and Nexus 7000 Series System Messages Reference
Cisco MDS 9000 Series SAN-OS Troubleshooting Guide
Cisco MDS 9000 Series NX-OS MIB Quick Reference
Cisco DCNM for SAN Database Schema Reference
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly, What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
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.
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: www.cisco.com/go/trademarks. 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)