Upgrade the Firmware on an MDS 9000 Series Multilayer Director Switch

Available Languages

Download Options

PDF (75.7 KB)
View with Adobe Reader on a variety of devices
ePub (76.8 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (73.1 KB)
View on Kindle device or Kindle app on multiple devices

Updated:April 18, 2019

Document ID:118952

Introduction

Background Information

Non-Disruptive Upgrades Overview

Upgrade Firmware

Introduction

This document describes how to upgrade the firmware on a Cisco MDS 9000 Series Multilayer Director Switch (MDS).

Background Information

Tip: For more detailed information about the procedure that is described in this document, refer to the appropriate Cisco MDS 9000 NX-OS and SAN-OS Software Install and Upgrade Guide. Additionally, refer to the NX-OS upgrade Best Practices for MDS switches Cisco Support Community article in order to view best practices information in regards to the Cisco MDS 9000 Series switch.

Non-Disruptive Upgrades Overview

All MDS switches support non-disruptive upgrades and downgrades subject to limitations listed in the MDS release notes.

On a 95xx or 97xx Series MDS with dual supervisors, during the firmware upgrade, the new code is loaded on the standby supervisor. A switchover then occurs in order to make the supervisor that runs the new code active. The code is then loaded on the previous active supervisor, and it becomes the new standby supervisor. The data plane continues to pass fibre channel traffic. The modules then non-disruptively start at the lowest numbered module and proceed to the highest.

On a 91xx, 92xx, or 93xx Series MDS, which has only one supervisor, the supervisor (control plane) is reloaded. The data plane continues to pass fibre channel traffic.

If you intend to upgrade via Telnet, Secure Shell (SSH), or Simple Network Management Protocol (SNMP) (Fabric Manager/Device Manager), ensure that you have an Ethernet connection to both of the supervisors. After the Telnet session is lost during the upgrade, you must reconnect to the switch. You will connect to the previous standby supervisor now.

Note: Cisco recommends that firmware upgrades be completed from the local console.

Upgrade Firmware

Complete these steps in order to upgrade the firmware:

Read the MDS Release Notes for the version to which you intend to upgrade. Optionally, review the Release Notes between the old and new firmware levels so that you can learn about the changes. There is a table in the Release Notes that provides the non-disruptive upgrade path.
Enter one of these commands in order to copy the running configuration and the startup configuration so that you have a backup in the event that you have made a change that you did not save:
```
copy running-config startup-config

copy r s
```
Enter this command in order to copy the running configuration to the bootflash, which ensures that there is a copy that can be used for backup and in order to check that the bootflash is not read-only (This is rare, but an error against the flash can cause this.):
```
copy running-config bootflash:$(SWITCHNAME)-$(TIMESTAMP).cfg
```
Here is an example of the output on the bootflash:
```
MDS9124A-2015-04-07-10.02.27.cfg
```
Copy the configuration that you just saved to your TFTP server. This accomplishes three things: It verifies that you have an operational TFTP server, it verifies that you can reach the server over the IP network, and it places a copy of the configuration in a location that is external to the switch so that you have a backup in the event of a switch failure.
Tip: There are many free TFTP servers available on the Internet, such as Solarwinds.
Enter the copy bootflash: tftp: command in order to copy the configuration to the TFTP server. Here is an example:
```
copy bootflash: tftp:
<prompts for file name> MDS9124A-2015-04-07-10.02.27.cfg
<prompt for tftp server name or ip address> 192.168.1.1
```
Verify that you have a copy of the current firmware on your TFTP server so that you have a backup in the event that you must return to the original version. If you do not, copy it from the switch to the TFTP server at this time.

Here are some examples:
```
copy bootflash: tftp:
<prompts for file name> m9100-s2ek9-kickstart-mz.3.3.5b.bin
<prompt for tftp server name or ip address> 192.168.1.1
```
```
copy bootflash: tftp:
<prompts for file name> m9100-s2ek9-kickstart-mz.3.3.5b.bin
<prompt for tftp server name or ip address> 192.168.1.1
```
Note: For the prompts for file name entries, use your actual current version.

Download the new NX-OS version from the Cisco Download Software page. You will need both a kickstart and a system image. Place them on the TFTP server in the default TFTP directory.

You can use this table in order to choose your switch series, and then you can choose the switch model:

Cisco MDS Series Switch Type		Naming Convention
MDS 9134 and 9124 Series, Cisco Fabric Switch for HP C-Class BladeSystem, Cisco Fabric Switch for IBM BladeCenter		File name begins with m9100-s2ek9
MDS 9132T Series		File name begins with m9100-s6ek9
MDS 9148 Series		File name begins with m9100-s3ek9
MDS 9148s Series		File name begins with m9100-s5ek9
MDS 9148T Series		File name begins with m9148-s6ek9
MDS 9222i Series		File name begins with m9200-s2ek9
MDS 9250i Series		File name begins with m9250-s5ek9
MDS 9396s Series		FIle name begins with m9300-s1ek9
MDS 9396T Series		FIle name begins with m9300-s2ek9
MDS 9513, 9509, and 9506 Series	Supervisor-2 module Supervisor-2A module	File name begins with m9500-sf2ek9
MDS 9710, 9706 and 9718 Series		File name begins with m9700-sf3ek9

Here is a example that uses the MDS 9148 Series firmware kickstart and system software Version 5.2(8f):

m9100-s3ek9-kickstart-mz.5.2.8f.bin

m9100-s3ek9-mz.5.2.8f.bin

Note: In order to get the Message Digest5 (MD5) checksum, hover over the image name on the download page.

Verify that there is enough free space on the bootflash in order for the new images to be added. If not, you must erase at least the system image file. Keep the kickstart image so that in the event of a malfunction, you can get the switch to a point that you can load (TFTP) a new image. Once you have upgraded, you can delete the old version.

Enter this command in order to check the bootflash free space:
```
dir bootflash:
```
Additionally, if you run a dual-supervisor switch, enter this command in order to check that there is enough free space on the standby supervisor as well:
```
dir bootflash://sup-standby/ 
```

Download the new images to the bootflash on the switch:

copy tftp: bootflash:
<prompts for file name> m9100-s3ek9-kickstart-mz.5.2.8f.bin
<prompt for tftp server name or ip address> 192.168.1.1

copy tftp: bootflash:
<prompts for file name> m9100-s3ek9-mz.5.2.8f.bin
<prompt for tftp server name or ip address> 192.168.1.1

Enter this command into the CLI in order to verify the checksum and the MD5 checksum:
```
show file bootflash:filename md5sum
```
Enter this command into the CLI in order to view the impact of this code installation, and to check the images and ensure that they are compatible with the switch:
```
show install all impact kickstart bootflash:m9100-s2ek9-kickstart-mz.5.2.8f.bin
 system bootflash:m9100-s2ek9-mz.5.2.8f.bin 
```
Note: This command is not used for installation, but it can be used in order to verify this information.

As an optional step, you can enter the show incompatibility system bootflash:m9500-sf2ek9-mz.6.2.5a.bin command into the CLI. Here is an example:

switch# show incompatibility system bootflash: m9500-sf2ek9-mz.6.2.5a.bin

Cisco Fabric Services (CFS)

The following configurations on active are incompatible with the system image:
1) Service : cfs , Capability : CAP_FEATURE_CFS_ENABLED_DEVICE_ALIAS
Description : CFS - Distribution is enabled for DEVICE-ALIAS
Capability requirement : STRICT
Disable command : no device-alias distribute

Enter this command into the CLI in order to install the firmware:
```
install all kickstart bootflash:m9100-s2ek9-kickstart-mz.4.2.9.bin system
 bootflash:m9100-s2ek9-mz.4.2.9.bin 
```
Note: Ensure that you monitor the impact table closely.
Repeat steps 7 through 12 for each version of code, and use the next version image name.