Cisco AJ732A - MDS 9134 Fabric Switch Instruction Manual

Send documentation comments to mdsfeedbac[email protected].
Americas Headquarters:
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.1(3)
Release Date: May 15, 2007
Text Part Number: OL-12208-05
This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use
this document in conjunction with documents listed in the “Related Documentation” section on page 33.
Note Release notes are sometimes updated with new information on restrictions and caveats. Refer to the
following website for the most recent version of the Cisco MDS 9000 Family Release Notes:
http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html
Contents
This document includes the following sections:
•Introduction, page 2
•Components Supported, page 2
•Software Download Process, page 6
•Upgrading Your Cisco MDS SAN-OS Software Image, page 9
•Downgrading Your Cisco MDS SAN-OS Software Image, page 17
•New Features in Cisco MDS SAN-OS Release 3.1(3), page 20
•Limitations and Restrictions, page 24
•Caveats, page 27
•Related Documentation, page 33
•Obtaining Documentation, Obtaining Support, and Security Guidelines, page 35

Send documentation comments to mdsfeedbac[email protected].
2
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Introduction
Introduction
The Cisco MDS 9000 Family of Multilayer Directors and Fabric Switches provides industry-leading
availability, scalability, security, and management, allowing you to deploy high performance
storage-area networks with lowest total cost of ownership. Layering a rich set of intelligent features onto
a high performance, protocol agnostic switch fabric, the Cisco MDS 9000 Family addresses the stringent
requirements of large data center storage environments: uncompromising high availability, security,
scalability, ease of management, and seamless integration of new technologies.
The Cisco MDS 9000 Family SAN-OS is the underlying system software that powers the Cisco MDS
9500 Series, 9200 Series, and 9100 Series multilayer switches. The Cisco SAN-OS provides intelligent
networking features, such as multiprotocol and multitransport integration, virtual SANs (VSANs),
advanced security, sophisticated debug analysis tools, and unified SAN management.
Components Supported
Table 1 lists the SAN-OS software part number and hardware components supported by the Cisco MDS
9000 Family.
Note To use the Cisco Storage Services Enabler package, Cisco MDS SAN-OS Release 1.3(5) or later must
be installed on the MDS switch.
Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components
Component Part Number Description Applicable Product
Software M95S2K9-3.1.3 MDS 9500 Supervisor/Fabric-2, SAN-OS software. MDS 9500 Series only
M95S1K9-3.1.3 MDS 9500 Supervisor/Fabric-I, SAN-OS software. MDS 9500 Series only
M92S1K9-3.1.3 MDS 9216 Supervisor/Fabric-I, SAN-OS software. MDS 9200 Series only
M91S2K9-3.1.3 MDS 9100 Supervisor/Fabric-2, SAN-OS software. MDS 9100 Series only
M91S1K9-3.1.3 NDS 9100 Supervisor/Fabric-I, SAN-OS software MDS 9100 Series only

Send documentation comments to mdsfeedbac[email protected].
3
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Components Supported
License M9500ENT1K9 Enterprise package. MDS 9500 Series
M9200ENT1K9 Enterprise package. MDS 9200 Series
M9100ENT1K9 Enterprise package. MDS 9100 Series
M9500FIC1K9 Mainframe package. MDS 9500 Series
M9200FIC1K9 Mainframe package. MDS 9200 Series
M9100FIC1K9 Mainframe package. MDS 9100 Series
M9500FMS1K9 Fabric Manager Server package. MDS 9500 Series
M9200FMS1K9 Fabric Manager Server package. MDS 9200 Series
M9100FMS1K9 Fabric Manager Server package. MDS 9100 Series
M9500EXT1K9 SAN Extension over IP package for IPS-8 module. MDS 9500 Series
M9200EXT1K9 SAN Extension over IP package for IPS-8 module. MDS 9200 Series
M9500EXT14K9 SAN Extension over IP package for IPS-4 module. MDS 9500 Series
M9200EXT14K9 SAN Extension over IP package for IPS-4 module. MDS 9200 Series
M9500EXT12K9 SAN Extension over IP package for MPS 14+2 module. MDS 9500 Series
M9200EXT12K9 SAN Extension over IP package for MPS 14+2 module. MDS 9200 Series
M9500SSE1K9 Storage Services Enabler package. MDS9500Serieswith
SSM
M9200SSE1K9 Storage Services Enabler package. MDS9200Serieswith
SSM
M9124PL8-4G On-Demand Ports Activation License MDS 9124 Switch
HP-PL12-4G On-Demand Ports Activation License Cisco Fabric Switch
for HP c-Class
BladeSystem only
IBM-PL10-4G On-Demand Ports Activation License CiscoFabricSwitchfor
IBM BladeCenter only
Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Component Part Number Description Applicable Product

Send documentation comments to mdsfeedbac[email protected].
4
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Components Supported
Chassis DS-C9513 MDS 9513 director (13-slot modular chassis with 11
slots for switching modules, and 2 slots reserved for
Supervisor 2 modules only—SFPs1sold separately).
MDS 9513 only
DS-C9509 MDS 9509 director, base configuration (9-slot modular
chassis includes 7 slots for switching modules and 2
slots for supervisor modules—SFPs sold separately).
MDS 9509 only
DS-C9506 MDS 9506 director (6-slot modular chassis includes 4
slots for switching modules and 2 slots for supervisor
modules—SFPs sold separately).
MDS 9506 only
DS-C9216-K9 MDS 9216 16-port semi-modular fabric switch
(includes 16 1-Gbps/2-Gbps Fibre Channel ports, power
supply, and expansion slot—SFPs sold separately).
MDS 9216 only
DS-C9216A-K9 MDS 9216A 16-port semi-modular fabric switch
(includes 16 1-Gbps/2-Gbps Fibre Channel ports, power
supply, and expansion slot—SFPs sold separately).
MDS 9216A only
DS-C9216i-K9 MDS 9216i 16-port semi-modular fabric switch
(includes 14 1-Gbps/2-Gbps Fibre Channel ports, 2
Gigabit Ethernet ports, power supply, and expansion
slot—SFPs sold separately).
MDS 9216i only
DS-C9140-K9 MDS 9140 fixed configuration (non-modular) fabric
switch (includes 8 full rate ports and 32 host-optimized
ports).
MDS 9140 only
DS-C9124-K9 MDS 9124 fixed configuration (non-modular)
multilayer fabric switch (includes 8 enabled ports; an
on-demand ports activation license can enable 8
additional ports, up to 24 ports).
MDS 9124 only
DS-C9120-K9 MDS 9120 fixed configuration, non-modular, fabric
switch (includes 4 full rate ports and 16 host-optimized
ports).
MDS 9120 only
DS-HP-FC-K9 Cisco Fabric Switch for HP c-Class BladeSystem
(includes sixteen internal and eight external active ports
and four 4-Gb SFPs installed, or eight internal and four
external active ports and two 4-Gb SFPs installed).
Cisco Fabric Switch
for HP c-Class
BladeSystem only
DS-IBM-FC-K9 Cisco Fabric Switch for IBM BladeCenter (includes
fourteen internal and six external ports) CiscoFabricSwitchfor IBM BladeCenter only
External
crossbar module DS-13SLT-FAB1 MDS 9513 crossbar fabric module. MDS 9513 only
Supervisor
modules DS-X9530-SF2-K9 MDS 9500 Supervisor-2, module. MDS 9500 Series only
DS-X9530-SF1-K9 MDS 9500 Supervisor/Fabric-I module.
Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Component Part Number Description Applicable Product

Send documentation comments to mdsfeedbac[email protected].
5
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Components Supported
Switching
modules DS-X9016 MDS 9000 16-port 1-Gbps/2-Gbps Fibre Channel module (SFPs sold separately). MDS 9500 Series and 9200 Series
DS-X9032 MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel
module (SFPs sold separately).
DS-X9112 MDS 9000 12-port 4-Gbps Fibre Channel module (SFPs
sold separately). MDS 9500 Series and 9200 Series, except
for the MDS 9216
DS-X9124 MDS 9000 24-port 4-Gbps Fibre Channel module (SFPs
sold separately). MDS 9500 Series and 9200 Series, except
for the MDS 9216
DS-X9148 MDS 9000 48-port 4-Gbps Fibre Channel module (SFPs
sold separately). MDS 9500 Series and 9200 Series, except
for the MDS 9216
DS-X9704 MDS 9000 4-port 10-Gbps Fibre Channel module (SFPs
sold separately) MDS 9500 Series and 9200 Series, except
for the MDS 9216
Services
modules DS-X9308-SMIP 8-port Gigabit Ethernet IP Storage services module. MDS 9500 Series and 9200 Series
DS-X9304-SMIP 4-port Gigabit Ethernet IP Storage services module.
DS-X9032-SSM MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel
Storage Services Module (SSM).
DS-X9302-14K9 14-port Fibre Channel/2-port Gigabit Ethernet
Multiprotocol Services (MPS-14/2) module.
Optics DS-X2-FC10G-SR X2/SC optics, 10-Gbps Fibre Channel for Short Reach. MDS 9500 Series and
9200 Series, except
for the MDS 9216
DS-X2-FC10G-LR X2/SC optics, 10-Gbps Fibre Channel for Long Reach.
DS-X2-FC10G-ER X2/SC optics, 10-Gbps Fibre Channel for Extended
Reach (40 km).
LC-type
fiber-optic SFP DS-SFP-FC-2G-SW 2-Gbps/1-Gbps Fibre Channel—short wavelength SFP. MDS 9000 Family
DS-SFP-FC-2G-LW 2-Gbps/1-Gbps Fibre Channel—long wavelength SFP.
DS-SFP-FCGE-SW 1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre
Channel—short wavelength SFP.
DS-SFP-FCGE-LW 1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre
Channel—long wavelength SFP.
DS-SFP-GE-T 1-Gbps Ethernet SFP.
DS-SFP-FC4G-SW 4-Gbps/2-Gbps/1-Gbps Fibre Channel—short
wavelength SFP for DS-X91xx switching modules. MDS 9500 Series and 9200 Series, except
for the MDS 9216
DS-SFP-FC4G-MR 4-Gbps/2-Gbps/1-Gbps Fibre Channel—long
wavelength SFP for DS-X91xx switching modules only.
Supports distances up to 4 km.
DS-SFP-FC4G-LW 4-Gbps/2-Gbps/1-Gbps Fibre Channel—long
wavelength SFP for DS-X91xx switching modules only.
Supports distances up to 10 km.
Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Component Part Number Description Applicable Product

Send documentation comments to mdsfeedbac[email protected].
6
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Software Download Process
Software Download Process
Use the software download procedure to upgrade to a later version, or downgrade to an earlier version,
of an operating system. This section describes the software download process for the Cisco MDS
SAN-OS and includes the following topics:
•Determining the Software Version, page 7
•Downloading Software, page 7
•Selecting the Correct Software Image for an MDS 9500 Series Switch, page 8
•Migrating from Supervisor-1 Modules to Supervisor-2 Modules, page 9
•Configuring Generation 2 Switching Modules, page 9
CWDM2DS-CWDM-xxxx Gigabit Ethernet and 1-Gbps/2-Gbps Fibre Channel SFP
LC interface xxxx nm, where xxxx = 1470, 1490, 1510,
1530, 1550, 1570, 1590, or 1610 nm.
MDS 9000 Family
DS-CWDM-MUX-4 Add/drop multiplexer for four CWDM wavelengths.
DS-CWDM-MUX-8 Add/drop multiplexer for eight CWDM wavelengths.
DS-CWDMCHASSIS Two slot chassis for CWDM add/drop multiplexers.
Power supplies DS-CAC-6000W 6000-W AC power supply. MDS 9513 only
DS-CAC-2500W 2500-W AC power supply. MDS 9509 only
DS-CDC-2500W 2500-W DC power supply.
DS-CAC-3000W 3000-W AC power supply.
DS-CAC-4000W-US 4000-W AC power supply for US (cable attached).
DS-CAC-4000W-INT 4000-W AC power supply international (cable
attached).
DS-CAC-1900W 1900-W AC power supply. MDS 9506 only
DS-CDC-1900W 1900-W DC power supply.
DS-CAC-845W 845-W AC power supply. MDS 9200 Series only
DS-CAC-300W 300-W3AC power supply. MDS 9100 Series only
CompactFlash MEM-MDS-FLD512M MDS 9500 supervisor CompactFlash disk, 512 MB. MDS 9500 Series only
Port analyzer
adapter DS-PAA-2, DS-PAA A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel
traffic in a switched fabric.
MDS 9000 Family
CD-ROM M90FM-CD-212= MDS 9000 Management Software and Documentation
CD-ROM, spare. MDS 9000 Family
1. SFP = small form-factor pluggable
2. CWDM = coarse wavelength division multiplexing
3. W = Watt
Table 1 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Component Part Number Description Applicable Product

Send documentation comments to mdsfeedbac[email protected].
7
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Software Download Process
Determining the Software Version
To determine the version of Cisco MDS SAN-OS software currently running on a Cisco MDS 9000
Family switch using the CLI, log in to the switch and enter the show version EXEC command.
To determine the version of Cisco MDS SAN-OS software currently running on a Cisco MDS 9000
Family switch using the Fabric Manager, view the Switches tab in the Information pane, locate the
switch using the IP address, logical name, or WWN, and check its version in the Release column.
Note We strongly recommend that you use the latest available software release supported by your vendor for
all Cisco MDS 9000 Family products.
Downloading Software
The Cisco MDS SAN-OS software is designed for mission-critical high availability environments. To
realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend
that you install dual supervisor modules.
To download the latest Cisco MDS SAN-OS software, access the Software Center at this URL:
http://www.cisco.com/public/sw-center
See the following sections in this release note for details on how you can nondisruptively upgrade your
Cisco MDS 9000 switch. Issuing the install all command from the CLI, or using Fabric Manager to
perform the downgrade, enables the compatibility check. The check indicates if the upgrade can happen
nondisruptively or disruptively depending on the current configuration of your switch and the reason.
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
At a minimum, you need to disable the default device alias distribution feature using the no device-alias
distribute command in global configuration mode. The show incompatibility system
bootflash:1.3(x)_filename command determines which additional features need to be disabled.
Note Refer to the “Determining Software Compatibility” section of the Cisco MDS 9000 Family CLI
Configuration Guide for more details.
Note If you would like to request a copy of the source code under the terms of either GPL or LGPL, please
send an e-mail to [email protected].

Send documentation comments to mdsfeedbac[email protected].
8
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Software Download Process
Selecting the Correct Software Image for an MDS 9100 Series Switch
The system and kickstart image that you use for an MDS 9100 series switch depends on which switch
you use, as shown in Table 2.
Selecting the Correct Software Image for an MDS 9500 Series Switch
The system and kickstart image that you use for an MDS 9500 Series switch depends on whether the
switch is based on a Supervisor-1 module or a Supervisor-2 module, as shown in Table 3.
Use the show module command to display the type of supervisor module in the switch.
For a Supervisor-1 module, the output might look like this:
switch# show module
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
...
...
5 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 active*
6 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 ha-standby
For a Supervisor-2 module, the output might look like this:
switch# show module
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
...
...
7 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 active *
8 0 Supervisor/Fabric-2 DS-X9530-SF2-K9 ha-standby
Table 2 Software Image for MDS 9100 Series Switch
Switch Image
MDS 9120 or MDS 9140 Filename begins with m9100-s1ek9
MDS 9124, Cisco Fabric Switch for HP
BladeSystem, or Cisco Fabric Switch for IBM
BladeCenter
Filename begins with m9100-s2ek9
Table 3 Software Image for Supervisor Type
Supervisor Type Switch Image
Supervisor-1 module MDS 9506 and 9509 Filename begins with m9500-sf1ek9
Supervisor-2 module MDS 9506, 9509, and 9513 Filename begins with m9500-sf2ek9

Send documentation comments to mdsfeedbac[email protected].
9
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Upgrading Your Cisco MDS SAN-OS Software Image
Migrating from Supervisor-1 Modules to Supervisor-2 Modules
As of Cisco MDS SAN-OS Release 3.0(1), the Cisco MDS 9509 and 9506 Directors support both
Supervisor-1 and Supervisor-2 modules. Supervisor-1 and Supervisor-2 modules cannot be installed in
the same switch, except during migration. Both the active and standby supervisor modules must be of
the same type, either Supervisor-1 or Supervisor-2 modules. For Cisco MDS 9513 Directors, both
supervisor modules must be Supervisor-2 modules.
Caution Migrating your supervisor modules is a disruptive operation.
Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported.
To migrate from a Supervisor-1 module to a Supervisor-2 module, refer to the step-by-step instructions
in the Cisco MDS 9000 Family CLI Configuration Guide.
Configuring Generation 2 Switching Modules
The Cisco MDS 9500 Multilayer Directors are designed to operate with any combination of Cisco MDS
9000 Generation 1 and Generation 2 modules. However, there are limitations to consider when
combining the various modules and supervisors in the Cisco MDS 9500 Series platform chassis. The
references listed in this section provide specific information about configurations that combine different
modules and supervisors.
For information on configuring Generation 2 switching modules, refer to:
http://www.cisco.com/en/US/products/ps5989/products_configuration_guide_chapter09186a0080664c6b.html
For information on port index availability, refer to:
http://www.cisco.com/en/US/products/ps5990/products_installation_guide_chapter09186a0080419599.html
For information on Cisco MDS 9000 hardware and software compatibility, refer to:
http://www.cisco.com/en/US/products/ps5989/products_device_support_table09186a00805037ee.html
Upgrading Your Cisco MDS SAN-OS Software Image
This section lists the guidelines recommended for upgrading your Cisco MDS SAN-OS software image
and contains the following sections:
•Upgrading Your Version of Cisco Fabric Manager, page 10
•Upgrading with IVR Enabled, page 13
•Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(3), page 14
•Upgrading the SSI Image on Your SSM, page 15
•Upgrading a Switch with Insufficient Space for Two Images on the Bootflash, page 16
•Upgrading a Cisco MDS 9124 Switch, page 17
•Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch, page 17

Send documentation comments to mdsfeedbac[email protected].
10
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Upgrading Your Cisco MDS SAN-OS Software Image
Caution Before upgrading your Cisco MDS SAN-OS software image, you must run the Compact Flash Report
utility described in the “Managing System Hardware” section of the Cisco MDS 9000 Family Fabric
Manager Configuration Guide. This reporting feature automatically scans your switch fabric and reports
the status of Compact Flash on certain switch modules. To run this utility prior to upgrading your Cisco
SAN-OS software image, upgrade Cisco Fabric Manager as described in the “Upgrading Your Version
of Cisco Fabric Manager” section on page -10.
For instructions on how to scan your switch fabric and display the status of Compact Flash using CLI
commands, refer to the “Managing System Hardware” section of the Cisco MDS 9000 Family CLI
Configuration Guide.
Upgrading Your Version of Cisco Fabric Manager
To upgrade your version of Cisco Fabric Manager, or install Cisco Fabric Manager for the first time,
follow these steps:
Step 1 Download m9000-fm-3.1.3.jar from the Software Center on Cisco.com
(http://www.cisco.com/cgi-bin/tablebuild.pl/mds-fm). You must have a CCO account to access the files
on Software Center.
Note As of Cisco MDS SAN-OS Release 3.1, Cisco Fabric Manager requires Java 1.5.
Step 2 Launch the Fabric Manager installation program by doing one of the following:
a. Navigate to the folder where you have downloaded the file and double-click it.
b. Open the file using Internet Explorer.
c. Enter java -jar m9000-fm-3.1.3.jar on the Windows or UNIX command line.
Step 3 Select an installation folder for Fabric Manager on your workstation. The default location is C:\Program
Files\Cisco Systems\MDS 9000 for Windows. On a Solaris or Linux machine, the installation path name
is /usr/local/cisco_mds9000 or $HOME/cisco_mds9000, depending on the permissions of the user
performing the installation.
Note The Fabric Manager Server and the Fabric Manager Client must be able to communicate with
each other at all times. They can be installed on different workstations or the same workstation.
Step 4 Check the Don't install and run FM Server check box if you are installing just the Fabric Manager
Client on a remote workstation.
Note For other methods and details on upgrading, downgrading, and uninstalling Cisco Fabric Manager, refer
to the Cisco MDS 9000 Family Fabric Manager Configuration Guide and the Cisco MDS 9000 Fabric
Manager Quick Configuration Guide.
Step 5 Click Finish to complete the Cisco Fabric Manager installation.

Send documentation comments to mdsfeedbac[email protected].
11
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Upgrading Your Cisco MDS SAN-OS Software Image
General Upgrading Guidelines
Use the following guidelines when upgrading to Cisco MDS SAN-OS Release 3.1(3):
•Install and configure dual supervisor modules.
•Issue the show install all impact upgrade-image CLI command to determine if your upgrade will
be nondisruptive.
•Follow the recommended guidelines for upgrading a Cisco MDS 9124 Switch as described in
“Upgrading a Cisco MDS 9124 Switch” section on page 17.
•Follow the guidelines for upgrading a single supervisor switch as described in “Performing a
Disruptive Upgrade on a Single Supervisor MDS Family Switch” section on page 17.
•Be aware that some features impact whether an upgrade is disruptive or nondisruptive:
– Fibre Channel Ports: Traffic on Fibre Channel ports can be nondisruptively upgraded. See
Table 4 for the nondisruptive upgrade path for all SAN-OS releases.
– SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write
acceleration, is disrupted during an upgrade. SSM Fibre Channel traffic is not.
– Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during an upgrade or
downgrade. Thisincludes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module.
Those nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric
reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose
connectivity to iSCSI targets while the upgrade is in progress.
– IVR: With IVR enabled, you must follow additional steps if you are upgrading from Cisco
SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the “Upgrading with IVR Enabled” section
on page 13 for these instructions.
– FICON: If you have FICON enabled, the upgrade path is different. See Table 5.
Use Table 4 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.1(3). Find the
image release number you are currently using in the Current column of the table and use the path
recommended.
Note The software upgrade information in Table 4 applies only to Fibre Channel switching traffic. Upgrading
system software disrupts IP traffic and SSM intelligent services traffic.
Table 4 Nondisruptive Upgrade Path to SAN-OS Release 3.1(3)
Current Nondisruptive Upgrade Path
SAN-OS 3.1(2b) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 3.1(2a) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 3.1(2) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 3.1(1) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 3.0(3a) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 3.0(3) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 3.0(2a) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 3.0(2) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 3.0(1) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).

Send documentation comments to mdsfeedbac[email protected].
12
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Upgrading Your Cisco MDS SAN-OS Software Image
Use Table 5 to determine your FICON nondisruptive upgrade path to Cisco MDS SAN-OS Release
3.1(3). Find the image release number you are currently using in the Current Release with FICON
Enabled column of the table and use the path recommended.
Note Cisco MDS SAN-OS Release 3.1(3) is not FICON certified.
SAN-OS 2.1(3) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 2.1(2e) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 2.1(2d) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 2.1(2b) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 2.1(2) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.1(3).
or.
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.1(3).
SAN-OS 2.1(1b) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.1(3).
SAN-OS 2.1(1a) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.1(3).
SAN-OS 2.0(x) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.1(3).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.1(3).
SAN-OS 1.x Upgrade to SAN-OS Release 1.3(4a), then to Release 2.1(2b), and then upgrade to
Release 3.1(3).
Table 4 Nondisruptive Upgrade Path to SAN-OS Release 3.1(3) (continued)
Current Nondisruptive Upgrade Path

Send documentation comments to mdsfeedbac[email protected].
13
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Upgrading Your Cisco MDS SAN-OS Software Image
Upgrading with IVR Enabled
An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade
from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive.
Some possible scenarios include the following:
•FCIP connection flapping during the upgrade process resulting in fabric segmentation or merge.
•ISL flap results in fabric segmentation or merge because of hardware issues or a software bug.
•ISL port becomes part of PCP results in fabric segmentation or merge because of a port flap.
If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state
because of a domain overlap.
This issue was resolved in Cisco SAN-OS Release 2.1(2b); therefore, you must upgrade to Release
2.1(2b) before upgrading to Release 3.1(3). An upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b),
or 2.1(2a) to Release 2.1(2b) when IVR is enabled requires that you follow the procedure below, and
then follow the upgrade guidelines listed in the “Upgrading Your Version of Cisco Fabric Manager”
section on page 10. If you have VSANs in interop mode 2 or 3, you must issue an IVR refresh for those
VSANs.
To upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) for all other
VSANs with IVR enabled, follow these steps:
Step 1 Configure static domains for all switches in all VSANs where IVR is enabled. Configure the static
domain the same as the running domain so that there is no change in domain IDs. Make sure that all
domains are unique across all of the IVR VSANs. We recommend this step as a best practice for
IVR-non-NAT mode. Issue the fcdomain domain id static vsan vsan id command to configure the static
domains.
Note Complete Step 1 for all switches before moving to Step 2.
Table 5 FICON Nondisruptive Upgrade Path to SAN-OS 3.1(3)
Current Release with
FICON Enabled Upgrade Path
SAN-OS 3.0(2) You can nondisruptively upgrade directly to SAN-OS Release 3.1(3).
SAN-OS 2.0(2b) Use the interface shutdown command to administratively shut any Fibre
Channel ports on Generation 1 modules that are in an operationally down
state before nondisruptively upgrading from SAN-OS Release 2.0(2b) to
SAN-OS Release 3.0(2), and then upgrade to Release 3.1(3). An
operationally down state includes Link failure or not-connected, SFP
not present,or Error Disabled status in the output of a show interface
command. When an interface is administratively shut it will then show as
Administratively down. Interfaces that are currently up or trunking do
not need to be shut down.
SAN-OS 1.x Upgrade to SAN-OS Release 3.0(2). Use the interface shutdown
command to shut all the ports operationally down and administratively up
on all the Generation 1 modules before nondisruptively upgrading to
Release 2.0(2b) and then upgrade to 1.3(4a).

Send documentation comments to mdsfeedbac[email protected].
14
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Upgrading Your Cisco MDS SAN-OS Software Image
Step 2 Issue the no ivr virtual-fcdomain-add vsan-ranges vsan-range command to disable RDI mode on all
IVR enabled switches. The range of values for a VSAN ID is 1 to 4093. This can cause traffic disruption.
Note Complete Step 2 for all IVR enabled switches before moving to Step 3.
Step 3 Check the syslogs for any ISL that was isolated.
2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED:
%$VSAN 2005%$ Isolation of interface
port-channel 52 (reason: unknown failure)
2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$
Isolation of interface port-channel 51
(reason: domain ID assignment failure)
Step 4 Issue the following commands for the isolated switches in Step 3:
switch(config)# vsan database
switch(config-vsan-db)# vsan vsan-id suspend
switch(config-vsan-db)# no vsan vsan-id suspend
Step 5 Issue the ivr refresh command to perform an IVR refresh on all the IVR enabled switches.
Step 6 Issue the copy running-config startup-config command to save the RDI mode in the startup
configuration on all of the switches.
Step 7 Follow the normal upgrade guidelines for Release 2.1(2b). If you are adding new switches running Cisco
MDS SAN-OS Release 2.1(2b) or later, upgrade all of your existing switches to Cisco SAN-OS Release
2.1(2b) as described in this workaround. Then follow the normal upgrade guidelines for Release 3.1(3).
Note RDI mode should not be disabled for VSANs running in interop mode 2 or interop mode 3.
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(3)
Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured
in auto mode, which is the default for releases prior to Release 3.0(1).
Note To avoid any traffic disruption, modify the configuration of the SSM ports as described below, before
upgrading a SAN-OS software image prior to Release 3.1(3).
For more information on upgrading SAN-OS software, see the “Upgrading Your Cisco MDS SAN-OS
Software Image” section on page 9.
If the configuration is not updated before the upgrade, the installation process for the new image will
automatically convert all ports configured in auto mode to Fx mode. This change in mode might cause
a disruption if the port is currently operating in E mode.
To upgrade the image on your SSM without any traffic disruption, follow these steps:
Step 1 Verify the operational mode for each port on the SSM using the show interface command:
switch# show interface fc 2/1 - 32
fc2/1 is up

Send documentation comments to mdsfeedbac[email protected].
15
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Upgrading Your Cisco MDS SAN-OS Software Image
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:4b:00:0d:ec:09:3c:00
Admin port mode is auto <-------- shows port is configured in auto mode
snmp traps are enabled
Port mode is F, FCID is 0xef0300 <-------- shows current port operational mode is F
Port vsan is 1
Speed is 2 Gbps
Transmit B2B Credit is 3
Step 2 Change the configuration for the first port of the quad when the admin port mode is auto. (A quad is a
group of four ports, supported by a data path processor (DPP). The groups are 1 to 4, 5 to 8, 9 to 12, and
so on.) Do not leave the port mode set to auto.
a. Set the port admin mode to E or Fx if the current operational port mode is E, TE, F or FL.
switch# config t
switch(config)# interface fc 2/1
switch(config-if)# switchport mode fx
b. Set the port admin mode to E if the current operational port mode is E:
switch# config t
switch(config)# interface fc 2/5
switch(config-if)# switchport mode e
Step 3 Change the configuration for ports 2, 3, and 4 of the quad:
a. Set the admin port mode to Fx if the admin port mode of these ports is E, TE, or auto.
switch# config t
switch(config)# interface fc 2/2
switch(config-if)# switchport mode fx
b. If the first port in the port group has admin mode E or if the port is operational in E port mode,
change the admin state of ports 2, 3, and 4 to shutdown.
switch# config t
switch(config)# interface fc 2/2
switch(config-if)# shutdown
Step 4 Save the running configuration to the startup configuration before the upgrade procedure to ensure that
the changes are preserved during and after the upgrade. To save the configuration, enter the following
command:
switch# copy running-config startup-config
Upgrading the SSI Image on Your SSM
Use the following guidelines to nondisruptively upgrade the SSI image on your SSM:
•Install and configure dual supervisor modules.
•SSM intelligent services traffic on SSM ports is disrupted during upgrades. Fibre Channel switching
traffic is not disrupted under the following conditions:
– Upgrade the SSI boot images on the SSMs on the switch to a release version supported by your
Cisco SAN-OS release. Refer to the Cisco MDS SAN-OS Release Compatibility Matrix for
Storage Service Interface Images.

Send documentation comments to mdsfeedbac[email protected].
16
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Upgrading Your Cisco MDS SAN-OS Software Image
– All SSM applications are disabled. Use the show ssm provisioning CLI command to determine
what applications are configured. Use the no ssm enable feature CLI command to disable these
applications.
– No SSM ports are in auto mode. See the “Reconfiguring SSM Ports Before Upgrading to
SAN-OS Release 3.1(3)” section on page 14.
– The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld
CLI command to determine your EPLD version. Refer to the Cisco MDS 9000 Family Release
Notes for Cisco MDS 9000 EPLD Images to upgrade your EPLD image.
– Refer to the Cisco MDS Storage Services Module Interoperability Support Matrix and the
“Managing Modules” chapter in the Cisco MDS 9000 Family CLI Configuration Guide,
Release 3.x, for information on upgrading your SSM.
Caution Upgrading from Cisco MDS SAN-OS Release 2.1(1b) or earlier to Release 2.1.2 or later can disrupt
traffic on any SSM installed on your MDS switch
Upgrading a Switch with Insufficient Space for Two Images on the Bootflash
To upgrade the SAN-OS image on a Cisco MDS 9000 Family switch requires enough space on the
internal CompactFlash (also referred to as bootflash) to accommodate both the old software image and
the new software image.
As of Cisco MDS SAN-OS Release 3.1(1), on MDS switches with a 256-MB CompactFlash, it is
possible in some scenarios that a user might be unable to fit two images on the bootflash. This lack of
space on the bootflash might cause the upgrade process to fail because new images are always copied
onto the bootflash during an upgrade.
The following MDS switches are affected by this issue:
•MDS 9216 and MDS 9216i
•MDS 9120 and MDS 9140
•MDS 9500 Series switches with a Supervisor 1 module
To work around an image upgrade failure caused by a lack of space on the bootflash, follow these steps:
Step 1 Prior to installing the new image, copy the old (existing) system image file to an external server. You
may need to reinstall this file later.
Step 2 Delete the old system image file from the bootflash by using either the Fabric Manager install utility or
the CLI delete bootflash: command. The system image file does not contain the word “kickstart” in the
filename.
switch# delete bootflash:m9200-ek9-mz.3.0.3.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-sf1ek9-mz.3.0.3.bin
Step 3 Start the image upgrade or installation process using the Fabric Manager install utility or the CLI install
all command.

Send documentation comments to mdsfeedbac[email protected].
17
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Downgrading Your Cisco MDS SAN-OS Software Image
Step 4 If the new installation or upgrade fails while copying the image and you want to keep the old (existing)
image, then copy the old image (that you saved to an external server in Step 1) to the bootflash using
either Fabric Manager or the copy command.
Step 5 If the switch fails to boot, then follow the recovery procedure described in the “Troubleshooting Installs,
Upgrades, and Reboots” section of the Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x.
Upgrading a Cisco MDS 9124 Switch
If you are upgrading from Cisco MDS SAN-OS Release 3.1(1) to Cisco SAN-OS Release 3.1(3) on a
Cisco MDS 9124 Switch, follow these guidelines:
•During the upgrade, configuration is not allowed and the fabric is expected to be stable.
•The Fabric Shortest Path First (FSPF) timers must be configured to the default value of 20 seconds;
otherwise, the nondisruptive upgrade is blocked to ensure that the maximum down time for the
control plane can be 80 seconds.
•If there are any CFS commits in the fabric, the nondisruptive upgrade will fail.
•If there is a zone server merge in progress in the fabric, the nondisruptive upgrade will fail.
•If a service terminates the nondisruptive upgrade, the show install all failure-reason command can
display the reason that the nondisruptive upgrade cannot proceed.
•If there is not enough memory in the system to load the new images, the upgrade will be made
disruptive due to insufficient resources and the user will be notified in the compatibility table.
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Cisco MDS SAN-OS software upgrades are disruptive on the following single supervisor Cisco MDS
Family switches:
•MDS 9120 switch
•MDS 9140 switch
•MDS 9216i switch
If you are performing an upgrade on one of those switches, you should follow the nondisruptive upgrade
path shown in Table 4, even though the upgrade is disruptive. Following the nondisruptive upgrade path
ensures that the binary startup configuration remains intact.
If you do not follow the upgrade path, (for example, you upgrade directly from SAN-OS Release 2.1(2b)
to SAN-OS Release 3.1(3)), the binary startup configuration is deleted because it is not compatible with
the new image, and the ASCII startup configuration file is applied when the switch comes up with the
new upgraded image. When the ASCII startup configuration file is applied, there may be errors. Because
of this, we recommend that you follow the nondisruptive upgrade path.
Downgrading Your Cisco MDS SAN-OS Software Image
This section lists the guidelines recommended for downgrading your Cisco MDS SAN-OS software
image and contains the following sections:
•General Downgrading Guidelines, page 18
•Downgrading the SSI Image on Your SSM, page 20

Send documentation comments to mdsfeedbac[email protected].
18
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
Downgrading Your Cisco MDS SAN-OS Software Image
General Downgrading Guidelines
Use the following guidelines to nondisruptively downgrade your Cisco MDS SAN-OS Release 3.1(3):
•Install and configure dual supervisor modules.
•Issue the system no acl-adjacency-sharing execute command to disable acl adjacency usage on
Generation 2 and Generation 1 modules. If this command fails, reduce the number of zones, IVR
zones, TE ports, or a combination of these in the system and issue the command again.
•Disable all features not supported by the downgrade release. Use the show incompatibility system
downgrade-image CLI command to determine what you need to disable.
•Layer 2 switching traffic is not disrupted when downgrading to Cisco SAN-OS Release 2.1(2) or
later.
•Use the show install all impact downgrade-image CLI command to determine if your downgrade
will be nondisruptive.
•Be aware that some features impact whether a downgrade is disruptive or nondisruptive:
– Fibre Channel Ports: Traffic on Fibre Channel ports can be nondisruptively downgraded. See
Table 6 for the nondisruptive downgrade path for all SAN-OS releases.
– SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write
acceleration, is disrupted during a downgrade. SSM Fibre Channel traffic is not.
– Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during a downgrade.
This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module. Those
nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric
reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose
connectivity to iSCSI targets while the downgrade is in progress.
– iSCSI: If you are downgrading from SAN-OS version 3.0(x) to a lower version of SAN-OS,
enable iSCSI if an IPS module or a MPS-14/2 module is online in the switch. Otherwise, the
downgrade will disrupt traffic.
– IVR: With IVR enabled, you must follow additional steps if you are downgrading from Cisco
SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the “Upgrading with IVR Enabled” section
on page 13 for these instructions.
– FICON: If you have FICON enabled, the downgrade path is different. See Table 7.
– iSNS: The iSNS feature does not support a graceful downgrade from Cisco MDS SAN-OS
Release 3.1(3) to any earlier SAN-OS release. Prior to a downgrade from Cisco SAN-OS 3.1(3),
disable the MDS iSNS server and remove all configurations associated with the MDS iSNS
client.
Use Table 6 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.1(3). Find
the SAN-OS image you want to downgrade to in the To SAN-OS Release column of the table and use
the path recommended.
Note The software downgrade information in Table 6 applies only to Fibre Channel switching traffic.
Downgrading system software disrupts IP and SSM intelligent services traffic.

Send documentation comments to mdsfeedbac[email protected].
19
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3)
OL-12208-05
Downgrading Your Cisco MDS SAN-OS Software Image
Use Table 7 to determine your FICON 3.1(3)nondisruptive downgrade path from Cisco SAN-OS Release
3.1(3). Find the image release number you are currently using in the Current Release with FICON
Enabled column of the table and use the path recommended.
Note Cisco MDS SAN-OS Release 3.1(3) is not FICON certified.
Table 6 Nondisruptive Downgrade Path from SAN-OS Release 3.1(3)
To SAN-OS Release Nondisruptive Downgrade Path
SAN-OS 3.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 3.1(2a) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 3.1(2) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 3.1(1) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 3.0(3a) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 3.0(3) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 3.0(2a) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 3.0(2) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 3.0(1) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 2.1(3) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 2.1(2e) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 2.1(2d) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 2.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2b).
SAN-OS 2.1(2) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(2).
SAN-OS 2.1(1b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1b).
SAN-OS 2.1(1a) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1a).
SAN-OS 2.0(4a) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4a).
SAN-OS 2.0(4) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4).
SAN-OS 2.0(3) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(3).
SAN-OS 2.0(2b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(2b).
SAN-OS 2.0(1b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(1b).
SAN-OS 1.x Downgrade to SAN-OS to Release 2.1(2b), then to Release 1.3(4a), and then
downgrade to your SAN-OS 1.x release.

Send documentation comments to mdsfeedbac[email protected].
20
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3) OL-12208-05
New Features in Cisco MDS SAN-OS Release 3.1(3)
Downgrading the SSI Image on Your SSM
Use the following guidelines when downgrading your SSI image on your SSM.
•On a system with at least one SSM installed, the install all command might fail on an SSM when
you downgrade from Cisco SAN-OS Release 3.1(3) to any SAN-OS 2.x release earlier than
SAN-OS Release 2.1(2e). Power down the SSM and perform the downgrade. Bring up the SSM with
the new bootvar set to the 2.x SSI image.
•Downgrade the SSI boot images on the SSMs on the switch to a release version supported by your
Cisco SAN-OS release. Refer to the Cisco MDS SAN-OS Release Compatibility Matrix for Storage
Service Interface Images.
•SSM intelligent services traffic switching on SSM ports is disrupted on upgrades or downgrades.
•Fibre Channel switching traffic on SSM ports is not disrupted under the following conditions:
– All SSM applications are disabled. Use the show ssm provisioning CLI command to determine
if any applications are provisioned on the SSM. Use the no ssm enable feature configuration
mode CLI command to disable these features.
– The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld
CLI command to determine your EPLD version. Refer to the Cisco MDS 9000 Family Release
Notes for Cisco MDS 9000 EPLD Images to upgrade your EPLD image.
– Refer to the Cisco MDS Storage Services Module Interoperability Support Matrix and to the
“Managing Modules” chapter in the Cisco MDS 9000 Family CLI Configuration Guide,
Release 3.x for information on downgrading your SSM.
New Features in Cisco MDS SAN-OS Release 3.1(3)
This section briefly describes the new features introduced in this release. For detailed information about
the features listed, refer to the Cisco MDS 9000 Family CLI Configuration Guide and the Cisco MDS
9000 Family Fabric Manager Configuration Guide.
Table 7 FICON Downgrade Path from SAN-OS 3.1(3)
To SAN-OS Release with FICON Enabled Downgrade Path
SAN-OS 3.0(2) You can nondisruptively downgrade directly from SAN-OS Release 3.1(3).
SAN-OS 2.0(2b) Use the interface shutdown command to administratively shut any Fibre
Channel ports on Generation 1 modules that are in an operationally down
state before nondisruptively downgrading from SAN-OS Release 3.1(3) to
SAN-OS Release 3.0(2), and then to SAN-OS Release 2.0(2b). An
operationally down state includes Link failure or not-connected, SFP
not present, or Error Disabled status in the output of a show interface
command. When an interface is administratively shut it will then show as
Administratively down. Interfaces that are currently up or trunking do not
need to be shut down.
SAN-OS 1.3(4a) Downgrade to SAN-OS Release 3.0(2). Use the shutdown command to shut
all the ports operationally down and administratively up on all the
Generation 1 modules before nondisruptively downgrading to Release
2.0(2b) and then downgrade to 1.3(4a).