PDF(1.2 MB) View with Adobe Reader on a variety of devices
Updated:March 17, 2017
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 6.2(x)
Last Published: April 15, 2019
This document describes how to upgrade to Cisco NX-OS Release 6.2(x) from Release 5.2(x), and how to downgrade from Cisco NX-OS Release 6.2(x) to Release 5.2(x).
Note All command-line interface (CLI) session examples provided in this document are only intended for reference. The actual switch output differs based on your switch model.
About Software Images
Each switch is shipped with the Cisco MDS NX-OS operating system for Cisco MDS 9000 Family 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. You must specify the variable and the respective image to upgrade or downgrade your switch. Both images are not always required for each install.
Note To download new Cisco MDS 9000 Family software including Cisco NX-OS and Cisco DCNM management software, refer to the Storage Networking Software download site at: http://www.cisco.com/cisco/software/navigator.html
The software image install procedure is dependent on the following factors:
Software images—The kickstart and system image files reside in directories or folders that can be accessed from the Cisco MDS 9000 Family 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—There are single or dual supervisor modules.
Note On switches with dual supervisor modules, both supervisor modules must have Ethernet connections on the management interfaces (mgmt 0) to maintain connectivity when switchovers occur during upgrades and downgrades. Refer to the Cisco MDS 9500 Series Hardware Installation Guide.
Components Supported
Table 1 lists the NX-OS software part numbers and hardware components supported by the Cisco MDS 9000 Series.
Table 1 Cisco MDS 9000 Series Supported Software and Hardware Components
Enterprise Package for one Cisco MDS 9700 Series Multilayer Director
MDS 9700 Series
M97FIC1K9
Cisco MDS 9700 Mainframe Package license for one MDS 9700 Switches
MDS 9700 Series
M9500SSE184K9z
Storage Services Enabler License for one MSM-18/4 module
MDS 9500 Series
M9300ENT1K9
Cisco MDS 9300 Series Enterprise Package
MDS 9396S Switch
DCNM-SAN-M93-K9
Cisco Prime Data Center Network Manager
MDS 9396S Switch
M9200ENT1K9
Cisco MDS 9200 Series Enterprise Package
MDS 9200 Series
DCNM-SAN-M92-K9
Cisco Prime Data Center Network Manager
MDS 9200 Series
M9250IIOA
Cisco MDS 9250i I/O Accelerator Services package
MDS 9250i Switch
M9250IDMMK9
Cisco MDS 9250i Data Mobility Manager package
MDS 9250i Switch
M9250IDMMT6M
Cisco MDS 9250i DMM License - 6-month period
MDS 9250i Switch
M9200FIC1K9
Cisco MDS 9200 Series Mainframe Package
MDS 9200 Series
M9200XRC
Cisco MDS 9200 XRC Acceleration Package for IBM series z, spare
MDS 9200 Series
M9222ISSE1K9
Storage Services Enabler License
MDS 9222i Switch
M9200SSE184K9
Storage Services Enabler License for one MSM-18/4 module
MDS 9222i Switch
M95DMM184K9
Data Mobility Manager License for one MSM-18/4 module
MDS 9500 Series
M9222IDMMK9
Data Mobility Manager License for Cisco MDS 9222i
MDS 9222i Switch
M92DMM184K9
Data Mobility Manager License for one MSM-18/4 module
MDS 9222i Switch
M95DMM184TSK9
Data Mobility Manager for one MSM-18/4 module — Time limited to 180 days only
MDS 9500 Series
M9222IDMMTSK9
Data Mobility Manager — Time limited to 180 days only
MDS 9222i Switch
M92DMM184TSK9
Data Mobility Manager for one MSM-18/4 module — Time limited to 180 days only
MDS 9222i Switch
M92SSESSNK9
Cisco Storage Services Enabler License for SSN-16 (1 engine)
MDS 9222i Switch
M95SSESSNK9
Cisco Storage Services Enabler License for SSN-16 (1 engine)
MDS 9500 Series
M92SMESSNK9
Cisco Storage Media Encryption License for SSN-16 (1 engine)
MDS 9222i Switch
M95SMESSNK9
Cisco Storage Media Encryption License for SSN-16 (1 engine)
MDS 9500 Series
M92IOASSN
Cisco I/O Accelerator License for SSN-16 (1 engine)
MDS 9222i Switch
M95IOASSN
Cisco I/O Accelerator License for SSN-16 (1 engine)
MDS 9500 Series
M92IOA184
Cisco I/O Accelerator License for MSM-18/4
MDS 9222i Switch
M95IOA184
Cisco I/O Accelerator License for MSM-18/4
MDS 9500 Series
M9222IIOA
Cisco I/O Accelerator License for Cisco MDS 9222i base switch
MDS 9222i Switch
M92EXTSSNK9
Cisco SAN Extension License for SSN-16 (1 engine)
MDS 9222i Switch
M95EXTSSNK9
Cisco SAN Extension License for SSN-16 (1 engine)
MDS 9500 Series
M9200XRC
Cisco XRC Acceleration
MDS 9200 Series
M9500XRC
Cisco XRC Acceleration
MDS 9500 Series
Chassis
DS-C9710
Cisco MDS 9710 Multilayer Director (10-slot multilayer director with 2 half-width slots for Supervisor modules, with 8 slots available for switching modules — SFPs sold separately)
MDS 9710 Switch
DS-C9706
Cisco MDS 9706 Multilayer Director (6-slot multilayer director with 2 half-width slots for Supervisor modules, with 4 slots available for switching modules — SFPs sold separately)
MDS 9706 Switch
DS-C9513
Cisco MDS 9513 Multilayer Director (13-slot multilayer director with 2 slots for Supervisor modules, with 11 slots available for switching modules — SFPs sold separately)
MDS 9513 Switch
DS-C9509
Cisco MDS 9509 Multilayer Director (9-slot multilayer director with 2 slots for Supervisor modules, with 7 slots available for switching modules — SFPs sold separately)
MDS 9509 Switch
DS-C9506
Cisco MDS 9506 Multilayer Director (6-slot multilayer director with 2 slots for Supervisor modules, with 4 slots available for switching modules — SFPs sold separately)
The Cisco MDS 9250i offers up to forty 16-Gbps Fibre Channel ports, two 10 Gigabit Ethernet IP storage services ports, and eight 10 Gigabit Ethernet Fibre Channel over Ethernet (FCoE) ports in a fixed two-rack-unit (2RU) form factor.
MDS 9250i Switch
DS-C9222i-K9
Cisco MDS 9222i Multilayer Fabric Switch (3-rack-unit (3RU) semimodular multilayer fabric switch with 18 4-Gbps Fibre Channel ports, 4 Gigabit Ethernet ports, and a modular expansion slot for Cisco MDS 9000 Series Switching and Services modules)
Cisco MDS 9000 Series 16-Port Storage Services Node (SSN-16) — 16 fixed 1-Gbps Ethernet ports, plus 4 service engines that support 16-Gigabit Ethernet IP storage services ports.
MDS 9500 Series
MDS 9222i Switch
DS-X9304-18K9
Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4) — 18-port, 4-Gbps Fibre Channel plus 4-port Gigabit Ethernet IP services and switching module with SFP LC connectors
Selecting the Correct Software Image for an MDS 9700 Series Switch
Table 1-8 lists the image filename for a Cisco MDS 9700 Series switch.
Table 1-8 Software Images for the MDS 9710 Switch
Cisco MDS 9710 Switch Type
Supervisor Module Type
Naming Convention
MDS 9710
Supervisor-3 module
Filename begins with m9700-sf3ek9
MDS 9706
Supervisor-3 module
Filename begins with m9700-sf3ek9
Installing Cisco NX-OS Release 6.2(x) Software on a New Cisco MDS Switch
Note If the management 10/100/1000 Ethernet port (mgmt0) interface of the Cisco MDS 9700 Series switches 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 it. Perform this process before commissioning the device into production as this process is disruptive to user traffic if it is applied to the active supervisor of a system. Ensure an active console connection to the supervisor as this process will remove the IPv4 address of the mgmt0 interface.
To install the latest Cisco NX-OS Release 6.2(x) software images on a new Cisco MDS 9000 Family switch, follow these steps:
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 username and password.
Note Unregistered Cisco.com users cannot access the links provided in this document.
Step 2 Verify the following physical connections for the new Cisco MDS 9000 Family 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.
Information on physical connections can be found in the Cisco MDS 9000 Series Hardware Installation Guides.
Note On switches with dual supervisor modules, both supervisor modules must have Ethernet connections on the management interfaces (mgmt 0) to maintain connectivity when switchovers occur during upgrades and downgrades. Refer to the Cisco MDS 9500 Series Hardware Installation Guide.
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 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 Family switch. The switch boots automatically and the switch prompt appears in your terminal window.
Step 5Obtain the IP address, subnet mask, and default gateway information that is required for the Cisco MDS 9000 Family switch to communicate over the supervisor module Ethernet interface. This information is required to configure and manage the switch.
Tip You have the option to change the default password during the initial setup process. All Cisco MDS 9000 Family switches have the network administrator as a default user (admin) and a default password (admin). You cannot change the default user at any time.
Step 6 Complete the System Admin Account Setup.
Tip If you create a short, easy-to-decipher password, your password is rejected. Be sure to configure a strong password as shown in the sample configuration. Passwords are case sensitive. You must explicitly create a password that meets the requirements listed in the “Characteristics of Strong Passwords” section in the “Configuring Users and Common Roles” chapter in the Cisco MDS 9000 Family NX-OS Security Configuration Guide.
---- System Admin Account Setup ----
Do you want to enforce secure password standard (yes/no) [y]: y
Enter the password for "admin":
Confirm the password for "admin":
Step 7 Enter yes to enter the setup mode and assign the information obtained in Step 5.
Note Press Ctrl-C at any prompt 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 skips to the next question.
The CLI configuration steps (using factory defaults) are 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 switches:
Network operator (network-operator)—Has permission to view the configuration only. 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 (in the network-admin role) besides the administrator’s account. The user name must contain non-numeric characters. Refer to the “Configuring User Accounts” section in the “Configuring Users and Common Roles” chapter in the Cisco MDS 9000 Family NX-OS Security Configuration Guide.
IPv4 address of the default gateway : 209.165.200.225
Configure advanced IP options? (yes/no) [n]: yes
Continue with In-band (vsan1) management configuration? (yes/no) [n]: n
Enable IP routing? (yes/no) [n]: yes
Configure static route? (yes/no) [n]: n
Note Be sure to configure the IP route, the IP default network address, and the IP default gateway address to enable 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 the Destination prefix: dest_prefix provided above 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
username admin password admin_pass role network-admin
username user_name password user_pass role network-admin
snmp-server community snmp_community ro
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 that 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. After this step, you can continue configuring the switch using the CLI or switch over to using the Cisco DCNM application. Refer to the Cisco DCNM Fundamentals Configuration Guide.
If you continue to use the CLI, the login prompt automatically appears in your terminal window.
Step 8 Log in to the switch using the new user name 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 will not cover unlicensed features that may be used during the grace period. Refer to the Cisco MDS 9000 Family NX-OS Licensing Guide.
The example CLI output for a valid license follows:
Step 10 Verify that the switch is running the latest Cisco NX-OS 6.2(x) software, depending on which you installed, by issuing the show version command.
If the latest Cisco NX-OS 6.2(x) software is not displayed, continue with upgrading or downgrading the switch as required to install the correct version. Refer to the appropriate section in this guide for upgrading or downgrading to specific versions.
Step 11 Verify the status of the modules on the switch using the show module command.
If your switch is running software that is earlier than Cisco NX-OS Release 5.2(x), you must upgrade to Release 6.2(x). Follow this upgrade path:
Release 5.0(x): upgrade to 5.2(x), and then upgrade to 6.2(x).
Release 4.1(x) or release 4.2(x): upgrade to Release 5.0(x), upgrade to Release 5.2(x) and then upgrade to Release 6.2(x).
Release 3.3(2), Release 3.3(3), Release 3.3(4x), and Release 3.3(5x), upgrade to release 4.1(x) or Release 4.2(x), then upgrade to Release 5.0(x), and then upgrade to Release 5.2(x), and then upgrade to 6.2(x).
Release 3.3(1c), all Release 3.2(x), all Release 3.1(x), and all Release 3.0(x), upgrade to release 3.3(5b), then upgrade to release 4.1(x) or release 4.2(x), then upgrade to Release 5.0(x), and then upgrade to Release 5.2(x), and then upgrade to 6.2(x).
NoteFor a nondisruptive upgrade, the switch must be running Cisco SAN-OS Release 3.3(5b) or later. A disruptive upgrade requires a switch reload.
Upgrading Guidelines
Observe these guidelines when upgrading software on a Cisco MDS 9500 Series Director switch:
Follow the upgrade path to Cisco NX-OS Release 6.2(x) specified in the Cisco MDS 9000 Series Release Notes for the particular release you intend to install.
When you replace a linecard with a different type of linecard, the ports revert to VSAN 1 and all the port configurations are lost.
Observe these guidelines when upgrading software on Cisco MDS 9148s, 9250i, 9396s, and 9700 Series Director switches:
Inserting smartoptics on Cisco MDS 9148s, 9250i, 9396s, and 9700 Series Director switches running an unsupported Cisco MDS NX-OS Release results in the port moving to error-disabled state.
Upgrading from Cisco MDS NX-OS Release 6.2(19) to any other unsupported release (higher or lower) with smartoptics links that are error disabled will keep the links in the error-disabled state, unless the links are physically removed and inserted to bring the links up.
Upgrading from Cisco MDS NX-OS Release 6.2(19) to any other unsupported release (higher or lower) with smartoptics links up and trunking will keep the links in trunking state.
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 before performing ISSU. Otherwise, ISSU will be disruptive. This issue is not seen when you transfer files from the switch using the copy command or when using the DCNM client.
Note Parallel In-Service Software Upgrade (ISSU) is not recommended on MDS 9148S, MDS 9250i and MDS 9396S fabric switches when these category of fabric switches are peers to each other.
Upgrade Process for an MDS 9700 Series Director
On the MDS 9710 Director, the high-level process to upgrade to Cisco NX-OS Release 6.2(x) and is as follows:
On the MDS 9513 switch, the high-level process to upgrade to Cisco NX-OS Release 6.2(x) and enable the increased bandwidth capabilities of the Generation 4 modules is as follows:
Step 2 Install Cisco MDS 9513 Fabric 3 modules in the MDS 9513 chassis. For additional information, see the “Migrating to Generation 4 8-Gbps Advanced Fibre Channel Switching Modules” section in the Cisco MDS 9500 Series Switch Hardware Installation Guide.
Step 3 If needed, reload the switch to enable increased bandwidth capabilities.
Step 3 Install a 8-Gbps Advanced Fibre Channel module.
Upgrading to Cisco NX-OS Release 6.2(x) on an MDS 9700 Series Switch
Note 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
To upgrade your switch to use the latest Cisco MDS NX-OS software on your Cisco MDS 9700 Series switch, follow these steps:
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 new Cisco MDS 9700 Series :
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 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. Refer to the “Using the Cisco NX-OS Setup Utility” chapter in the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.
Step 5 Verify that the requested license files installed in the switch are displayed in response to the show license usage command.
Step 6 Install 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 e-mail. The license key file is digitally signed to only authorize use 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.
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.
Step 8 Ensure 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# dir bootflash:
241410048 May 19 14:11:03 2014 0x501_eth-qos_core.4690
239902720 May 19 14:21:14 2014 0x501_eth-qos_core.6054
236326912 Jun 02 13:11:51 2014 0x501_eth-qos_core.6469
44946 Jun 02 13:12:08 2014 0x501_eth-qos_log.6469
196659318 Apr 03 17:15:00 2014 IMG_629_suh.gbin
37012992 Apr 03 17:12:51 2014 KS_629_suh.gbin
36800512 May 15 14:43:21 2014 KS_SA.bin
36800512 May 15 15:44:28 2014 KS_SA.gbin
196849390 May 15 18:48:29 2014 SUH.bin
36426752 May 15 18:50:28 2014 SUH_KS.bin
196852387 May 15 19:11:22 2014 SUH_NW.bin
212670 Feb 26 14:48:19 2014 ac_log
5047806 Dec 17 11:43:00 2013 cfs
92 Dec 18 17:51:39 2013 cfs_test.txt
3400551 May 30 14:08:06 2014 debug
3378033 Dec 17 11:40:16 2013 dp627
3366221 Jan 07 14:32:34 2014 dps
86850 Jun 02 13:09:38 2014 ethpm_act_logs.log
491521 Jun 02 13:11:39 2014 ethpm_im_tech.log
608 Jun 02 13:10:38 2014 ethpm_mts_details.log
73 Jun 02 13:10:38 2014 ethpm_syslogs.log
205691 Jun 02 13:11:38 2014 ethpm_tech.log
4096 Oct 29 17:02:38 2013 fcoe_vdc1/
819200 Jun 02 13:15:17 2014 hap_reset_show_tech.gz
12465596 Jun 30 13:29:36 2014 ipqosmgr
12335635 May 06 18:12:50 2014 ipqosmgr1
36426752 Jun 05 12:20:14 2014 kick_628_14.bin
36226560 Jun 09 16:17:07 2014 kick_629_s4.bin
12763786 May 13 17:54:24 2014 lc2dce_mds.bin
4096 May 14 13:29:55 2014 lost+found/
6442141 Oct 09 14:25:48 2013 m9700-s3-epld.6.2.7.BF.0.9.gimg
switch(standby)# exit (to return to the active supervisor)
Step 11 If you need more space on the standby supervisor module bootflash on a Cisco MDS 9500 Series switch, delete unnecessary files to make space available.
switch(standby)# del bootflash: m9700-sf2ek9-kickstart-mz.6.2.5.bin.S68
switch(standby)# del m9700-sf3ek9-mz.6.2.5.bin.S68
Step 12 Access the Software Download Center using this URL:
Step 19 Perform the upgrade by issuing 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 an MDS 9700 Series switch.
switch# install all kickstart bootflash:m9700-sf3ek9-kickstart-mz.6.2.9.bin system bootflash:m9700-sf3ek9-mz.6.2.9.bin
Installer will perform compatibility check first. Please wait.
Verifying image bootflash:/m9700-sf3ek9-kickstart-mz.6.2.9.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9700-sf3ek9-mz.6.2.9.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "slc4xb" version from image bootflash:/m9700-sf3ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9700-sf3ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9700-sf3ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9700-sf3ek9-kickstart-mz.6.2.9.bin.
You have now upgraded the Cisco MDS NX-OS software in your existing switch.
Upgrading to Cisco NX-OS Release 6.2(x) on an MDS 9500 Series Switch
Note 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
To upgrade your switch to use the latest Cisco MDS NX-OS software on your Cisco MDS 9500 Series switch, follow these steps:
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 new Cisco MDS 9500 Family 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 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. Refer to the “Using the Cisco NX-OS Setup Utility” chapter in the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.
Step 5 Verify that the requested license files installed in the switch are displayed in response to the show license usage command.
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=FOX064317SQ
Tip Use the entire ID that appears after the colon (:) sign. In this example, the host ID is VDH=FOX064317SQ
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 e-mail. The license key file is digitally signed to only authorize use 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.
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.
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 If you need more space on the standby supervisor module bootflash on a Cisco MDS 9500 Series switch, delete unnecessary files to make space available.
switch(standby)# del bootflash: m9500-sf2ek9-kickstart-mz.6.2.5.bin
switch(standby)# del bootflash:m9500-sf2ek9-mz.6.2.5.bin
Step 12 Access the Software Download Center using this URL:
Step 19 Perform the upgrade by issuing 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 an MDS 9500 Series switch.
switch# install all kickstart m9500-sf2ek9-kickstart-mz.6.2.9.bin system m9500-sf2ek9-mz.6.2.9.bin ssi m9000-ek9-ssi-mz.6.2.9.bin
Copying image from bootflash:/m9000-ek9-ssi-mz.6.2.9.bin to modflash://3-1/m9000-ek9-ssi-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Copying image from bootflash:/m9000-ek9-ssi-mz.6.2.9.bin to modflash://4-1/m9000-ek9-ssi-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Verifying image modflash://3-1/m9000-ek9-ssi-mz.6.2.9.bin for boot variable "ssi".
[####################] 100% -- SUCCESS
Verifying image modflash://4-1/m9000-ek9-ssi-mz.6.2.9.bin for boot variable "ssi".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.6.2.9.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9500-sf2ek9-mz.6.2.9.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "slcdce-mds" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "ips16" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "18_4" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9500-sf2ek9-kickstart-mz.6.2.5.bin.
[####################] 100% -- SUCCESS
Extracting "slc4" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "slc4" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "slc4" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "slc4" version from image bootflash:/m9500-sf2ek9-mz.6.2.9.bin.
107587249 Mar 30 15:42:52 2014 m9250-s5ek9-mz.6.2.5.bin
29714 Mar 30 16:20:21 2014 mts.log
2855303 Mar 30 14:14:36 2014 runn-fc
2855147 Mar 26 15:05:30 2014 runn-mar26
2777996 Mar 27 07:07:46 2014 runn-mar27
2855147 Mar 27 04:51:08 2014 runn-mar27-preRel
2777996 Mar 27 06:22:29 2014 runn-mar27-preRel-wozone
Usage for bootflash://sup-local
236338292 bytes used
142984076 bytes free
379322368 bytes total
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 at the following URL: http://www.cisco.com/cisco/software/navigator.html
107587249 Mar 30 15:42:52 2014 m9250-s5ek9-mz.6.2.7.bin
29714 Mar 30 16:20:21 2014 mts.log
Usage for bootflash://sup-local
120695976 bytes used
63863640 bytes free
184559616 bytes total
Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.
switch# del bootflash:m9250-s5ek9-kickstart-mz.6.2.5.bin.S60
switch# del bootflash:m9250-s5ek9-kickstart-mz.6.2.5.bin.S16
Step 5 Save the configuration using the copy running-config startup-config command.
switch# copy running-config startup-config
You can also create a backup of your existing configuration to a file by issuing the copy running-config bootflash:backup_config.txt command. You might want to add a date reference to the.txt file name to identify the file at a later date.
Step 6 Perform the upgrade by issuing the install all command.
switch# install all kickstart bootflash:m9250-s5ek9-kickstart-mz.6.2.9.bin system bootflash:m9250-s5ek9-mz.6.2.9.bin
Installer will perform compatibility check first. Please wait.
Verifying image bootflash:/m9250-s5ek9-kickstart-mz.6.2.9.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9250-s5ek9-mz.6.2.9.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9250-s5ek9-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9250-s5ek9-kickstart-mz.6.2.9.bin.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9250-s5ek9-mz.6.2.9.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 at the following URL:
Step 4If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.
switch# del bootflash:m9200-sf2ek9-kickstart-mz.5.2.1a.bin
switch# del bootflash:m9200-sf2ek9-mz.5.2.1a.bin
Step 5 Save the configuration using the copy running-config startup-config command.
switch# copy running-config startup-config
You can also create a backup of your existing configuration to a file by issuing the copy running-config bootflash:backup_config.txt command. You might want to add a date reference to the.txt file name to identify the file at a later date.
Step 6 Perform the upgrade by issuing the install all command.
switch# install all system bootflash:m9200-s2ek9-mz.6.2.x.bin.S74 kickstart bootflash:m9200-s2ek9-kickstart-mz.6.2.x.bin.S74
Verifying image bootflash:/m9200-s2ek9-kickstart-mz.6.2.x.bin.S74 for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9200-s2ek9-mz.6.2.x.bin.S74 for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9200-s2ek9-mz.6.2.x.bin.S74.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9200-s2ek9-kickstart-mz.6.2.x.bin.S74.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9200-s2ek9-mz.6.2.x.bin.S74.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9200-s2ek9-mz.6.2.x.bin.S74.
1 00-17-94-ee-1b-54 to 00-17-94-ee-1b-5c JAE11430NJM
2 00-14-a9-74-e0-e8 to 00-14-a9-74-e0-ec JAB093902HZ
* this terminal session
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.
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.
system variable = bootflash:/ m9500-sf2ek9-mz.6.2.1.bin
No module boot variable set
sw-6x-9509(config)#
Step 21 Reload the switch by issuing the reload command.
sw-6x-9509(config)# reload
This command will reboot the system. (y/n)? [n]
You have now upgraded the Cisco MDS NX-OS software in your existing switch.
Downgrading from Cisco NX-OS Release 6.2(x)
Observe these guidelines when downgrading software on Cisco MDS 9148s, 9250i, 9396s, and 9700 Series Director Switches:
Inserting smartoptics on Cisco MDS 9148s, 9250i, 9396s, and 9700 Series Director Switches running an unsupported Cisco MDS NX-OS Release results in the port moving to error-disabled state.
Downgrading from Cisco MDS NX-OS Release 6.2(19) to any other unsupported release (higher or lower) on Cisco MDS 9148s, 9250i, 9396s, and 9700 Series Director Switches with smartoptics links that are error disabled will keep the links in the error-disabled state, unless the links are physically removed and inserted to bring the links up.
Downgrading from Cisco MDS NX-OS Release 6.2(19) to any other unsupported release (higher or lower) on Cisco MDS 9148s, 9250i, 9396s, and 9700 Series Director Switches with smartoptics links up and trunking will keep the links in trunking state.
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 before performing ISSD. Otherwise, ISSD will be disruptive. This issue is not seen when you transfer files from the switch using the copy command or when using the DCNM client.
The following section describes how to downgrade from NX-OS Release 6.2(9) to NX-OS Release 6.2(7), 6.2(5a), 6.2(5), 6.2(3)6.2(1), or 5.2(x).
Note Parallel In-Service Software Downgrade (ISSD) is not recommended on MDS 9148S, MDS 9250i and MDS 9396S fabric switches when these category of fabric switches are peers to each other.
Downgrading from Cisco MDS NX-OS Release 6.2(7) to Cisco MDS NX-OS Release 6.2(5a), 6.2(5), 6.2(3), or 6.2(1)
You must follow these general guidelines before performing a software downgrade from MDS NX-OS Release 6.2(7) to MDS NX-OS Release 6.2(7), 6.2(5a), 6.2(5), 6.2(3), or 6.2(1).
MDS 9700 Series Director with the 48-Port 10-Gigabit Fibre Channel over Ethernet (FCoE) Module and VLAN Configurations
Note You must not perform the Step 2 before Step 1. If you perform Step 2 before Step 1, unexpected events might occur in the switch.
To downgrade from NX-OS Release 6.2(9) from NX-OS Release to Cisco MDS NX-OS Release, 6.2(5a), 6.2(5), 6.2(3), or 6.2(1), follow these steps:
Step 1 You must remove all 48-Port 10-Gigabit FCoE modules from the Cisco MDS 9710 chassis.
Step 2 Use the purge module running-config command to remove any FCoE-related configuration from each 48-Port 10-Gigabit FCoE module that is removed.
Step 3 You must remove all VLANs that you have created and verify that no VLAN or VSAN mapping exist on the switch by using the show vlan and show vlan fcoe command.
Step 4 You must remove all Ethernet Port Channels and verify that no Ethernet Port Channel exists on the switch by using the show interface brief and show ethernet-port-channel database command.
Step 5 You must remove all virtual Fibre Channels (vFCs) and verify that no vFC exists on the switch by using the show interface brief command.
Downgrading from NX-OS Release 6.2(9) to NX-OS Release 6.2(7), 6.2(5a), 6.2(5), 6.2(3), or 6.2(1) on an MDS 9700 Series Director
Use the install all command to downgrade the switch and handle configuration conversions. When downgrading any switch in the Cisco MDS 9000 Family, avoid using the reload command.
To downgrade from NX-OS Release 6.2(x) from NX-OS Release 6.2(9), follow these steps:
Step 1 Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.
switch# dir bootflash:
16384 Mar 13 22:06:41 2014.fc-pcm-log-5354.swp
195379283 Mar 29 10:24:59 2014 46_pvt_image.bin
191117954 Mar 30 11:25:06 2014 47_ps_negative.bin
195257014 Mar 29 07:30:28 2014 S46_deepak_fib_crash.bin
4096 Dec 13 07:19:44 2013 _vdc1/
3383061 Mar 21 04:29:41 2014 d
3383061 Mar 22 12:20:51 2014 d1
4096 Feb 11 12:53:22 2014 epld_dir/
3963713 Mar 22 02:14:25 2014 ethpm.core.gz
4997021 Mar 21 23:44:53 2014 ethpm.ts
4096 Dec 26 10:15:18 2013 fcoe_vdc1/
11870971 Mar 21 23:46:21 2014 lacpa.ts
284045 Mar 14 15:09:58 2014 libfcscli.so
232 Sep 10 13:18:19 2013 license.lic
1718723 Mar 25 19:08:02 2014 logfile.txt
4096 Mar 30 12:50:24 2014 lost+found/
3382868 Mar 28 20:56:38 2014 m9700-sf3ek9-dplug-mzg.6.2.9.bin
36701184 Mar 22 07:14:26 2014 m9700-sf3ek9-kickstart-mz.6.2.1.bin.S60
36726272 Mar 31 08:16:08 2014 m9700-sf3ek9-kickstart-mz.6.2.3.bin.S16
36729856 Mar 22 05:53:53 2014 m9700-sf3ek9-kickstart-mz.6.2.5.bin.S68
36819968 Mar 30 10:24:55 2014 m9700-sf3ek9-kickstart-mz.6.2.9.bin
36819968 Mar 30 07:26:27 2014 m9700-sf3ek9-kickstart-mz.6.2.9.bin.S47
180230838 Mar 22 07:19:31 2014 m9700-sf3ek9-mz.6.2.1.bin.S60
184361989 Mar 31 08:17:24 2014 m9700-sf3ek9-mz.6.2.3.bin.S16
185116340 Mar 22 05:55:29 2014 m9700-sf3ek9-mz.6.2.5.bin.S68
191473732 Mar 30 10:27:44 2014 m9700-sf3ek9-mz.6.2.9.bin
191461839 Mar 30 07:28:01 2014 m9700-sf3ek9-mz.6.2.9.bin.S47
636324 Mar 21 20:14:53 2014 msgs.log
191430449 Mar 30 09:37:09 2014 ps_negative.bin
2887394 Mar 27 20:00:02 2014 runn-fc
2887386 Mar 29 10:33:51 2014 runn-fc1
2888147 Mar 30 06:55:55 2014 runn-fc2
3145515 Mar 24 08:24:36 2014 runn-mar24
3161689 Mar 26 18:34:36 2014 runn-mar26
880111 Mar 27 07:07:25 2014 runn-mar27
3161725 Mar 26 19:47:41 2014 runn-mar27-preRel
Usage for bootflash://sup-local
2178080768 bytes used
1562763264 bytes free
3740844032 bytes total
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 at the following URL:
Step 3 Ensure that the required space is available on the active supervisor.
switch# dir bootflash:
3382868 Mar 28 20:56:38 2014 m9700-sf3ek9-dplug-mzg.6.2.7.bin
36701184 Mar 22 07:14:26 2014 m9700-sf3ek9-kickstart-mz.6.2.1.bin.S60
36726272 Mar 31 08:16:08 2014 m9700-sf3ek9-kickstart-mz.6.2.3.bin.S16
36729856 Mar 22 05:53:53 2014 m9700-sf3ek9-kickstart-mz.6.2.5.bin.S68
36819968 Mar 30 10:24:55 2014 m9700-sf3ek9-kickstart-mz.6.2.5.bin
36819968 Mar 30 07:26:27 2014 m9700-sf3ek9-kickstart-mz.6.2.7.bin.S47
180230838 Mar 22 07:19:31 2014 m9700-sf3ek9-mz.6.2.1.bin.S60
184361989 Mar 31 08:17:24 2014 m9700-sf3ek9-mz.6.2.3.bin.S16
185116340 Mar 22 05:55:29 2014 m9700-sf3ek9-mz.6.2.5.bin
Usage for bootflash://sup-local
2178080768 bytes used
1562763264 bytes free
3740844032 bytes total
Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.
switch# del m9700-sf3ek9-mz.6.2.1.bin.S60
switch# del m9700-sf3ek9-mz.6.2.3.bin.S16
Step 5 Verify that there is enough space available for the standby supervisor.
switch(standby)# dir bootflash
3382868 Mar 28 20:56:38 2014 m9700-sf3ek9-dplug-mzg.6.2.7.bin
36701184 Mar 22 07:14:26 2014 m9700-sf3ek9-kickstart-mz.6.2.1.bin.S60
36726272 Mar 31 08:16:08 2014 m9700-sf3ek9-kickstart-mz.6.2.3.bin.S16
36729856 Mar 22 05:53:53 2014 m9700-sf3ek9-kickstart-mz.6.2.5.bin.S68
36819968 Mar 30 10:24:55 2014 m9700-sf3ek9-kickstart-mz.6.2.7.bin
36819968 Mar 30 07:26:27 2014 m9700-sf3ek9-kickstart-mz.6.2.7.bin.S47
Usage for bootflash://sup-local
116188794 bytes used
68370822 bytes free
184559616 bytes total
Step 6 If you need more space on the standby supervisor module bootflash, delete unnecessary files to make space available.
switch(standby)# del m9700-sf3ek9-kickstart-mz.6.2.3.bin.S16
switch(standby)# del m9700-sf3ek9-kickstart-mz.6.2.3.bin.S60
Step 7 Issue the show incompatibility system image-filename c ommand to determine if you need to disable any features not supported by the earlier release.
switch# show incompatibility system bootflash:m9700-sf3ek9-dplug-mzg.6.2.7.bin
No incompatible configuration
switch#
Step 8 Save the configuration using the copy running-config startup-config command.
switch# copy running-config startup-config
Step 9 Issue the install all command to downgrade the software.
switch# install all kickstart bootflash:m9700-sf3ek9-kickstart-mz.6.2.1.bin.S60 system bootflash:m9700-sf3ek9-mz.6.2.1.bin.S60
Installer will perform compatibility check first. Please wait.
Verifying image bootflash:/m9700-sf3ek9-kickstart-mz.6.2.1.bin.S60 for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9700-sf3ek9-mz.6.2.1.bin.S60 for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "slc4xb" version from image bootflash:/m9700-sf3ek9-mz.6.2.1.bin.S60.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9700-sf3ek9-mz.6.2.1.bin.S60.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9700-sf3ek9-mz.6.2.1.bin.S60.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9700-sf3ek9-kickstart-mz.6.2.1.bin.S60.
Downgrading from NX-OS Release 6.2(x) to NX-OS Release 5.2(x)
Before performing ISSD from Cisco MDS NX-OS Release 6.2(x) to Cisco MDS NX-OS Release 5.2(x) on Cisco MDS 9500 Series Directors, ensure that the purge fcdomain fcid vsan vsan-id command is executed on the IOA VSAN.
The following sections describe how to perform downgrades on an MDS 9513 switch:.
To determine whether high bandwidth capability is enabled, issue the show hardware fabric-mode command. The following example shows that the higher bandwidth capability has not been 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 has been activated:
switch# show hardware fabric-mode
fabric mode supports FCoE, Gen2 and above linecards
switch#
The following sections describe how to perform downgrades on an MDS 9509 and MDS 9506 switch:
Downgrading from NX-OS Release 6.2(x) to NX-OS Release 5.2(x) on an MDS 9513 Multilayer Director
Use the install all command to downgrade the switch and handle configuration conversions. When downgrading any switch in the Cisco MDS 9000 Family, avoid using the reload command.
To downgrade from NX-OS Release 6.2(x) from NX-OS Release 5.2(x), follow these steps:
Step 1 Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.
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 at the following URL:
Step 6If you need more space on the standby supervisor module bootflash, delete unnecessary files to make space available.
switch(standby)# del bootflash:m9500-sf2ek9-kickstart-mz.5.2.x.bin
switch(standby)# del bootflash:m9500-sf2ek9-mz.5.2.x.bin
Step 7 Issue the show incompatibility system image-filename c ommand to determine if you need to disable any features not supported by the earlier release.
switch# show incompatibility system bootflash:m9500-sf2ek9-mz.5.2.1.bin
The following configurations on active are incompatible with the system image
1) Service : port-channel, Capability : CAP_FEATURE_AUTO_CREATED_41_PORT_CHANNEL
Description : auto create enabled ports or auto created port-channels are present
Capability requirement : STRICT
Disable command :
1.Disable autocreate on interfaces (no channel-group auto).
2.Convert autocreated port channels to be persistent (port-channel 1 persistent)
...
Step 8 Disable any features that are incompatible with the downgrade system image.
switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fcip 31
switch(config-if)# no channel-group auto
switch(config-if)# end
switch# port-channel 127 persistent
switch#
Step 9 Save the configuration using the copy running-config startup-config command.
switch# copy running-config startup-config
Step 10 Issue the install all command to downgrade the software.
switch# install all kickstart bootflash:m9500-sf2ek9-kickstart-mz.5.2.1.bin.S74 system bootflash:m9500-sf2ek9-mz.5.2.1.bin.S74
Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.5.2.1.bin.S74 for boot variable
"kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9500-sf2ek9-mz.5.2.1.bin.S74 for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.5.2.1.bin.S74.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.5.2.1.bin.S74.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.5.2.1.bin.S74.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.5.2.1.bin.S74.
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.5.2.1.bin.S74.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.5.2.1.bin.S74.
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 at the following URL:
Step 6If you need more space on the standby supervisor module bootflash, delete unnecessary files to make space available.
switch(standby)# del bootflash:m9500-sf2ek9-kickstart-mz.5.2.x.bin
switch(standby)# del bootflash:m9500-sf2ek9-mz.5.2.x.bin
Step 7 Issue the show incompatibility system image-filename c ommand to determine if you need to disable any features not supported by the earlier release.
switch# show incompatibility system bootflash:m9500-sf2ek9-mz.5.2.x.bin
The following configurations on active are incompatible with the system image
1) Service : port-channel, Capability : CAP_FEATURE_AUTO_CREATED_41_PORT_CHANNEL
Description : auto create enabled ports or auto created port-channels are present
Capability requirement : STRICT
Disable command :
1.Disable autocreate on interfaces (no channel-group auto).
2.Convert autocreated port channels to be persistent (port-channel 1 persistent)
...
Step 8 Disable any features that are incompatible with the downgrade system image.
switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fcip 31
switch(config-if)# no channel-group auto
switch(config-if)# end
switch# port-channel 127 persistent
switch#
Step 9 Save the configuration using the copy running-config startup-config command.
switch# copy running-config startup-config
Step 10 Verify the status of the modules on the switch using the show module command.
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 at the following URL:
Step 4 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.
switch# del bootflash:m9200-sf2ek9-kickstart-mz.5.0.1a.bin
switch# del bootflash:m9200-sf2ek9-mz.5.0.1a.bin
Step 5 Issue the show incompatibility system image-filename c ommand to determine if you need to disable any features not supported by the earlier release.
switch# show incompatibility system bootflash:m9200-sf2ek9-mz.5.2.x.bin
The following configurations on active are incompatible with the system image
1) Service : port-channel, Capability : CAP_FEATURE_AUTO_CREATED_41_PORT_CHANNEL
Description : auto create enabled ports or auto created port-channels are present
Capability requirement : STRICT
Disable command :
1.Disable autocreate on interfaces (no channel-group auto).
2.Convert autocreated port channels to be persistent (port-channel 1 persistent)
...
Step 6 Disable any features that are incompatible with the downgrade system image.
switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fcip 31
switch(config-if)# no channel-group auto
switch(config-if)# end
switch# port-channel 127 persistent
switch#
Step 7 Save the configuration using the copy running-config startup-config command.
switch# copy running-config startup-config
Step 8 Issue the install all command to downgrade the software.
switch# install all kickstart bootflash:m9200-s2ek9-kickstart-mz.5.2.1.bin.S74 system bootflash:m9200-s2ek9-mz.5.2.1.bin.S74
Verifying image bootflash:/m9200-s2ek9-kickstart-mz.5.2.1.bin.S74 for boot variable
"kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9200-s2ek9-mz.5.2.1.bin.S74 for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9200-s2ek9-mz.5.2.1.bin.S74.
107587249 Mar 30 15:42:52 2014 m9250-s5ek9-mz.6.2.7.bin
29714 Mar 30 16:20:21 2014 mts.log
2855303 Mar 30 14:14:36 2014 runn-fc
2855147 Mar 26 15:05:30 2014 runn-mar26
2777996 Mar 27 07:07:46 2014 runn-mar27
2855147 Mar 27 04:51:08 2014 runn-mar27-preRel
2777996 Mar 27 06:22:29 2014 runn-mar27-preRel-wozone
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 at the following URL:
Step 4If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.
switch# del bootflash:m9250-sf2ek9-kickstart-mz.6.2.5.bin
switch# del bootflash:m9250-sf2ek9-kickstart-mz.6.2.5.bin
Step 5 Issue the show incompatibility system image-filename c ommand to determine if you need to disable any features not supported by the earlier release.
switch# show incompatibility system bootflash:m9200-sf2ek9-mz.5.2.x.bin
no incompatible configuration
Step 6 Save the configuration using the copy running-config startup-config command.
switch# copy running-config startup-config
Step 7 Issue the install all command to downgrade the software.
switch# install all kickstart bootflash:m9250-s5ek9-kickstart-mz.6.2.5.bin.S68 system bootflash:m9250-s5ek9-mz.6.2.5.bin.S68
Installer will perform compatibility check first. Please wait.
Verifying image bootflash:/m9250-s5ek9-kickstart-mz.6.2.5.bin.S68 for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9250-s5ek9-mz.6.2.5.bin.S68 for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9250-s5ek9-mz.6.2.5.bin.S68.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9250-s5ek9-kickstart-mz.6.2.5.bin.S68.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9250-s5ek9-mz.6.2.5.bin.S68.
Preparing for a Nondisruptive Upgrade on Fabric and Modular Switches
You can upgrade software on the following switches without any disruptions by using the install all command for the system software images:
Cisco MDS 9148 Multilayer Fabric Switch
Cisco MDS 9148S Multilayer Fabric Switch
Cisco MDS 9222i Multiservice Modular Switch
Cisco MDS 9250i Multiservice Modular Switch
When the installation is completed, the supervisor kickstart image, supervisor system image, line card image, and the system BIOS are all updated.
Nondisruptive upgrades on these fabric switches disrupts the control plane for not more than 80 seconds. The software upgrade might be disruptive if the upgrade progresses beyond when it can be stopped gracefully or if a failure occurs.
Note During the upgrade the control plane is down, but the data plane remains up. New devices are not able to log in to the fabric through the control plane, but existing devices do not experience any disruption of traffic through the data plane.
Before attempting to upgrade any software images on the fabric switches, follow these guidelines:
During the upgrade, the fabric must be stable. Do not perform these configuration activities during the upgrade:
– Zoning changes
– Telnet sessions
– Schedule changes
– Switch cabling
– Addition or removal of physical devices
Configure the FSPF timers to the default value of 20 seconds.
If any CFS 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 the upgrade, you are prompted to enter the show install all failure-reason command to identify the reason.
If the system has insufficient space to load the new images, then you will be notified through the compatibility table. At this point, you need to either abort the upgrade or proceed with a disruptive upgrade.
Check whether sufficient space is available in the system to load the new images by using the Software Install Wizard. Depending on the available space, you need to either abort the upgrade or proceed with a disruptive upgrade.
Enter the no logging level all command before beginning the upgrade. If you do not enter this command, a failure might occur due to the debug system log messages being printed, which potentially can result in the control plane downtime to exceed 80 seconds.
If VRRP is running on the mgmt0 interface, and the switch being upgraded is the master, then 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, upgrades of the 4-Gigabit Ethernet ports for the hybrid Supervisor 18/4 line card will be disruptive.
To ensure that you can view the entire upgrade process, you should perform the upgrade by using the console port. By performing the upgrade this way, you can log your session to a file (in case you need it later for troubleshooting). Telnet sessions are lost when the switch is rebooted, so if you want to view the process in its entirety, be sure to use the console port.
The following section shows an example of the failed nondisruptive upgrade due to insufficient resources.
Example 1-1 Failed Nondisruptive Upgrade Due to Insufficient Resources
switch# install all kickstart bootflash:boot-fs9148 system bootflash:isan-164
Verifying image bootflash:/boot-fs9148 for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/isan-164 for boot variable "system".
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/isan-164.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/boot-fs9148.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/isan-164.
1 bios v1.0.0(10/04/06):v1.0.0(10/04/06) v1.0.0(10/04/06) no
Do you want to continue with the installation (y/n)? [n]
Before performing an upgrade, you may wish to use the show install all impact command to view the effect of updating the system from the running image to another specified image.
switch# show install all impact kickstart bootflash:boot-fs9148 system bootflash:isan-164
Verifying image bootflash:/boot-fs9148 for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/isan-164 for boot variable "system".
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/isan-164.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/boot-fs9148.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/isan-164.
1 bios v1.0.0(10/04/06): v1.0.0(10/04/06) v1.0.0(10/04/06) no
switch#
Performing a Nondisruptive Upgrade on a Fabric Switch
You can perform a nondisruptive software upgrade on any of the following switches by entering the install all kickstart command using the console port:
Cisco MDS 9148 Multilayer Fabric Switch
Cisco MDS 9148S Multilayer Fabric Switch
Cisco MDS 9222i Multiservice Modular Switch
Cisco MDS 9250i Multiservice Modular Switch
Cisco MDS 9396S Multilayer Fabric Switch
The following is an example of the nondisruptive upgrade on a fabric switch:
switch# install all kickstart bootflash:boot-fs9148 system bootflash:isan-164u
Verifying image bootflash:/boot-fs9148 for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/isan-164u for boot variable "system".
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/isan-164u.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/boot-fs9148.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/isan-164u.
1 bios v1.0.0(10/04/06): v1.0.0(10/04/06) v1.0.0(10/04/06) no
Do you want to continue with the installation (y/n)? [n]
Install is in progress, please wait.
Notifying services about the upgrade.
[####################] 100% -- SUCCESS
Setting boot variables.
[####################] 100% -- SUCCESS
Performing configuration copy.
[####################] 100% -- SUCCESS
Converting startup config.
[####################] 100% -- SUCCESS
Upgrade can no longer be aborted, any failure will result in a disruptive upgrade. <---Note that after this point you cannot abort the upgrade.
Freeing memory in the file system.
[####################] 100% -- SUCCESS
Loading images into memory.
[####################] 100% -- SUCCESS
Saving linecard runtime state.
[####################] 100% -- SUCCESS
Saving supervisor runtime state.
[####################] 100% -- SUCCESS
Saving mts state.
[####################] 100% -- SUCCESS
Rebooting the switch to proceed with the upgrade.
Continuing with installation process, please wait.
The login will be disabled until the installation is completed.
Status for linecard upgrade.
[####################] 100% -- SUCCESS
Performing supervisor state verification.
[####################] 100% -- SUCCESS
Install has been successful.
You can use the Software Install Wizard to perform nondisruptive upgrades on Cisco MDS 9148 Fabric Switches.
Caution We recommend that you enable PortFast on the Ethernet interface of the Catalyst switch to which the management interface of the fabric switch is connected. This step action avoids spanning tree convergence time on the Catalyst switch, and immediately forwards packets from the fabric switch during the nondisruptive upgrade.
Note ASM-SFN and SSI images are not supported for upgrades on the Cisco MDS 9148 Multilayer Fabric Switch.
Displaying the Status of a Nondisruptive Upgrade on a Fabric Switch
You can display the status of a nondisruptive upgrade by using the show install all status command. The output displays the status only after the switch has rebooted with the new image. All 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 can reconnect to the switch through a Telnet session, the upgrade might already be complete, in which case, the output will display 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 services that an upgrade is about to start, and finds out whether or not the upgrade can proceed. If a service cannot allow the upgrade to proceed at this time (for example, FSPF timers are not configured to the default value, or a CFS operation is in progress), then the service aborts the upgrade. If this 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.
switch#
Once the upgrade is already in progress if any failures occur for whatever reason (for example, a save runtime state failure or line card upgrade failure), then 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; entering it will not yield any useful information.
If you need additional information to determine why an upgrade is unsuccessful, you can obtain the details from the show tech-support command output and from the console output from the installation, if available.
Related Documentation
The documentation set for the Cisco MDS 9000 Family includes the following documents. To find a document online, use the Cisco MDS NX-OS Documentation Locator at:
Cisco MDS 9000 Family Data Mobility Manager Configuration Guide
Cisco MDS 9000 Family Storage Media Encryption Configuration Guide
Cisco MDS 9000 Family Secure Erase Configuration Guide
Troubleshooting and Reference
Cisco MDS 9000 Family and Nexus 7000 Series System Messages Reference
Cisco MDS 9000 Family NX-OS Troubleshooting Guide
Cisco MDS 9000 Family 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.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
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. (1110R)
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 command-line interface (CLI) session examples provided in this document are only intended for reference. The actual switch output differs based on your switch model.
Feedback