Cisco AJ732A - MDS 9134 Fabric Switch Instruction Manual

Send documentation comments to mdsfeedbac[email protected]
Americas Headquarters:
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.3(2)
Release Date: November 11, 2008
Part Number: OL-14116-10 C0
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 56.
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/ps5989/prod_release_notes_list.html
Table 1 shows the online change history for this document.
Contents
This document includes the following sections:
•Introduction, page 2
•Components Supported, page 2
•Software Download Process, page 8
•Upgrading Your Cisco MDS SAN-OS Software Image, page 11
Table 1 Online History Change
Revision Date Description
A0 11/11/2008 Created release notes.
B0 11/12/2008 Added DDTS CSCsr89410 and CSCsr92585.
C0 11/14/2008 Added DDTS CSCso72230.
Corrected the DDTS number of CSCsm32705.

Send documentation comments to mdsfeedbac[email protected]
2
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Introduction
•Downgrading Your Cisco MDS SAN-OS Software Image, page 23
•New Features in Cisco MDS SAN-OS Release 3.3(2), page 26
•Limitations and Restrictions, page 27
•Caveats, page 29
•Related Documentation, page 56
•Obtaining Documentation and Submitting a Service Request, page 57
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 2 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 2 Cisco MDS 9000 Family Supported Software and Hardware Components
Component Part Number Description Applicable Product
Software M95S2K9-3.3.2 MDS 9500 Supervisor/Fabric-2, SAN-OS software. MDS 9500 Series only
M95S1K9-3.3.2 MDS 9500 Supervisor/Fabric-I, SAN-OS software. MDS 9500 Series only
M92S2K9-3.3.2 MDS 9222 Supervisor/Fabric-2, SAN-OS software. MDS 9200 Series only
M92S1K9-3.3.2 MDS 9216 Supervisor/Fabric-I, SAN-OS software. MDS 9200 Series only
M91S2K9-3.3.2 MDS 9100 Supervisor/Fabric-2, SAN-OS software. MDS 9100 Series only
M91S1K9-3.3.2 MDS 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.3(2)
OL-14116-10
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
M9100FIC1EK9 FICON license. 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
Table 2 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.3(2)
OL-14116-10
Components Supported
License 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
M9500EXT1AK9 SAN Extension over IP package for MSM-18/4 module or
MSFM-18/4 FIPS module.
MDS 9500 Series
M9200EXT1AK9 SAN Extension over IP package for MSM-18/4 module or
MSFM-18/4 FIPS module.
MDS 9200 Series
M9500SSE1K9 Storage Services Enabler package. MDS 9500 Series with
SSM
M9200SSE1K9 Storage Services Enabler package. MDS 9200 Series with
SSM
M9500SME1MK9 Cisco Storage Media Encryption package for MSM-18/4
module
MDS 9500 Series with
MSM
M9200SME1MK9 Cisco Storage Media Encryption package for MSM-18/4
module
MDS 9200 Series with
MSM
M9200SME1FK9 Cisco Storage Media Encryption package for fixed slot MDS 9222i Switch only
M95DMMS1K9 Data Mobility Manager (DMM) MDS 9500 Series with
SSM
M92DMMS1K9 Data Mobility Manager (DMM) MDS 9200 Series with
SSM
M95DMMTS1K9 Data Mobility Manager (DMM) for 180 days MDS 9500 Series with
SSM
M92DMMTS1K9 Data Mobility Manager (DMM) for 180 days MDS 9200 Series with
SSM
M9124PL8-4G On-Demand Ports Activation License MDS 9124 Switch
M9134PL8-4G On-Demand Ports Activation License MDS 9134 Switch
M9134PL2-10G On-Demand Ports Activation License MDS 9134 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 Cisco Fabric Switch for
IBM BladeCenter only
Table 2 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.3(2)
OL-14116-10
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 Switch 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 Switch 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 Switch only
DS-C9222i-K9 MDS 9222i Multiservice Modular Switch (includes 18
4-Gbps Fibre Channel ports and 4 Gigabit Ethernet IP
storage services ports, and a modular expansion slot for
Cisco MDS 9000 Family Switching and Service modules.)
MDS 9222i Switch 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 Switch 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 Switch
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 Switch only
DS-C9140-K9 MDS 9140 fixed configuration (non-modular) fabric
switch (includes 8 full rate ports and 32 host-optimized
ports).
MDS 9140 Switch 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 Switch only
DS-C9134-K9 MDS 9134 fixed configuration (non-modular) multilayer
fabric switch (includes 24 enabled 4-Gbps ports; an
on-demand ports activation license can enable 8 additional
ports, up to 32 4-Gbps ports. An additional port activation
license can enable 2 10-Gbps ports.).
MDS 9134 Switch only
DS-C9120-K9 MDS 9120 fixed configuration, non-modular, fabric
switch (includes4 full rate ports and 16 host-optimized
ports).
MDS 9120 Switch 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)
Cisco Fabric Switch for
IBM BladeCenter only
Table 2 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.3(2)
OL-14116-10
Components Supported
External
crossbar
module
DS-13SLT-FAB1 MDS 9513 crossbar fabric module. MDS 9513 Switch 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.
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 Switch
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 Switch
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 Switch
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 Switch
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.
DS-X9304-18K9 18-port Fibre Channel/4-port Gigabit Ethernet
Multiservice (MSM-18/4) module.
DS-X9304-18FK9 18-port Fibre Channel/4-port Gigabit Ethernet
Multiservice FIPS (MSFM-18/4) 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 Switch
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).
DS-X2-E10G-SR X2/SC optics, 10-Gbps Ethernet for Short Reach
DS-X2-FC10G_CX4 X2/CX-4 optics, 10-Gbps Fibre Channel, copper
Table 2 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.3(2)
OL-14116-10
Components Supported
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 Switch
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.
CWDM2DS-CWDM-xxxx Gigabit Ethernet and 1-Gbps/2-Gbps/4-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-FLD51M 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 M90FMK9-CD322= 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 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)
Component Part Number Description Applicable Product

Send documentation comments to mdsfeedbac[email protected]
8
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
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 8
•Downloading Software, page 8
•Selecting the Correct Software Image for an MDS 9200 Series Switch, page 9
•Migrating from Supervisor-1 Modules to Supervisor-2 Modules, page 10
•Configuring Generation 2 Switching Modules, page 10
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.

Send documentation comments to mdsfeedbac[email protected]
9
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Software Download Process
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 mds-softwa[email protected].
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 3.
Selecting the Correct Software Image for an MDS 9200 Series Switch
The system and kickstart image that you use for an MDS 9200 series switch depends on which switch
you use, as shown in Table 4.
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 5.
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:
Table 3 Software Images for MDS 9100 Series Switch
Switch Image
MDS 9120 or MDS 9140 Filename begins with m9100-s1ek9
MDS 9134, MDS 9124, Cisco Fabric Switch for
HP BladeSystem, or Cisco Fabric Switch for IBM
BladeCenter
Filename begins with m9100-s2ek9
Table 4 Software Images for MDS 9200 Series Switches
Switch Image
MDS 9222i Filename begins with m9200-s2ek9
MDS 9216A or MDS 9216i Filename begins with m9200-ek9
Table 5 Software Images 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]
10
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Software Download Process
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
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 the Configuring Generation 2
Switching Modules chapter in the the Cisco MDS 9000 Family CLI Configuration Guide.
For information on port index availability, refer to the “Port Index Availability” section in the Product
Overview chapter of the Cisco MDS 9500 Series Hardware Installation Guide.
For information on Cisco MDS 9000 hardware and software compatibility, refer to the Cisco MDS 9000
SAN-OS Hardware and Software Compatibility Information.

Send documentation comments to mdsfeedbac[email protected]
11
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
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 11
•Upgrading with IVR Enabled, page 18
•Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.3(2), page 20
•Upgrading the SSI Image on Your SSM, page 21
•Upgrading a Switch with Insufficient Space for Two Images on the Bootflash, page 21
•Upgrading a Cisco MDS 9124 Switch, page 22
•Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch, page 23
Upgrading Your Version of Cisco Fabric Manager
As of Cisco SAN-OS Release 3.2(1), Cisco Fabric Manager is no longer packaged with a Cisco MDS 9000
Family switch. It is included on the CD-ROM that ships with the switch. You can install Fabric Manager from
the CD-ROM or from files that you download.
Installing Cisco Fabric Manager is a multi-step process that involves installing a database, as well as Fabric
Manager. The complete installation instructions are provided in the “Installation of Cisco MDS SAN-OS and
Fabric Manager” section in the Cisco MDS 9000 Family Fabric Manager Configuration Guide, and are
available on-screen once you launch the Fabric Manager installer from the CD-ROM.
Note When upgrading Fabric Manager, refer to the supported upgrade path shown in Table 6. For example,
when upgrading from SAN-OS Release 3.1(x) to Release 3.3(2), you will need to upgrade from Release
3.1(x) to Release 3.2(x) and then upgrade to Release 3.3(2).
Note Fabric Manager Server can not be installed on an Active Directory Server when using PostgreSQL,
Fabric Manager servers are domain controllers and can not create local PostgreSQL user accounts.
Table 6 Supported Fabric Manager Upgrade Paths
Current Upgrade Path
3.0.x 3.1.x
3.1.x (HSQL) 3.2.x (Oracle)
3.1.x (HSQL) 3.2.x PostgreSQL
3.1.x (Oracle) 3.2.x (Oracle)
3.2.x (Oracle) 3.3.x (Oracle
3.2.x (PostgreSQL) 3.3.x (PostgreSQL)

Send documentation comments to mdsfeedbac[email protected]
12
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
Upgrading from Release 3.1(2c) with the PostgreSQL Patch
To upgrade Fabric Manager to Release 3.3(2) from the UBS special version of 3.1.2c with the PostgreSQL
patch, do the following:
Step 1 Upgrade Fabric Manager to Release 3.2(1b), pointing to the same PostgreSQL database which was used
by Release 3.1.2c.
Step 2 When the installation is complete, stop the Fabric Manager server.
Step 3 Run PM.sh s located in $InstallDir/bin to re-index the rrd files in the PostgreSQL database.
Step 4 Upgrade Fabric Manager to Release 3.3(2) by running the Release 3.3(2) installer.
Step 5 Discover the fabric again.
Step 6 Add the fabric back into the PM collection. This starts the PM collection.
The Fabric Manager Installation Process Overview
The following section presents the flow of the installation process at a high level. Review these guidelines
before you begin the installation process.
1. Verify supported software. Cisco Fabric Manager has been tested with the following software:
•Windows 2000 SP4, 2003 SP2, XP SP2
•Redhat Linux (2.6 Kernel)
•Solaris (SPARC) 8 and 10
•VMWare Server 1.0:
– Base Operating System: Windows 2000 SP4 / Virtual Operating System: Windows XP SP2
– Base Operating System: Windows 2000 SP4 / Virtual Operating System: Windows 2000 SP4
•Java Sun JRE and JDK 1.5(x) and JRE 1.6 are supported
•Java Web Start 1.2, 1.0.1, 1.5, 1.6
•Firefox 1.5 and 2.0
•Internet Explorer 6.x, and 7.0
Note Internet Explorer 7.0 is not supported on Windows 2000 SP4.
•Oracle Database 10g Express
•PostgreSQL 8.2 (Windows and Linux)
•PostgreSQL 8.1 (Solaris)
•Cisco ACS 3.1 and 4.0
•PIX Firewall
•IP Tables
•SSH v2
•Global Enforce SNMP Privacy Encryption
•HTTPS

Send documentation comments to mdsfeedbac[email protected]
13
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
2. Ensure data migration when upgrading Cisco Fabric Manager from Cisco SAN-OS Releases 3.1(2b)
and later.
If you are upgrading Cisco Fabric Manager in Cisco SAN-OS Releases 3.1(2b) and later, be aware
that data is migrated from the Hypersonic HSQL database to either the PostgreSQL database or
Oracle Database 10g Express during the installation. Data is also migrated from Oracle Database
10g Express to Oracle Database 10g Express. If you migrate the database from Oracle to Oracle, the
schema is updated. Refer to Table 6 for information on the supported upgrade path.
3. Ensure data migration when upgrading Cisco Fabric Manager from releases prior to Cisco SAN-OS
Releases 3.1(2b).
If you are upgrading Fabric Manager in a Cisco SAN-OS Release prior to 3.1(2b), be aware that data
is migrated from the Hypersonic HSQL database to either the PostgreSQL database or the Oracle
Database 10g Express during the installation. The Fabric Manager Installer installs the PostgreSQL
database on Windows. If you want to install the PostgreSQL database on Solaris or Linux, or if you
want to install the Oracle Database 10g Express database, follow the instructions in the “Installation
of Cisco MDS SAN-OS and Fabric Manager” section in the Cisco MDS 9000 Family Fabric Manager
Configuration Guide. Refer to Table 6 for information on the supported upgrade path.
4. If you are upgrading a previous installation of Fabric Manager, make sure the previous installation
is installed and running. Do not uninstall the previous version. If the previous version is uninstalled,
the database will not be migrated and your server settings will not be preserved.
5. Select the database.
If you want to use the Oracle Database 10g Express, you must install the database and create a user
name and password before continuing with the Fabric Manager installation. We recommend the
Oracle Database 10g Express option for all users who are running Performance Manager on large
fabrics (1000 or more end devices).
If you want to install the PostgreSQL database, you must disable any security software you are
running as PostgreSQL may not install certain folders or users. You must also log in as a Superuser
before you start the installation.
6. Install Fabric Manager from the CD-ROM or from files that you download from Cisco.com at the
following website:
http://cisco.com/cgi-bin/tablebuild.pl/mds-fm
Installing Fabric Manager on Solaris
This section describes how to install Fabric Manager on Solaris.
To install Fabric Manager on Solaris, follow these steps:
Step 1 Set Java 1.5 or 1.6 to the path that is to be used for installing Fabric Manager.
Step 2 Install the database that is to be used with Fabric Manager.
Step 3 Copy the Fabric Manager jar file m9000-fm-3.3.1c.jar from the CD-ROM to a folder on the Solaris
workstation.
Step 4 Launch the installer using the following command:
java -Xms512m -Xmx512m -jar m9000-fm-3.3.1c.jar
Step 5 Follow the onscreen instructions provided in the Fabric Manager management software setup wizard.

Send documentation comments to mdsfeedbac[email protected]
14
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
Installing Fabric Manager on Windows
This section describes how to install Fabric Manager on Windows.
Note Fabric Manager Server can not be installed on an Active Directory Server when using PostgreSQL,
Fabric Manager servers are domain controllers and can not create local PostgreSQL user accounts.
If your server is running Terminal Services in Application mode, or if you are running Citrix Metaframe
or any variation thereof, you need to issue the following command on the DOS prompt before installing
Fabric Manager Server.
1. Open a command-line prompt: Start > Run, then type cmd and press Return.
2. At the command prompt type: user /install.
Note Do not close the command line window. This must remain open for the entire duration
of the install.
The following is an example of the output of this command:
C:\Documents and Settings\user.domain>USER /INSTALL
User session is ready to install applications.
3. Follow all steps needed to install Fabric Manager, Fabric Manager Server, and Device Manager.
See the instructions later in this section.
4. When the installation is complete, at the command prompt, type user /execute and press
Return. Then type exit and press Return.
The following is an example of the output of this command:
C:\Documents and Settings\user.domain>USER /execute
User session is ready to execute applications.
To install Fabric Manager on Windows, follow these steps:
Step 1 Click the Install Management Software link.
Step 2 Choose Management Software > Cisco Fabric Manager.
Step 3 Click the Installing Fabric Manager link.
Step 4 Select the drive for your CD-ROM.
Step 5 Click the FM Installer link.
Step 6 Follow the onscreen instructions provided in the Fabric Manager Installer 3.3(2).
To install Device Manager on your workstation, follow these steps:
Step 1 Enter the IP address of the switch in the Address field of your browser.
Step 2 Click the Cisco Device Manager link in the Device Manager installation window.
Step 3 Click Next to begin the installation.

Send documentation comments to mdsfeedbac[email protected]
15
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
Step 4 Follow the onscreen instructions to complete the installation of Device Manager.
Note If you use a Java JDK instead of a JRE on Solaris, you might encounter a problem trying to install the
Device Manager from a web browser. This can happen because the installer heap limit of 256 MB is not
sufficient. If you have this problem, save the jnlp link as file, increase the heap limit to 512 MB, and run
javaws element-manager.jnlp at the shell prompt.
General Upgrading Guidelines
Use the following guidelines when upgrading to Cisco MDS SAN-OS Release 3.3(2):
•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 22.
•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 23.
•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 7 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. This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module,
the MSM-18/4 module, and the MDS 9222i switch. 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.
– Inter-VSAN Routing (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 18 for these instructions.
– FICON: If you have FICON enabled, the upgrade path is different. See Table 8.
Use Table 7 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.3(2). Find the
image release number you are currently using in the Current column of the table and use the path
recommended.
Note On an MDS 9222i switch, an upgrade from SAN-OS Release 3.2(x), Release 3.3(1a), or Release 3.3(1c)
to SAN-OS Release 3.3(2) fails when there is an active FC-Redirect configuration (created by Cisco
SME or Cisco DMM applications) on the switch. An active FC-Redirect configuration is defined as:

Send documentation comments to mdsfeedbac[email protected]
16
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
•FC-Redirect configuration for hosts or target connected locally
•FC-Redirect configuration created by application running on that switch.
If an upgrade is attempted when an active configurations is present, the switch will go into a disruptive
upgrade.
Note The software upgrade information in Table 7 applies only to Fibre Channel switching traffic. Upgrading
system software disrupts IP traffic and SSM intelligent services traffic.
Table 7 Nondisruptive Upgrade Path to SAN-OS Release 3.3(2)
Current Nondisruptive Upgrade Path
SAN-OS 3.3(1c) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.3(1a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.2(3a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.2(3) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.2(2c) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.2(1a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.1(4) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.1(3a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.1(2b) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.1(2a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.1(2) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.1(1) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.0(3a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.0(3) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.0(2a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.0(2) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.0(1) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 2.1(3) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 2.1(2e) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 2.1(2d) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 2.1(2b) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 2.1(2) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.3(2).

Send documentation comments to mdsfeedbac[email protected]
17
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
Use Table 8 to determine your FICON nondisruptive upgrade path to Cisco MDS SAN-OS Release
3.3(2). 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.
SAN-OS 2.1(1b) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.3(2).
SAN-OS 2.1(1a) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.3(2).
SAN-OS 2.0(x) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.3(2).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.3(2).
SAN-OS 1.x Upgrade to SAN-OS Release 1.3(4a), then to Release 2.1(2b), and then upgrade to
Release 3.3(2).
Table 7 Nondisruptive Upgrade Path to SAN-OS Release 3.3(2) (continued)
Current Nondisruptive Upgrade Path
Table 8 FICON Nondisruptive Upgrade Path to SAN-OS 3.3(2)
Current Release with
FICON Enabled Upgrade Path
SAN-OS 3.0(3b) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).
SAN-OS 3.0(2) You can nondisruptively upgrade directly to SAN-OS Release 3.3(2).

Send documentation comments to mdsfeedbac[email protected]
18
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
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); you must upgrade to Release 2.1(2b) before
upgrading to Release 3.3(2). 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 11.
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.
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.
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) or SAN-OS Release 3.0(3b), and then upgrade to
Release 3.3(2). 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).
Table 8 FICON Nondisruptive Upgrade Path to SAN-OS 3.3(2)
Current Release with
FICON Enabled Upgrade Path

Send documentation comments to mdsfeedbac[email protected]
19
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
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.3(2).
Note RDI mode should not be disabled for VSANs running in interop mode 2 or interop mode 3.

Send documentation comments to mdsfeedbac[email protected]
20
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Upgrading Your Cisco MDS SAN-OS Software Image
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.3(2)
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.3(2).
For more information on upgrading SAN-OS software, see the “Upgrading Your Cisco MDS SAN-OS
Software Image” section on page 11.
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
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