To upgrade your switch to use the latest Cisco MDS SAN-OS software on your 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 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 9000 Family switch:
•
The console port is physically connected to a computer terminal (or terminal server).
•The management 10/100 Ethernet port (mgmt0) is connected to an external hub, switch, or router.
These procedures are specified in the hardware installation guide for the required product. Refer to one of the following documents to obtain more information:
•Cisco MDS 9100 Series Hardware Installation Guide
•Cisco MDS 9200 Series Hardware Installation Guide
•Cisco MDS 9216 Switch Hardware Installation Guide
•Cisco MDS 9500 Series Hardware Installation Guide
Step 3 Log in to the switch.
Step 4 Issue the copy running-config startup-config command to create a backup of your existing configuration file. Refer to the “Saving Your Configuration” section in the “Initial Configuration” chapter in the Cisco MDS 9000 Family CLI Configuration Guide.
Step 5 Verify that the requested license files installed in the switch are displayed in response to the show license usage command.
Note The switch is initially shipped with the required licenses installed in the system; however, the initial license file will not cover unlicensed features that may be used during the grace period. Refer to the “Obtain a Factory-Installed License” section in the “Obtaining and Installing Licenses” chapter in the Cisco MDS 9000 Family CLI Configuration Guide. If no license is displayed at this point, perform Step 6 and Step 7 to install the required licenses. If the required licenses are displayed at this point, skip to Step 8.
The example CLI output for a valid license follows:
switch# show license usage
Feature Insta License Status Expiry Date Comments
lled Count
--------------------------------------------------------------------------------
FM_SERVER_PKG Yes - Unused never -
MAINFRAME_PKG Yes - Unused never -
ENTERPRISE_PKG Yes - In use never -
SAN_EXTN_OVER_IP Yes 1 Unused never -
--------------------------------------------------------------------------------
The example CLI output for licenses with expiring grace periods follows:
switch# show license usage
Feature Insta License Status Expiry Date Comments
lled Count
--------------------------------------------------------------------------------
FM_SERVER_PKG No - In use Grace Period 78days 5hrs
MAINFRAME_PKG No - Unused -
ENTERPRISE_PKG No - In use Grace Period 88days 5hrs
SAN_EXTN_OVER_IP No 0 Unused -
--------------------------------------------------------------------------------
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=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 SAN-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.
Refer to the “Performing a Manual Installation” section in the “Obtaining and Installing Licenses” chapter in the Cisco MDS 9000 Family CLI Configuration Guide.
Step 7 Install the license key file when you receive it by e-mail. Perform the following steps:
a. Perform the installation by issuing the install license command on the active supervisor module from the switch console.
switch# install license bootflash:license_file.lic
Installing license ..done
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.
b. Exit the switch console.
Refer to the “Installing a License Key File” section in the “Obtaining and Installing Licenses” chapter in the Cisco MDS 9000 Family CLI Configuration Guide.
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 SAN-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/warp/public/687/Directory/DirTAC.shtml. Cisco Systems employees should refer to the Original Storage Manufacturers (OSMs) support matrix.
switch# dir bootflash:
12288 Jan 01 00:01:06 1980 lost+found/
3821032 Apr 06 16:50:22 2006 m9000-ek9-ssi-mzg.2.1.1a.bin
14765056 Mar 21 15:35:06 2006 m9500-sf1ek9-kickstart-mz.2.1.1.bin
15944704 Apr 06 16:46:04 2006 m9500-sf1ek9-kickstart-mz.2.1.1a.bin
48063243 Mar 21 15:34:46 2006 m9500-sf1ek9-mz.2.1.1.bin
48036239 Apr 06 16:45:41 2006 m9500-sf1ek9-mz.2.1.1a.bin
Usage for bootflash://sup-local
130642562 bytes used
53917054 bytes free
184559616 bytes total
Step 9 If you need more space on the active supervisor module bootflash, delete unnecessary files to make space available.
switch# delete bootflash:m9500-sf1ek9-kickstart-mz.2.1.1.bin
switch# delete bootflash:m9500-sf1ek9-mz.2.1.1.bin
Step 10 Verify that there is space available on the standby supervisor module bootflash on a Cisco MDS 9500 Series switch.
switch# dir bootflash://sup-standby/
12288 Jan 01 00:01:06 1980 lost+found/
3821032 Apr 06 16:50:22 2006 m9000-ek9-ssi-mzg.2.1.1a.bin
14765056 Mar 21 15:35:06 2006 m9500-sf1ek9-kickstart-mz.2.1.1.bin
15944704 Apr 06 16:46:04 2006 m9500-sf1ek9-kickstart-mz.2.1.1a.bin
48063243 Mar 21 15:34:46 2006 m9500-sf1ek9-mz.2.1.1.bin
48036239 Apr 06 16:45:41 2006 m9500-sf1ek9-mz.2.1.1a.bin
Usage for bootflash://sup-standby
130642562 bytes used
53917054 bytes free
184559616 bytes total
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# delete bootflash://sup-standby/m9500-sf1ek9-kickstart-mz.2.1.1.bin
switch# delete bootflash://sup-standby/m9500-sf1ek9-mz.2.1.1.bin
Step 12 Access the Software Download Center using this URL:
http://www.cisco.com/public/sw-center/sw-stornet.shtml
Step 13 Click the required Cisco MDS SAN-OS (new) image file.
You see the Technical Support Encryption Software Export Distribution Authorization form.
Step 14 Complete the required forms to obtain authorization.
Step 15 Download the files to an FTP or TFTP server.
Step 16 Copy the MDS SAN-OS kickstart and system images to the active supervisor module bootflash using FTP or TFTP.
Note When you download an image file, change to your FTP environment IP Address or DNS name and the path where the files are located.
switch# copy ftp://ftpserver.cisco.com/MDS/m9500-sf1ek9-kickstart-mz.2.1.2b.bin
bootflash:m9500-sf1ek9-kickstart-mz.2.1.2b.bin
switch# copy ftp://ftpserver.cisco.com/MDS/m9500-sf1ek9-mz.2.1.2b.bin
bootflash:m9500-sf1ek9-mz.2.1.2b.bin
Step 17 Read the release notes for the related image file. Refer to the Cisco MDS 9000 Series Multilayer Switches release notes.
Step 18 Issue the show version command at the EXEC level switch prompt to verify the current software version in the switch.
Step 19 Verify that the switch is running the required software version by issuing the show version command—you might need to downgrade to the latest certified original storage manufacturer (OSM) release.
switch# show version
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2006, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software may be covered under the GNU Public
License or the GNU Lesser General Public License. A copy of
each such license is available at
http://www.gnu.org/licenses/gpl.html and
http://www.gnu.org/licenses/lgpl.html
Software
BIOS: version 1.1.0
loader: version 1.2(2)
kickstart: version 2.1(1a)
system: version 2.1(1a)
BIOS compile time: 10/24/03
kickstart image file is: bootflash:/m9500-sf1ek9-kickstart-mz.2.1.1a.bin
kickstart compile time: 4/6/2005 19:00:00 [09/18/2005 18:47:39]
system image file is: bootflash:/m9500-sf1ek9-mz.2.1.1a.bin
system compile time: 4/6/2005 19:00:00 [09/18/2005 19:15:42]
...
Step 20 Issue the show incompatibility system bootflash:filename command to determine incompatibilities, if any. Refer to the “Determining Incompatibility” section in the “Software Images” chapter in the Cisco MDS 9000 Family CLI Configuration Guide.
The file name specified for this command must already exist in the switch.
Use this command to obtain further information if the install all command returns the following message:
Warning: The startup config contains commands not supported by the standby supervisor; as
a result, some resources might become unavailable after a switchover.
Do you wish to continue? (y/ n) [y]: n
switch# show incompatibility system bootflash:m9500-sf1ek9-mz.2.1.2b.bin
The following configurations on active are incompatible with the system image
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
These incompatibilities can be the result of existing or new software or hardware. You must disable features that are not supported in earlier releases.
switch# config t
switch(config)# no device-alias distribute
switch(config)# exit
switch# copy running-config startup-config
Issue the show incompatibility system bootflash:filename again to verify that there are no incompatibilities.
Step 21 Verify compatibility between the existing software and the new software. See the “Verifying Software Release Compatibility” section for more information.
Step 22 Verify that your switch is running compatible hardware. See the “Verifying Hardware Release and SAN-OS Feature Compatibility” section for more information.
Step 23 If you have configured FC IDs, enable the persistent FC ID feature using the fcdomain fcid persistent vsan command. To display the persistent FC ID feature status, use the show fcdomain fcid vsan for each VSAN on the switch.
The example CLI output follows:
switch# show fcdomain vsan 2
The local switch is the Principal Switch.
Local switch run time information:
State: Stable
Local switch WWN: 20:02:00:05:30:00:a7:9f
Running fabric name: 20:02:00:05:30:00:a7:9f
Running priority: 128
Current domain ID: 0x6e(110)
Local switch configuration information:
State: Enabled
FCID persistence: Enabled
Auto-reconfiguration: Disabled
Contiguous-allocation: Disabled
Configured fabric name: 20:01:00:05:30:00:28:df
Configured priority: 128
Configured domain ID: 0x00(0) (preferred)
Principal switch run time information:
Running priority: 128
Note As of SAN-OS Release 2.0(1b), the persistent FC ID feature is globally enabled on the switch.
Step 24 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.
switch# install all kickstart bootflash:m9500-sf1ek9-kickstart-mz.2.1.2b.bin system
bootflash:m9500-sf1ek9-mz.2.1.2b.bin
Verifying image bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin
[####################] 100% -- SUCCESS
Verifying image bootflash:/m9500-sf1ek9-mz.2.1.2b.bin
[####################] 100% -- SUCCESS
Extracting "slc" version from image bootflash:/m9500-sf1ek9-mz.2.1.2b.bin.
####################] 100% -- SUCCESS
Extracting "ips" version from image bootflash:/m9500-sf1ek9-mz.2.1.2b.bin.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/m9500-sf1ek9-mz.2.1.2b.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin.
[####################] 100% -- SUCCESS
Extracting "loader" version from image bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin.
[####################] 100% -- SUCCESS
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive rolling
2 yes disruptive rolling Hitless upgrade is not supported
3 yes disruptive rolling Hitless upgrade is not supported
4 yes non-disruptive rolling
5 yes non-disruptive reset
6 yes non-disruptive reset
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- -------------------- -------------------- ------------
1 slc 2.1(2a) 2.1(2b) yes
1 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no
2 ips 2.1(2a) 2.1(2b) yes
2 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no
3 ips 2.1(2a) 2.1(2b) yes
3 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no
4 slc 2.1(2a) 2.1(2b) yes
4 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no
5 system 2.1(2a) 2.1(2b) yes
5 kickstart 2.1(2a) 2.1(2b) yes
5 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no
5 loader 1.2(2) 1.2(2) no
6 system 2.1(2a) 2.1(2b) yes
6 kickstart 2.1(2a) 2.1(2b) yes
6 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no
6 loader 1.2(2) 1.2(2) no
Do you want to continue with the installation (y/n)? [n] y
Install is in progress, please wait.
Syncing image bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin to standby.
[####################] 100% -- SUCCESS
Syncing image bootflash:/m9500-sf1ek9-mz.2.1.2b.bin to standby.
[####################] 100% -- SUCCESS
Jan 18 23:40:03 Hacienda %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from
Performing configuration copy.
[####################] 100% -- SUCCESS
Module 6: Waiting for module online.
|
Auto booting bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin
bootflash:/m9500-sf1ek9-mz.2.1.2b.bin...
Booting kickstart image: bootflash:/m9500-sf1ek9-kickstart-mz.2.1.2b.bin....
.....................................Image verification OK
Starting kernel...
INIT: version 2.78 booting
Checking all filesystems..r.r.. done.
Loading system software
Uncompressing system image: bootflash:/m9500-sf1ek9-mz.2.1.2b.bin
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCC
INIT: Entering runlevel: 3
If the configuration meets all guidelines when the install all command is issued, all modules (supervisor and switching) are upgraded. Refer to the “Benefits of Using the install all Command” section in the “Software Images” chapter in the Cisco MDS 9000 Family CLI Configuration Guide.
Step 25 Open a new terminal session to view the upgraded supervisor module using the show module command. Refer to the “Viewing the State of A Module” section in the “Managing Modules” chapter in the Cisco MDS 9000 Family CLI Configuration Guide.
switch# show module
Mod Ports Module-Type Model Status
--- ----- ------------------------------- ------------------ ------------
2 8 IP Storage Services Module DS-X9308-SMIP ok
4 0 Caching Services Module ok
5 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 active *
6 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 ha-standby
8 0 Caching Services Module DS-X9560-SMAP ok
9 32 1/2 Gbps FC Module DS-X9032 ok
Mod Sw Hw World-Wide-Name(s) (WWN)
--- ----------- ------ --------------------------------------------------
2 2.1(2b) 0.206 20:41:00:05:30:00:00:00 to 20:48:00:05:30:00:00:00
5 2.1(2b) 0.602 --
6 2.1(2b) 0.602 --
8 2.1(2b) 0.702 --
9 2.1(2b) 0.3 22:01:00:05:30:00:00:00 to 22:20:00:05:30:00:00:00
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
2 00-05-30-00-9d-d2 to 00-05-30-00-9d-de JAB064605a2
5 00-05-30-00-64-be to 00-05-30-00-64-c2
6 00-d0-97-38-b3-f9 to 00-d0-97-38-b3-fd JAB06350B1R
8 00-05-30-01-37-7a to 00-05-30-01-37-fe JAB072705ja
9 00-05-30-00-2d-e2 to 00-05-30-00-2d-e6 JAB06280ae9
* this terminal session
You have now upgraded the Cisco MDS SAN-OS software in your existing switch.
Verify that the system image files for the downgrade are present on the active supervisor module bootflash:.
If you need more space on the active supervisor module bootflash:, use the delete command to remove unnecessary files.
eddynurh