Cisco Firmware Upgrade Procedures - 1

EMC ® Connectrix Procedure Generator
Topic
Cisco Firmware Upgrade Procedures
Selections
Current Version Family: Current 4.1 Versions
Current 4.1 version: 4.1.3a
Target Version Family: Target 5.0 Versions
Target 5.0 version: 5.0.4d
Additional Appendixes?: Screenshots
Additional Appendixes?: USB Instructions
Procedure Generated: 11/1/2011 12:17:40 PM
IMPORTANT: To be sure you have the latest procedure generator application and content, always
choose Yes when asked if you want to update the application or repository.
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
Procedure Generators@emc.com
©
Copyright 2010 – 2011 EMC Corporation. All rights reserved.
Publication Date: November, 2011
EMC believes the information in this publication is accurate as of its publication date. The information is subject to
change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories
section on EMC Powerlink.
For the most up-to-date listing of EMC trademarks, see the list of EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.
EMC CONFIDENTIAL version: 1.0.1
1 of 28
Contents
About this Procedure ......................................................................................................... 3
Site Activity and Event Record.......................................................................................... 3
Overview.............................................................................................................................. 3
Firmware Package Information and Contents............................................................................................... 4
Supported Switches and Modules ................................................................................................................ 4
Known Issues, Limitations and Restrictions.................................................................................................. 5
Assumptions.................................................................................................................................................. 5
Preparation Tasks............................................................................................................... 7
Task 1: Read and understand the procedure before you begin.............................................................7
Task 2: Obtain software ......................................................................................................................... 7
Task 3: Verify connectivity...................................................................................................................... 7
Task 4: Verify compatibility..................................................................................................................... 8
Task 5: Ensure you have sufficient flash space .....................................................................................9
Task 6: Copy and verify new firmware files............................................................................................9
Task 7: Ensure GigE and Storage Services application traffic is halted. .............................................10
Upgrade Tasks.................................................................................................................. 11
Task 1: Back up and save the current switch configuration .................................................................12
Task 2: Upgrade firmware ....................................................................................................................12
Task 3: Upgrade verification.................................................................................................................13
Appendix A: NX-OS 5.0(4d) Upgrade Examples .......................................................... 14

Appendix B: Using USBs port on 9500 MDS switches................................................ 21
2 of 28
About this Procedure

This document steps you through the completion of a Connectrix management activity that can be
completed without the involvement of Remote Technical Support. If you have any concerns, questions, or
need assistance with an implementation, regarding your environment or this procedure, please contact
EMC Customer Support.
As part of the effort to continuously improve and enhance the performance and capabilities of the
Connectrix product line, EMC periodically releases new versions of its hardware and software, or qualifies
various systems interoperability with the Connectrix product family. Therefore, some functions described
in this procedure may not be supported by all revisions of the software or hardware you have currently in
use. For the most up-to-date information on specific requirements concerning your environment, refer to
the EMC Connectrix MDS-9000 NX-OS Release Notes for your version, and the E-Lab Interoperability
Navigator, both located on PowerLink, and the Cisco MDS Family Release Notes for your version located
at http://www.cisco.com/en/US/products/ps5989/prod_release_notes_list.html.
CAUTION: If this switch participates in a Virtual Storage services solution, such as Invista,
VPLEX, or RecoverPoint, please refer to that product’s documentation, support matrices, and
Procedure Generator for compatibility information or caveats.
Site Activity and Event Record

For your own change management practices, you may need to document this task activity. You may note
critical information in the log area below:
Table 1 Task Information
Date/Time Task being executed Performed by
Table 2 Switch Information
Switch Serial Number Switch Model Switch Name Switch IP
Overview
This procedure explains how upgrade the NX-OS on an MDS-9000 series switch using the command line
interface. You may also use the Cisco Fabric Manager application. Please refer to the Cisco Fabric
Fundamentals Configuration Guide for more information.
These instructions do not contain information on updating Storage Services Interface (SSI) code. EMC
storage services based applications may have their own specific supported versions and upgrade
instructions. Please refer to the applicable product pages on PowerLink. For SSI upgrade instructions for
non-EMC storage services applications, please refer to the Cisco MDS 9000 Family Storage Services
Module Software Installation and Upgrade Guide.
3 of 28
Topics for this upgrade include:

 Preparation tasks
 Upgrade tasks
Firmware Package Information and Contents

The firmware package file name you will download and use is dependent on the platform or series you
will be upgrading. The packages have a naming convention of CISCNXOSx_x_x_model.zip, where x_x_x
is the NX-OS version and model is the applicable switch model or series. Each firmware package
contains the NX-OS kickstart image and the system image. Unzip this firmware package prior to use.
 CISCNXOS5_0_4d_9500V2.zip package for MDS-9500 directors w/Supervisor 2.
 m9500-sf2ek9-mz.5.0.4d.bin
 m9500-sf2ek9-kickstart-mz.5.0.4d.bin
 CISCNXOS5_0_4d_9222i.zip package for the MDS-9222i.
 m9200-s2ek9-mz.5.0.4d.bin
 m9200-s2ek9-kickstart-mz.5.0.4d.bin
 CISCNXOS5_0_4d_9148.zip package for the MDS-9148.
 m9100-s3ek9-mz.5.0.4d.bin
 CISCNXOS5_0_4d_91x4.zip package for the MDS-9124/9134.
 m9100-s2ek9-mz.5.0.4d.bin
Supported Switches and Modules

 Supported Switches
 MDS-9513
 MDS-9509 (with Supervisor II modules)
 MDS-9506 (with Supervisor II modules)
 MDS-9222i
 MDS-9148
 MDS-9134
 MDS-9124
4 of 28
Table 3 Supported Modules
Module Module Description MDS-9500 MDS-9222i

Series
(EMC Model) (Cisco Model)
DS-X9530-SF2A-K9 DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes N/A

DS-X9530-SF2-K9 DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes N/A
MDS-PBF-24-8G DS-X9224-96K9 24-port 8-Gbps Fibre Channel Yes* No
Switching Module
MDS-PBF-48-8G DS-X9248-96K9 48-port 8-Gbps Fibre Channel Yes* No
Switching Module
MDS-PBF-44-8G DS-X9248-48K9 4/44-port Host Optimized 8-Gbps Yes Yes
Fibre Channel Switching Module
MDS-SSN-16 DS-X9316-SSNK9 16-Port Storage Services Node Yes Yes
(SSN-16)
MDS-PBFI-1804 DS-X9304-18K9 18/4-Port Multiprotocol Services Yes Yes
Module (MSM-18/4)
MDS-PBF-12SW DS-X9112 12-port 4-Gbps Fibre Channel Yes Yes
Switching Module
MDS-PBF- DS-X9124 24-port 4-Gbps Fibre Channel Yes Yes
24SW/MR/LR Switching Module
MDS-PBF-48SW DS-X9148 48-port 4-Gbps Fibre Channel Yes Yes
Switching Module
MDS-PBF- DS-X9704 4-port 10-Gbps Fibre Channel Yes Yes
4SR/MDS-PBF-4LR Switching Module
* Requires Fabric 2 modules (DS-13SLT-FAB2) in the MDS-9513. Fabric 2 modules are not required for the MDS-9506 /9509.
Known Issues, Limitations and Restrictions

 The switch must be running a minimum version of NX-OS 4.1(1b) in order to upgrade.
 NX-OS 5.x versions do not support Generation 1 switches and modules.
Always refer to the current version of the Fabric OS Release Notes and the E-Lab Interoperability
Navigator on PowerLink, the Cisco MDS Family Release Notes for your version, and EMC’s
Knowledgebase (Primus) for up to date information.
Assumptions
This upgrade procedure assumes the following:
 Before beginning the upgrade procedure, the switch must be IP accessible for establishing an SSH or
Telnet (or HyperTerminal session), and for the install all command to establish a TFTP
connection to the TFTP server.
 Working knowledge of the Connectrix C Series product family.
If these assumptions are not true, please contact EMC Customer Support for advice before continuing.
5 of 28
CAUTION: The procedure takes approximately 30 minutes to complete, dependant on the number
and types of modules installed. Please plan accordingly.
6 of 28
Preparation Tasks
Before you start the actual upgrade, prepare by performing the tasks in this section.
IMPORTANT: Refer to the documentation for your TFTP server or the instructions in the included
3CDaemon zip file for configuration instructions.
Task 1: Read and understand the procedure before you begin

1. [ ] To prevent errors, save time, and to minimize customer downtime, please read through the entire
upgrade procedure at least once. If you do not understand the upgrade procedure steps, contact
Customer Support before you begin the upgrade.
Task 2: Obtain software

2. [ ] Create a download directory on the TFTP server host machine that you will be using for your
upgrade.
Example:
Windows hosts: c:\temp\cisco
Unix host: /tmp/cisco
3. [ ] Download the firmware package file from the appropriate location. Refer to the section Firmware
Package Information and Contents for the correct file name. EMC personnel and customers with
Enhanced switch support may download the firmware from PowerLink. EMC Partners may use the
EMC Partner’s site.
4. [ ] Unzip the firmware package file that you downloaded in Step 3. [ ] to the directory you created
in Step 2. [ ].
Task 3: Verify connectivity

5. [ ] Ensure a TFTP Server is installed and running on the computer you will do the upgrade from. A
freeware TFTP, FTP, and syslog software package (3CDaemon) is available at
http://support.3com.com/software/utilities_for_windows_32_bit.htm.
Note: TFTP is not necessary if copying code from slot0 or from USB drives. See Appendix B for
information on USB drives.
6. [ ] Check to make sure you have a physical connection to your switch. Log into the switch through a
terminal session or the console port of the active supervisor, an SSH session, or a Telnet session.
You cannot TFTP if connected to a console port only and no network connection to management
port. Please note in 4.1(3a) and higher, TFTP is enabled and telnet is disabled by default.
7 of 28
CAUTION: EMC Supplied Field Laptops and some Customer Sites see the information
below
The firewall service or other services, such as Antivirus software, may be required to be
stopped prior to the firmware upgrade. For example, to stop the firewall BlackICE:
1. Go into services (under Administrative Tools in Windows).
2. Right click and select the process BlackICE and select stop.
----- If the service will not stop, you must change the startup type to manual and reboot.
----- Right click under services, select properties, and change the startup type to Manual.
3. Complete the firmware upgrade procedure.
4. Restart the BlackICE service (or reset the startup type) when the upgrade is complete.
If you have McAfee 8.x VirusScan installed, you may need to reconfigure it. To reconfigure it,
go to the McAfee VirusScan Console, select Access Protection, and deselect “FTP inbound”
Task 4: Verify compatibility

7. [ ] Check the listing of compatible switches and modules in the section Supported Switches and
Modules. Only upgraded supported configurations. If unsure, do not proceed until all questionable
configurations are reviewed and confirmed as supported.
It is recommended that the commands show sprom backplane 1 and show modules be used.
Login into the switch(es) in question and use these commands to check the switches and modules
before attempting any upgrade. Keeping the outputs from these commands is highly recommended.
Example:
switch# show sprom backplane 1
DISPLAY backplane sprom contents:

Common block:
~
OEM String : Cisco Systems, Inc.
Product Number : DS-C9513
Serial Number : FOX110905RG
Part Number : 73-10095-03
switch# show module

Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ----------
-
1 12 1/2/4 Gbps FC Module DS-X9112 ok
3 4 10 Gbps FC Module DS-X9704 ok
5 48 1/2/4/8 Gbps 4/44-Port FC Module DS-X9248-48K9 ok
6 48 1/2/4/8 Gbps 48-Port FC Module DS-X9248-96K9 ok
7 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 active *
8 of 28
8 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 ha-standby

11 16 16x1GE, Storage Services Node DS-X9316-SSNK9 ok
12 22 4x1GE IPS, 18x1/2/4Gbps FC Modul DS-X9304-18K9 ok
8. [ ] Verify that the status of each module is “OK” and the supervisor modules are “active” and “ha-
standby” (ha-standby for switches with two supervisor modules – 9506/9509/9513). Note the active
and standby supervisor module slot locations.
Task 5: Ensure you have sufficient flash space

To upgrade the NX-OS image on a Cisco MDS 9000 Family switch, it requires enough space on the
internal Compact Flash (also referred to as bootflash) to accommodate both the old software image and
the new software image.
To work around an image upgrade failure caused by a lack of space on the bootflash, follow these steps:
9. [ ] Prior to installing the new image, copy the old (existing) system image file to an external server,
slot0, or USB drives. You may need to reinstall this file later.
10. [ ] Delete the old system image file from the bootflash by using either the Fabric Manager software
install wizard or the command line delete bootflash: command. The system image file does not
contain the word “kickstart” in the filename.
switch# delete bootflash:m9200-ek9-mz.4.2.1b.bin
Note: On MDS 9500 Series switches, you also need to delete the image file from the standby
supervisor after deleting it from the active supervisor.
switch# delete bootflash://sup-standby/m9500-sf2ek9-mz.4.2.1b.bin

11. [ ] Start the image upgrade or installation process using the Fabric Manager software install wizard
or the command line install all command.
12. [ ] If the new installation or upgrade fails while copying the image and you want to keep the old
(existing) image, copy the old image that you saved in 9. [ ] to the bootflash using either Fabric
Manager or the copy command.
CAUTION: If the switch fails to boot, then follow the recovery procedure described in the
“Troubleshooting Installs, Upgrades, and Reboots” section of the appropriate version of the
Cisco MDS 9000 Family Troubleshooting Guide.
Task 6: Copy and verify new firmware files

13. [ ] Copy the software image from a TFTP location (or USB drive) to one of two targets: bootflash:, or
slot0.
Note: The Connectrix MDS 9100 and 9200 series switches do not have an external Compact Flash
(slot0:). If you are using a switch in this series, use the bootflash: directory to copy and verify files.
Not all 9500 series switches have Compact Flash devices installed. Run dir slot0: to see if there
is one installed.
9 of 28
You can also copy the image onto a new Flash disk from a PC and insert it in slot0: in the Connectrix
MDS 9500 Director. After you copy the image and insert it into the slot0: partition, the process is the
same as the Compact Flash device after the copy command is issued.
The format of the command for copying the files to the bootflash is:
switch# copy tftp://<server IP address>/<filename in TFTP>
bootflash:<image filename>
And for copying to the compact flash:
switch# copy tftp://<server IP address>/<filename in TFTP > slot0:<image
filename>
Note: Brackets <> indicate user supplied information. Do NOT include the <> in your commands.
Please refer to Appendix A for specific examples. For information on using the USB drives on 9500
series switches, please refer to Appendix B.
14. [ ] Verify that the files copied over successfully by run the dir command on the target device, for
example bootflash: or slot0:.
15. [ ] Ensure that the software images are not damaged or corrupted in the saved bootflash, usb, or
slot0 location. Use the show version image command to verify that the required image was
copied successfully. Refer to Appendix A for an example.
Task 7: Ensure GigE and Storage Services application traffic is halted.

16. [ ] GigE and Storage Services application traffic will be disrupted during the upgrade process.
Ensure that this traffic has been halted prior to the upgrade.
10 of 28
Upgrade Tasks
IMPORTANT: Before you begin the upgrade procedure, make sure you have completed all of the tasks
described under
11 of 28
Preparation Tasks, in particular verifying the compatibility of your switches and modules.
Task 1: Back up and save the current switch configuration

1. [ ] Copy your existing running configuration the start up configuration (make sure running
configuration is correct).
Example:
switch# copy running-config startup-config
2. [ ] Backup the configuration file. You can do this via the TFTP server, slot0, or the USB drive. Use a
meaningful name as shown in the example below.
Example:
switch# copy startup-config tftp://<server IP address>/<startup-
config_switch name_date>
3. [ ] Ensure that a copy of the outputs of the show tech-support detail command is saved.
Task 2: Upgrade firmware

IMPORTANT: When you issue the install all command, the switch displays a summary of changes
that will be made to your configuration and waits for your authorization to continue executing the
command process. Check to see if the upgrade will be disruptive or not. Only proceed with upgrades if
the disruptive nature is correct.
CAUTION: Avoid aborting the switch progress after issuing the install all command. If the
install all command is aborted, be sure to verify the state of the switch at every level. If you
issue the command and then abort, you may need to use the manual procedure commands to
complete the upgrade. This necessity depends on the state of the switch at the time of the failure.
4. [ ] Perform the upgrade by issuing the install all command on the active supervisor module
from the switch console or your current logged in session. The format of the install all command
is :
switch# install all system bootflash:<system image name>
kickstart bootflash:<kickstart image name>
The install all command will extract the firmware files, perform a compatibility check, inform you
if any module being upgraded will be hitless (non-disruptive) or hitful (disruptive), and ask whether
you want to continue the upgrade, as shown in the example in Appendix A.
5. [ ] Enter y if you wish to continue with the installation. Only select y after confirming that the impact
is acceptable. If you see disruptive for any module and interruption or downtime is not acceptable, DO
NOT answer with y. Answer n and abort the upgrade if there are any concerns with the upgrade.
12 of 28
6. [ ] After confirming the upgrade, the process will proceed. You may lose your connection to the
active supervisor or flash module during the switchover, as shown in Appendix A. This is part of the
normal HA switchover and is not a concern.
Task 3: Upgrade verification

7. [ ] Reconnect to the switch after the upgrade has stated it is successful via a telnet, ssh, or console
connection. Depending on the switch model and the type of type of upgrade, your initial connection
may have been lost. Simply reconnect back to the switch and issue the show module command
just as you had performed in Preparation Tasks, step 7. [ ].
Verify the status of each module is “OK” and the supervisor modules are “active” and “ha-standby”
(ha-standby for switches with two supervisor modules). If all modules display correct, the upgrade has
completed successfully. Review switch logs and confirm the switch is working correctly.
If for any reason the upgrade failed or modules do not show up as “Ok”, collect logs and troubleshoot
the issue as necessary. This may include contacting the EMC Support Center. They will ask you for
complete set of logs (show tech-support details) to further troubleshoot the issue. Looking at the
output from the show install all status command (which is also in the show tech-support output) can
provide information on what may have happened in the install. Looking at the show logging log output
can also give an idea of why a module may be not working.
IMPORTANT: For more information on any of the commands used in this procedure, refer to the
Cisco MDS 9000 Family Command Reference, which contains detailed information on commands,
and command syntax.
13 of 28
Appendix A: NX-OS 5.0(4d) Upgrade Examples
Preparation Tasks
This section contains version unique examples of the commands used in the Preparation Tasks topic.
Example for Task 5, Step 9

These are examples of copy commands used to copy firmware files from a TFTP location to either
bootflash or a compact flash device on the switch.
Bootflash
Example of a MDS 9222i:
switch# copy tftp://10.1.7.2/m9200-s2ek9-mz.5.0.4d.bin bootflash:m9200-
s2ek9-mz.5.0.4d.bin
switch# copy tftp://10.1.7.2/m9200-s2ek9-kickstart-
mz.5.0.4d.bin bootflash:m9200-s2ek9-kickstart-mz.5.0.4d.bin
Example of a MDS 9148:

switch# copy tftp://10.1.7.2/m9100-s3ek9-mz.5.0.4d.bin bootflash: m9100-
s3ek9-mz.5.0.4d.bin
mz.5.0.4d.bin bootflash: m9100-s3ek9-kickstart-mz.5.0.4d.bin
Example of a MDS 9124 / 9134:

switch# copy tftp://10.1.7.2/m9100-s2ek9-mz.5.0.4d.bin bootflash:m9100-
s2ek9-mz.5.0.4d.bin
mz.5.0.4d.bin bootflash:m9100-s2ek9-kickstart-mz.5.0.4d.bin
Example of a MDS 9513 / MDS 9509 / MDS 9506:

switch# copy tftp://10.1.7.2/m9500-sf2ek9-mz.5.0.4d.bin bootflash:m9500-
sf2ek9-mz.5.0.4d.bin
switch# copy tftp://10.1.7.2/m9500-sf2ek9-kickstart-
mz.5.0.4d.bin bootflash:m9500-sf2ek9-kickstart-mz.5.0.4d.bin
Compact Flash
Example:
switch# copy tftp://10.1.7.2/m9500-sf2ek9-mz.5.0.4d.bin slot0:m9500-
sf2ek9-mz.5.0.4d.bin
switch# copy tftp://10.1.7.2/m9500-sf2ek9-kickstart-
mz.5.0.4d.bin slot0:m9500-sf2ek9-kickstart-mz.5.0.4d.bin
14 of 28

The following is an example of the show version image command used to verify the image integrity.
Example:
switch# show version image bootflash:m9500-sf2ek9-mz.5.0.4d.bin
MD5 Verification Passed

image name: m9500-sf2ek9-mz.5.0.4d.bin
bios: v1.0.10(01/08/09)
system: version 5.0(4d)
compiled: 4/14/2011 18:00:00 [05/03/2011 15:21:27]
Upgrade Tasks
This section contains version unique examples of the commands used in the Upgrade Tasks topic.

Example install all command lines and output.
Upgrading an MDS 9222i:
switch# install all system bootflash:m9200-s2ek9-mz.5.0.4d.bin
kickstart bootflash:m9200-s2ek9-kickstart-mz.5.0.4d.bin
Upgrading an MDS 9148:

Upgrading an MDS 9124 / 9134:

Upgrading an MDS 9500 w/Version II Supervisor:

switch# install all system bootflash:m9500-sf2ek9-mz.5.0.4d.bin
kickstart bootflash:m9500-sf2ek9-kickstart-mz.5.0.4d.bin
Example of MDS 9513 upgrade output:

Verifying image bootflash:/m9500-sf2ek9-kickstart-mz.5.0.4d.bin for boot
variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin for boot variable

"system".
[####################] 100% -- SUCCESS
Verifying image type.
15 of 28
[####################] 100% -- SUCCESS
Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.

[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.

[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9500-sf2ek9-kickstart-

mz.5.0.4d.bin.
[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS
Extracting "ips16" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.

[####################] 100% -- SUCCESS
Extracting "ssi" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS
Extracting "18_4" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.

[####################] 100% -- SUCCESS
Extracting "ssi" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.

[####################] 100% -- SUCCESS
Performing Compact Flash and TCAM sanity test.
16 of 28
[####################] 100% -- SUCCESS
Performing module support checks.

[####################] 100% -- SUCCESS
Notifying services about system upgrade.

[####################] 100% -- SUCCESS
Compatibility check is done:

Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive rolling
7 yes non-disruptive reset
8 yes non-disruptive reset
11 yes disruptive rolling Hitless upgrade is not
supported
Other miscellaneous information for installation:

Module info
------ ----------------------------------
11 Hitless upgrade is not supported
12 FC ports 1-18 are hitless, GigE 1-4 are hitful, and Intelligent
Applications running are hitful
Images will be upgraded according to following table:

Module Image Running-Version(pri:alt) New-Version Upg-Required
------ ---------- ----------------------------- ----------- ------------
1 slc2 5.0(4c) 5.0(4d) yes
1 bios v1.0.19(02/01/10):
v1.0.19(02/01/10) v1.0.19(02/01/10) no
2 slc2 5.0(4c) 5.0(4d) yes
2 bios v1.0.19(02/01/10):
v1.0.19(02/01/10) v1.0.19(02/01/10) no
3 slc2 5.0(4c) 5.0(4d) yes
3 bios v1.0.19(02/01/10):
v1.0.19(02/01/10) v1.0.19(02/01/10) no
4 slc2 5.0(4c) 5.0(4d) yes
4 bios v1.0.19(02/01/10):
v1.0.19(02/01/10) v1.0.19(02/01/10) no
5 slc2 5.0(4c) 5.0(4d) yes
5 bios v1.0.19(02/01/10):
17 of 28
v1.0.19(02/01/10) v1.0.19(02/01/10) no
6 slc2 5.0(4c) 5.0(4d) yes
6 bios v1.0.19(02/01/10):
v1.0.19(02/01/10) v1.0.19(02/01/10) no
7 system 5.0(4c) 5.0(4d) yes
7 kickstart 5.0(4c) 5.0(4d) yes
7 bios v1.0.10(01/08/09):
v1.0.10(01/08/09) v1.0.10(01/08/09) no
8 system 5.0(4c) 5.0(4d) yes
8 kickstart 5.0(4c) 5.0(4d) yes
8 bios v1.0.10(01/08/09):
v1.0.10(01/08/09) v1.0.10(01/08/09) no
9 slc2 5.0(4c) 5.0(4d) yes
9 bios v1.0.19(02/01/10):
v1.0.19(02/01/10) v1.0.19(02/01/10) no
11 slc2 5.0(4c) 5.0(4d) yes
11 ips16 5.0(4c) 5.0(4d) yes
11 ssi 5.0(4c) 5.0(4d) yes
11 bios v1.0.19(02/01/10):
v1.0.19(02/01/10) v1.0.19(02/01/10) no
12 slc2 5.0(4c) 5.0(4d) yes
12 18_4 5.0(4c) 5.0(4d) yes
12 ssi 5.0(4c) 5.0(4d) yes
12 bios v1.0.19(02/01/10):
v1.0.19(02/01/10) v1.0.19(02/01/10) no
Do you want to continue with the installation (y/n)? [n] y

Continuation of the upgrade example from Step 4, after replying y to continue:
Install is in progress, please wait.
Performing runtime checks.

[####################] 100% -- SUCCESS
Syncing image bootflash:/m9500-sf2ek9-kickstart-mz.5.0.4d.bin to standby.

[####################] 100% -- SUCCESS
Syncing image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin to standby.

[####################] 100% -- SUCCESS
Setting boot variables.

[####################] 100% -- SUCCESS
Performing configuration copy.

[####################] 100% -- SUCCESS
Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.

Warning: please do not remove or power off the module at this time.
18 of 28
[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS

[####################] 100% -- SUCCESS
2011 Jun 10 05:41:19 SVT9513 %PLATFORM-2-MOD_REMOVE: Module 8 removed (Serial
number JAE141501VJ)
Module 8: Waiting for module online.

-- SUCCESS
Notifying services about the switchover.

[####################] 100% -- SUCCESS
19 of 28
"Switching over onto standby"
20 of 28
Appendix B: Using USBs port on 9500 MDS switches
Background on USB Flash Drives on MDS switches

The Supervisor 2 modules on Cisco MDS 9000 Family switches contain two USB flash drive ports called
usb1 and usb2 (see picture 1 below). Currently only the 9513, 9509 and 9506 can contain the Supervisor
II modules that have the USB ports. Flash drives connected to these USB ports can be used for storing
software images, logs, and core dumps.
As of Cisco MDS SAN-OS release 3.2(1a), the USB ports on the Supervisor-2 module are EMC
supported. USB flash drives connected to these ports may be used for the same functions as media in
the external compact flash slot. USB devices up to 2GB are supported (see list of support USB drives
below).
Figure 1 Supervisor II module
Looking at the actual Supervisor II modules more closely you will see that there are two USB ports on the
far end of the module. Supervisor I modules do not have the USB ports. The two ports are labeled USB 1
on the top and USB 2 on the bottom (see diagram below).
21 of 28
Figure 2 How the USB ports are labeled
What is required to use USB Flash Drives?

The switch must be a 9513, or a 9509 or 9506 switch with Generation II Supervisors. The switch must be
running SAN-OS 3.2(1a) or above or NX-OS, and the Power Management EPLD version 0xD or higher.
Use the “show version” command to display the version. See below for how to find the EPLD version.
How to check the EPLD version?

The command “show version module slot epld” where slot is the 9500 supervisor module will display the
current EPLD version. For a 9509 or 9506, the supervisors will be in slots 5 and 6. For a 9513, the
supervisors are in slots 7 and 8. See below for how to upgrade the EPLD if necessary.
Example:
switch# show version module 7 epld
EPLD Device Version
---------------------------------------
Power Manager 0x0d  at version 0xD so upgrade of EPLD
not required
XBUS IO 0x0b
Fabric Controller 0x0b
How can I use the USB Flash Drives?

The USB drives can be used to copy NX-OS (firmware), logs, and core dumps onto and off the switch.
You cannot boot off the USB drive but you can copy the NX-OS from the USB drive to the bootflash on
the switch and then upgrade from there. You can also copy off older versions of NX-OS from bootflash
just in case you need roll back to the older version. The use of the USB drive for installation can make it
easier to bring code into secure sites as a laptop is no longer required to transfer the code to the switch.
Which USB Flash Drives are supported?

While many USB flash drives up to 2 GB will work, Cisco only has tested and supports only certain
models (see below). Your USB flash drive may work if not listed below but will not be supported if a
problem is found using it.
22 of 28
Table 4 Supported USB Flash Drives
Brand Size Model

IBM 32 MB IBM 32MB
Sony 2G Micro Vault TINY 2GB
2G Micro Vault 2GB
1G Micro Vault 1GB
1G Micro Vault TINY 1GB
512 MB Micro Vault 512 MB
LEXAR 2G JumpDrive FireFly 2GB
2G JumpDriver Lightning 2GB
2G JumpDriver 360 2GB
1G JumpDrive FireFly 1GB
1G JumpDriver Lightning 1GB
1G JumpDriver 360 1GB
1G JumpDriver Mercury 1GB
KINGSTON 2G DataTraveler 2GB
2G DataTraveler U3 Smart 2GB
1G DataTraveler 1GB
512 MB DataTraveler 512 MB
SANDISK 2G Cruzer Micro 2GB
1G Cruzer Micro 1GB
TDK 2G TRANS-IT 2GB
PQA 2G PQI Traveling Disk 2GB
1G PQI Traveling Disk 1GB
PNY 2G Optima Pro™ Attaché 2GB
1G Optima Pro™ Attaché 1GB
EMPREX 2G USB Flash Drive PD330 2GB
2G USB Flash Drive PD10 2GB
MEMOREX 1G Tracel Drive 1GB
Note: Other drives may work but aren’t officially tested and supported by Cisco.
Viewing Files on USB Flash Drives

To view files on a USB flash drive that has already been formatted on NX-OS, issue the dir usb1: or dir
usb2: CLI commands. Please note that the USB port numbers may be swapped (see above)
23 of 28
Copying Files To / From USB Flash Drives

To copy files to and from the USB drives, use the copy CLI command.
To copy NX-OS files from the USB drive (connected on USB2) to bootflash for an upgrade, issue the
following command: copy usb2:filename bootflash:filename, where filename is your
specific system image file.
To copy files to a USB drive (connected on USB1) from the bootflash, issue the following command:
copy bootflash:log_files usb1:log_files
Formatting USB Flash Drives

USB drives are accessible once the USB drives are formatted on SAN-OS. If the USB flash drive is not
already formatted on SAN-OS, issue the format usb1 or format usb2 CLI commands. In most cases if
your Windows host can see the drive and copy files to it, the format on the USB Flash drive should be fine
when you connect it to the switch and formatting is not required. Always test the drive before you need it
for any upgrade or other important use.
Error encountered when using USB drive on the switch

When attempting to use USB ports, the following message may be displayed: Please upgrade Power
Management EPLD to version OxD or higher. If you receive this message, you need to upgrade the
Power Management EPLD for the Supervisor II modules to version OxD or higher in order to use the USB
ports.
Methods to upgrade EPLD

There are two methods to upgrade the EPLD, one is disruptive and other is non-disruptive. The
differences in the upgrade processes for disruptive and non-disruptive deal with power cycling the entire
switch. For the disruptive method, the entire switch must be power cycled after the EPLD is upgraded. In
the non-disruptive method, the supervisors are individually removed and replaced after upgrading the
EPLD instead of power cycling the entire switch. In most cases, only the non-disruptive method should be
used. Please note that even though the non-disruptive process should be non-disruptive there is a
chance that it could be disruptive. Please receive customer approval before doing any EPLD upgrades.
Upgrading Power Management EPLD Non-Disruptively

1. [ ] Log into the switch through the console port, an SSH session, or a Telnet session. Confirm the
EPLD is not running version 0xD or above with the show version module x epld command (where x is
the slot number of either supervisor module). If the EPLD is 0xd or above, no upgrade of EPLD is
required to use the USB ports.
Example:
EMC9513# show version module 7 epld
EPLD Device Version

---------------------------------------
Power Manager 0x0d  at version 0xD so upgrade of
EPLD not required
XBUS IO 0x0b
Fabric Controller 0x0b
24 of 28
2. [ ] If EPLD needs to upgraded, issue the show version command to verify the Cisco MDS SAN-OS
release running on the MDS switch is 3.2(1a) or above.
3. [ ] If required; upgrade the Cisco MDS SAN-OS software running on your switch to 3.2(1a) or
above.
4. [ ] Download the appropriate EPLD software image as listed in the matrix below. You can find the
EPLD images at the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/mds-epld
Table 5 EPLD Release Compatibility Matrix
SAN-OS or NX-OS Release EPLD Image

SAN-OS 3.3(1c) m9000-epld-3.2.2c.img
SAN-OS 3.3(2) m9000-epld-3.3.2.img
SAN-OS 3.3(3)
SAN-OS 3.3(4)
SAN-OS 3.3(4a)
SAN-OS 3.3(5)
SAN-OS 3.3(5a) m9000-epld-3.3.5a.img
SAN-OS 3.3(5b)
NX-OS 4.1(1b) m9000-epld-4.1.1a.img
NX-OS 4.1(3a) m9000-epld-4.1.3.img
NX-OS 4.2(1a)
NX-OS 4.2(1b)
NX-OS 4.2(3)
NX-OS 4.2(5)
NX-OS 4.2(7b) m9000-epld-4.2.7a.img
NX-OS 4.2(7d)
NX-OS 4.2(7e)
NX-OS 5.0(1a) m9000-epld-5.0.1a.img
NX-OS 5.0(4) m9000-epld-5.0.4
NX-OS 5.0(4b)
NX-OS 5.0(4c)
NX-OS 5.0(4d)
Note: You may not have access to this area of the Cisco web site. If you don’t have access, please
contact EMC Support and note this document. EMC Support will provide you with the EPLD if
appropriate.
5. [ ] Once you have the EPLD software image file, follow these steps:
25 of 28
a. Copy the EPLD software image file from Cisco.com to your TFTP or FTP server. You can use the
3CDAEMON software which is available on the ESN Product Site or at
http://support.3com.com/software/utilities_for_windows_32_bit.htm
b. Verify that you have enough free space available on the active and standby supervisors (or slot0)
that you plan to use to copy the EPLD image file to. The download site on Cisco.com shows the
size of the EPLD image file in bytes.
The following example shows how to display the available bootflash space on the active
supervisor with the dir bootflash: command. The command defaults to the active supervisor.
Switch# dir bootflash:
49152 Feb 24 14:04:31 2010 lost+found/

21446656 Feb 24 13:56:55 2010 m9500-sf2ek9-kickstart-
mz.5.0.1a.bin
90083821 Feb 24 13:56:33 2010 m9500-sf2ek9-mz.5.0.1a.bin
Usage for bootflash://sup-local

299175936 bytes used
574541824 bytes free
873717760 bytes total
Next use the show module command to find out the standby supervisor.
switch# show module
Mod Ports Module-Type Model Status

--- ----- -------------------------------- ------------------ --------
----
3 4 10 Gbps FC Module DS-X9704 ok
5 48 1/2/4/8 Gbps 4/44-Port FC Module DS-X9248-48K9 ok
7 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 active *
8 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 ha-
standby
11 16 16x1GE, Storage Services Node DS-X9316-SSNK9 ok
12 22 4x1GE IPS, 18x1/2/4Gbps FC Modul DS-X9304-18K9 ok
The show module command output shows that the standby supervisor is in slot 6. Use the attach
command to access the supervisor module and check for available space with the dir bootflash:
command.
switch# attach module 6
switch(standby)#dir bootflash:
~
~
49152 Feb 24 14:04:31 2010 lost+found/
26 of 28

mz.5.0.1a.bin
90083821 Feb 24 13:56:33 2010 m9500-sf2ek9-mz.5.0.1a.bin
Usage for bootflash://sup-local

574541824 bytes free
The following example shows how to display the available space for the slot0: device on the active
supervisor.
switch# dir slot0:
12288 Jan 01 00:01:06 1980 lost+found/
mz.5.0.1a.bin
90083821 Feb 24 13:56:33 2010 m9500-sf2ek9-mz.5.0.1a.bin
Usage for slot:

43493376 bytes free
c. If there is not enough available space on the active or standby supervisor (or slot0), delete
unneeded files to make room.
switch# delete bootflash:m9500-sf2ek9-kickstart-mz.4.2.1b.bin
The show module command output shows that the standby supervisor is in slot 6. Use the attach
command to access the standby supervisor module and delete files if necessary.
switch# attach module 6
switch(standby)# delete bootflash:m9500-sf2ek9-kickstart-mz.4.2.1b.bin
switch(standby)# exit
d. Copy the EPLD image file from the TFTP server to the bootflash: or slot0: device in the active
supervisor module. The following example shows how to copy the image file to bootflash:
switch# copy tftp://10.1.7.2/m9000-epld-x.x.x.img bootflash:m9000-epld-
x.x.x.img
Note: Note The system will automatically synchronize the ELPD image to the standby supervisor
if automatic copying is enabled. You can set automatic copy if not already set with the boot auto-
copy command.
switch# config
switch(config)# boot auto-copy
e. Issue the dir bootflash: or dir slot0: command to verify that the EPLD software image file
corresponding to your Cisco MDS SAN-OS release is present on the active supervisor module.
Please note that the EPLD image will NOT directly match the SAN-OS version.
Switch# dir bootflash:
49152 Dec 15 00:45:29 2007 lost+found/
27 of 28
3209976 Feb 01 01:05:50 2008 m9000-epld-3.2.2c.img
6. [ ] Upgrade the Power Management EPLD on the standby Supervisor module. From the active
Supervisor module, issue the install module <x> epld bootflash:<epld_image_file_x_x_x> CLI
command where <x> is the standby supervisor previously noted. After the EPLD upgrade is
complete, the standby Supervisor module will reboot. The active Supervisor cannot be upgraded, only
the standby Supervisor can be upgraded.
Example Upgrading Module EPLDs on standby supervisor
switch# install module 6 epld bootflash:m9000-epld.x.x.x.img
Len 3206928, CS 0xd0, string MDS series EPLD image, built on Fri Nov 16
18:02:28 2007
EPLD Curr Ver New Ver

-------------------------------------------------------
Power Manager 0x0c 0x0d
XBUS IO 0x0b 0x0b
WARNING: Upgrade process could take upto 15 minutes.
Module 6 will be powered down now!!
Do you want to continue (y/n) ? y
\ <------------------------------------------------------------progress
twirl
Module 6 EPLD upgrade is successful.
7. [ ] When the standby Supervisor module is online, physically remove the standby Supervisor
module and re-install it. The standby Supervisor module will come up with the new Power
Management EPLD version.
8. [ ] After the standby Supervisor module comes online, perform a switchover of the supervisors and
wait until the new standby Supervisor module comes online as the active Supervisor.
Example of system switchover
switch# system switchover
9. [ ] From the active Supervisor module, repeat steps 6 through 8 until both Supervisors have had
their EPLD upgraded successfully.
28 of 28

Cisco Firmware Upgrade Procedures - 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cisco Firmware Upgrade Procedures - 1

Uploaded by

Copyright:

Available Formats

EMC ® Connectrix Procedure Generator

Procedure Generated: 11/1/2011 12:17:40 PM

EMC CONFIDENTIAL version: 1.0.1

Supported Switches and Modules ................................................................................................................ 4

Known Issues, Limitations and Restrictions.................................................................................................. 5

Appendix A: NX-OS 5.0(4d) Upgrade Examples .......................................................... 14

EMC CONFIDENTIAL version: 1.0.1

About this Procedure

Site Activity and Event Record

Table 1 Task Information

Date/Time Task being executed Performed by

Table 2 Switch Information

Switch Serial Number Switch Model Switch Name Switch IP

EMC CONFIDENTIAL version: 1.0.1

Topics for this upgrade include:

Firmware Package Information and Contents

Supported Switches and Modules

EMC CONFIDENTIAL version: 1.0.1

Table 3 Supported Modules

Module Module Description MDS-9500 MDS-9222i

DS-X9530-SF2A-K9 DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes N/A

Known Issues, Limitations and Restrictions

EMC CONFIDENTIAL version: 1.0.1

EMC CONFIDENTIAL version: 1.0.1

Task 1: Read and understand the procedure before you begin

Task 2: Obtain software

Task 3: Verify connectivity

EMC CONFIDENTIAL version: 1.0.1

Task 4: Verify compatibility

DISPLAY backplane sprom contents:

switch# show module

EMC CONFIDENTIAL version: 1.0.1

8 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 ha-standby

Task 5: Ensure you have sufficient flash space

switch# delete bootflash://sup-standby/m9500-sf2ek9-mz.4.2.1b.bin

Task 6: Copy and verify new firmware files

EMC CONFIDENTIAL version: 1.0.1

Task 7: Ensure GigE and Storage Services application traffic is halted.

EMC CONFIDENTIAL version: 1.0.1

EMC CONFIDENTIAL version: 1.0.1

Task 1: Back up and save the current switch configuration

Task 2: Upgrade firmware

EMC CONFIDENTIAL version: 1.0.1

Task 3: Upgrade verification

EMC CONFIDENTIAL version: 1.0.1

Appendix A: NX-OS 5.0(4d) Upgrade Examples

Example for Task 5, Step 9

Example of a MDS 9148:

Example of a MDS 9124 / 9134:

Example of a MDS 9513 / MDS 9509 / MDS 9506:

EMC CONFIDENTIAL version: 1.0.1

Example for Task 5, Step 11

MD5 Verification Passed

Example for Task 2, Step 4

Upgrading an MDS 9148:

Upgrading an MDS 9124 / 9134:

Upgrading an MDS 9500 w/Version II Supervisor:

Example of MDS 9513 upgrade output:

Verifying image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin for boot variable

Verifying image type.

EMC CONFIDENTIAL version: 1.0.1

[####################] 100% -- SUCCESS

Extracting "slc2" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.

Extracting "bios" version from image bootflash:/m9500-sf2ek9-mz.5.0.4d.bin.