|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.3(5)Determining the Software Version
Determining Software Version Compatibility
Selecting the Correct Software Image for an MDS 9100 Series Switch
Selecting the Correct Software Image for an MDS 9200 Series Switch
Selecting the Correct Software Image for an MDS 9500 Series Switch
Migrating from Supervisor-1 Modules to Supervisor-2 Modules
Configuring Generation 2 Switching Modules
Upgrading Your Cisco MDS SAN-OS Software Image
Upgrading Your Version of Cisco Fabric Manager
Upgrading from Release 3.1(2c) with the PostgreSQL Patch
The Fabric Manager Installation Process Overview
FICON Supported Releases and Upgrade Paths
Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.3(5)
Upgrading the SSI Image on Your SSM
Upgrading a Switch with Insufficient Space for Two Images on the Bootflash
Upgrading a Cisco MDS 9124 Switch
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Downgrading Your Cisco MDS SAN-OS Software Image
General Downgrading Guidelines
Downgrading the SSI Image on Your SSM
Downgrading an MDS 9222i Switch
New Features in Cisco MDS SAN-OS Release 3.3(5)
Upgrading to Recover Loss of Performance Manager Data
Maximum Number of Zones Supported in Interop Mode 4
Upgrading the SAN-OS Software on the MDS 9222i Switch
Cisco Storage Media Encryption
Cisco SME Configuration Limits
Cisco MDS 9222i Module Upgrade
Deleting SANTap Configurations Is Required Before Downgrade
Applying Zone Configurations to VSAN 1
Running Storage Applications on the MSM-18/4
Compatibility of Fabric Manager and Data Mobility Manager
A Supervisor-2 Module Might Reset in Switches Running SAN-OS Release 3.2(x)
Limited ISSU Support on the MDS 9222i Switch
PPRC Not Supported with FCIP Write Acceleration
Using IVR In a Fabric With Mixed Code Versions
HTTP Transport Method Not Supported in Call Home
Regulatory Compliance and Safety Information
Intelligent Storage Networking Services
Installation and Configuration Note
Obtaining Documentation and Submitting a Service Request
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.3(5)
Release Date: April 6, 2010
Part Number: OL-14116-14 F0
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.
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 on-line change history for this document.
Table 1 Online History Change
Revision Date DescriptionA0
04/06/2010
Created release notes.
B0
06/11/2010
Corrected the description of the limitation "A Supervisor-2 Module Might Reset in Switches Running SAN-OS Release 3.2(x)".
C0
07/29/2010
Added the "PPRC Not Supported with FCIP Write Acceleration" limitation.
Added the "Using IVR In a Fabric With Mixed Code Versions" limitation.
D0
11/03/2010
Added the Supervisor-2A module to Table 2.
E0
04/29/2011
Added DDTS CSCto68011.
F0
11/29/2011
Updated the "Nondisruptive Upgrade Path to Cisco MDS SAN-OS Release 3.3(5)" table.
Updated "Nondisruptive Downgrade Path from Cisco MDS SAN-OS Release 3.3(5)" table.
Added the "HTTP Transport Method Not Supported in Call Home" limitation.
Contents
This document includes the following sections:
•Upgrading Your Cisco MDS SAN-OS Software Image
•Downgrading Your Cisco MDS SAN-OS Software Image
•New Features in Cisco MDS SAN-OS Release 3.3(5)
•Obtaining Documentation and Submitting a Service Request
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 ProductSoftware
M95S2K9-3.3.5
MDS 9500 Supervisor/Fabric-2, SAN-OS software.
MDS 9500 Series only
M95S1K9-3.3.5
MDS 9500 Supervisor/Fabric-I, SAN-OS software.
MDS 9500 Series only
M92S2K9-3.3.5
MDS 9222 Supervisor/Fabric-2, SAN-OS software.
MDS 9200 Series only
M92S1K9-3.3.5
MDS 9216 Supervisor/Fabric-I, SAN-OS software.
MDS 9200 Series only
M91S2K9-3.3.5
MDS 9100 Supervisor/Fabric-2, SAN-OS software.
MDS 9100 Series only
M91S1K9-3.3.5
MDS 9100 Supervisor/Fabric-I, SAN-OS software.
MDS 9100 Series only
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
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
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—SFPs1 sold 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
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-SF2A-K9
MDS 9500 Supervisor-2A module.
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
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.
CWDM2
DS-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-W3 AC 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
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
•Determining Software Version Compatibility
•Selecting the Correct Software Image for an MDS 9200 Series Switch
•Migrating from Supervisor-1 Modules to Supervisor-2 Modules
•Configuring Generation 2 Switching Modules
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.
Determining Software Version Compatibility
Table 3 lists the software versions that are compatible in a mixed SAN environment, and the minimum software versions that are supported. We recommend that you use the latest 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 rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive resetAt 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 mds-software-disclosure@cisco.com.
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 4.
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 5.
Table 5 Software Images for MDS 9200 Series Switches
Switch ImageMDS 9222i
Filename begins with m9200-s2ek9
MDS 9216A or MDS 9216i
Filename begins with m9200-ek9
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 6.
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-standbyFor 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-standbyMigrating 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 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.
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
•FICON Supported Releases and Upgrade Paths
•Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.3(5)
•Upgrading the SSI Image on Your SSM
•Upgrading a Switch with Insufficient Space for Two Images on the Bootflash
•Upgrading a Cisco MDS 9124 Switch
•Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
•Upgrading an MDS 9222i Switch
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 7. For example, when upgrading from SAN-OS Release 3.1(x) to Release 3.3(5), you will need to upgrade from Release 3.1(x) to Release 3.2(x) to Release 3.3(x), and then upgrade to Release 3.3(5).
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.
Upgrading from Release 3.1(2c) with the PostgreSQL Patch
To upgrade Fabric Manager to Release 3.3(5) 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(5) by running the Release 3.3(5) 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 and Device Manager have 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
Note Do not use Java 1.6 Update 13.
•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
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 7 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 7 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.5.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.5.jar
Step 5 Follow the onscreen instructions provided in the Fabric Manager management software setup wizard.
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.
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.
Note If you are running Fabric Manager Server on Windows and using the PostgreSQL database, you should examine your Windows Active Directory environment for organizational units (OUs) and make the change recommended below to ensure that Fabric Manager Server does not periodically stop working.
On a Windows system, the Microsoft Active Directory applies a Group Policy Object (GPO) to the Fabric Manager Server. The GPO does not recognize the local user PostgreSQL because it is not in the GPO allow list. As a result, the GPO removes it, and the PostgreSQL database stops working.
To avoid this situation, you should move the Fabric Manager Server to its own OU and apply the same feature settings as the original OU, but remove the local user account to log in as a service.
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 /INSTALLUser 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 /executeUser 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(5).
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.
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(5):
•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.
•Follow the guidelines for upgrading a single supervisor switch as described in "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch" section.
•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 8 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 for these instructions.
–FICON: If you have FICON enabled, the upgrade path is different. See the "FICON Supported Releases and Upgrade Paths" section.
Use Table 8 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.3(5). 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(5) 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:
•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 8 applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and SSM intelligent services traffic.
FICON Supported Releases and Upgrade Paths
Cisco MDS SAN-OS Release 3.3(5) does not support FICON.
Table 9 lists the SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes for FICON upgrade path information.
Table 9 FICON Supported Releases
FICON Supported ReleasesNX-OS
Release 4.2(1b)
Release 4.1(1c)
SAN-OS
Release 3.3(1c)
Release 3.2(2c)
Release 3.0(3b)
Release 3.0(3)
Release 3.0(2)
Release 2.0(2b)
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(4). 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. 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.
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 interfaceport-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 suspendswitch(config-vsan-db)# no vsan vsan-id suspendStep 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(5).
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.3(5)
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(5).
For more information on upgrading SAN-OS software, see the "Upgrading Your Cisco MDS SAN-OS Software Image" section.
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 upHardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)Port WWN is 20:4b:00:0d:ec:09:3c:00Admin port mode is auto <-------- shows port is configured in auto mode
snmp traps are enabledPort mode is F, FCID is 0xef0300 <-------- shows current port operational mode is F
Port vsan is 1Speed is 2 GbpsTransmit B2B Credit is 3Step 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 NX-OS Release Compatibility Matrix for Storage Service Interface Images.
–All SSM applications are disabled. Use the show ssm provisioning command to determine what applications are configured. Use the no ssm enable feature command to disable these applications.
–No SSM ports are in auto mode. See the "Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.3(5)" section.
–The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld 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 Data Center 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.
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.3(5) 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 8, 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(2) or earlier version to SAN-OS Release 3.3(5), 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.
Upgrading an MDS 9222i Switch
If you are running SAN-OS Release 3.3(5) on an MDS 9222i switch and you want to upgrade to an NX-OS 4.x release, you can upgrade to release 4.1(3a) and higher. Do not attempt to upgrade an MDS 9222i switch from SAN-OS 3.3(5) to NX-OS 4.1(1x) (including 4.1(1b) and 4.1(1c)) because the upgrade path is not supported on the MDS 9222i. This restriction does not apply to other platforms.
Before upgrading, issue the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive.
Following the upgrade, you may need to enable features with the feature feature-name command, such as the feature iscsi command. In SAN-OS 3.3(x) release, features are enabled with the feature-name enable command, such as the iscsi enable command.
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
•Downgrading the SSI Image on Your SSM
•Downgrading an MDS 9222i Switch
General Downgrading Guidelines
Use the following guidelines to nondisruptively downgrade your Cisco MDS SAN-OS Release 3.3(5):
•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 10 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, 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 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, MPS-14/2 module, MSM-18/4 module, or the MDS 9222i switch is online. 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 for these instructions.
–FICON: If you have FICON enabled, the downgrade path is different. See the "FICON Downgrade Paths" section.
Use Table 10 to determine the nondisruptive downgrade path from Cisco SAN-OS Release 3.3(5). 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 10 applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP and SSM intelligent services traffic.
FICON Downgrade Paths
Cisco MDS SAN-OS Release 3.3(5) does not support FICON.
Refer to Table 9 for a list SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes for FICON downgrade path information.
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.3(5) 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 NX-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 command to determine if any applications are provisioned on the SSM. Use the no ssm enable feature configuration mode command to disable these features.
–The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld 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 Data Center Interoperability Support Matrix and the "Managing Modules" chapter in the Cisco MDS 9000 Family CLI Configuration Guide, Release 3.x, for information on downgrading your SSM.
Downgrading an MDS 9222i Switch
If you are running MDS NX-OS 4.1(1x) on an MDS 9222i switch and you need to downgrade to a SAN-OS 3.3(x) release, you can downgrade to Release 3.3(2), 3.3(1c), or 3.3(1a), but you cannot downgrade to 3.3(5). A nondisruptive downgrade from NX-OS 4.1(1x) to SAN-OS 3.3(5) is not supported on the MDS 9222i switch. This restriction does not apply to other platforms.
Before downgrading, disable all features not supported by the downgrade release. Use the show incompatibility system downgrade-image CLI command to determine what features you need to disable.
Following the downgrade, you will need to enable features with the feature-name enable command, such as the iscsi enable command. In NX-OS 4.1(x) releases, features are enabled with the feature feature-name command, such as the feature iscsi command.
New Features in Cisco MDS SAN-OS Release 3.3(5)
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, Release 3.x, the Cisco MDS 9000 Family Fabric Manager Configuration Guide, and the Cisco MDS 9000 Family Storage Media Encryption Configuration Guide. For information about new CLI commands associated with these features, refer to the Cisco MDS 9000 Family Command Reference. The "New and Changed Information" section in each of these books provides a detailed list of all new features and includes links to the feature description or new command.
Note These release notes are specific to this release. For the complete Release 3.x documentation set, see the "Related Documentation" section.
There are no new features in Cisco MDS SAN-OS Release 3.3(5).
Limitations and Restrictions
This section lists the limitations and restrictions for this release. This section includes the following topics:
•Upgrading to Recover Loss of Performance Manager Data
•Maximum Number of Zones Supported in Interop Mode 4
•Upgrading the SAN-OS Software on the MDS 9222i Switch
•Cisco Storage Media Encryption
•Cisco MDS 9222i Module Upgrade
•Deleting SANTap Configurations Is Required Before Downgrade
•Applying Zone Configurations to VSAN 1
•Running Storage Applications on the MSM-18/4
•Compatibility of Fabric Manager and Data Mobility Manager
•A Supervisor-2 Module Might Reset in Switches Running SAN-OS Release 3.2(x)
•Limited ISSU Support on the MDS 9222i Switch
•PPRC Not Supported with FCIP Write Acceleration
•Using IVR In a Fabric With Mixed Code Versions
•HTTP Transport Method Not Supported in Call Home
Upgrading to Recover Loss of Performance Manager Data
Caution You must upgrade to Fabric Manager Release 3.1(x) and then upgrade to a later release of Fabric Manager to avoid losing Performance Manager data. If data has been lost, follow the steps below to recover the data.
Step 1 Disable Performance Manager interpolation using Fabric Manager Web Client. Uncheck Interpolate missing statistics, then click Apply.
Step 2 Stop the Fabric Manager Server.
Step 3 Save the data file in the $INSTALL_DIR directory.
Step 4 Move the old RRD file into the $INSTALL_DIR/pm/db directory.
Step 5 Run $INSTALL_DIR/bin/pm.bat m.
Step 6 Restart Fabric Manager Server.
Maximum Number of Zones Supported in Interop Mode 4
In interop mode 4, the maximum number of zones that is supported in an active zone set is 2047, due to limitations in the connected vendor switch.
When IVR is used in interop mode 4, the maximum number of zones supported, including IVR zones, in the active zone set is 2047.
Upgrading the SAN-OS Software on the MDS 9222i Switch
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(5) 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:
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.
Java Web Start
When using Java Web Start, it is recommended that you do not use an HTML cache or proxy server. You can use the Java Web Start Preferences panel to view or edit the proxy configuration. To do this, launch the Application Manager, either by clicking the desktop icon (Microsoft Windows), or type ./javaws in the Java Web Start installation directory (Solaris Operating Environment and Linux), and then select Edit>Preferences.
If you fail to change these settings, you may encounter installation issues regarding a version mismatch. If this occurs, you should clear your Java cache and retry.
Cisco Storage Media Encryption
The following limitations are described for Cisco SME:
•Cisco SME Configuration Limits
•Deleting Cisco SME Interfaces
Cisco SME Configuration Limits
Table 11 lists the Cisco SME configuration limits for this release.
Deleting Cisco SME Interfaces
A Cisco SME interface can be deleted from the cluster only after the interface is administratively shut-down and all related tasks associated with the interface shut-down are complete.
Emulex Driver Version
In some instances, the Emulex driver version 8.1.10.9 may set the task attribute to HEAD_OF_QUEUE instead of SIMPLE_QUEUE. Certain tape drives do not accept this attribute and may reject these commands. The Emulex driver version 8.1.10.12 does not have this issue.
Cisco MDS 9222i Module Upgrade
On the MDS 9222i module, an upgrade from SAN-OS Release 3.2(x) to Release 3.3(1c) is not supported if there is a Cisco SME or Cisco DMM configuration in the fabric for hosts and targets attached to the MDS 9222i module.
SANTap
The SANTap feature allows third party data storage applications, such as long distance replication and continuous backup, to be integrated into the SAN.
Deleting SANTap Configurations Is Required Before Downgrade
If you are running Cisco MDS NX-OS Release 4.1(1b) in combination with the SSI 4.1(1b) image and you wish to downgrade to Cisco SAN-OS Release 3.3(5) and an SSI 3.2(3*) image, you must delete all SANTap configurations prior to the downgrade. Downgrading without completely deleting the SANTap configurations is not supported.
FCIP Interoperability
FCIP interoperability fails between two MDS switches, one running MDS NX-OS Release 4.1(1c) and the other running MDS SAN-OS Release 3.3(5), if the IP ACL configuration for an IPsec crypto map specifies TCP as the protocol, as in the following example:
switch(config)# ip access-list acl-name permit tcp local-gige-ip-address local-mask remote-gige-ipaddress remote-mask
FCIP interoperability does not fail if the IP ACL uses IP as the protocol, as in the following example:
switch(config)# ip access-list acl-name permit ip local-gige-ip-address local-mask remote-gige-ipaddress remote-mask
Applying Zone Configurations to VSAN 1
In the setup script, you can configure system default values for the default-zone to be permit or deny, and you can configure default values for the zone distribution method and for the zone mode.
These default settings are applied when a VSAN is created. However, the settings will not take effect on VSAN 1, because it exists prior to running the setup script. Therefore, when you need these settings for VSAN 1, you must explicitly issue the following commands:
•zone default-zone permit vsan 1
•zoneset distribute full vsan 1
•zone mode enhanced vsan 1
Running Storage Applications on the MSM-18/4
The Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4) does not support multiple, concurrent storage applications. Only one application, such as SME or DMM, can run on the MSM-18/4 at a time.
Compatibility of Fabric Manager and Data Mobility Manager
Cisco Fabric Manager in any MDS NX-OS 4.1(x) release does not support Data Mobility Manager (DMM) in any SAN-OS 3.3(x) release or in any 3.2(x) release. To use the Cisco Fabric Manager GUI for DMM, both Fabric Manager and DMM must be running NX-OS or SAN-OS software from the same release series.
A Supervisor-2 Module Might Reset in Switches Running SAN-OS Release 3.2(x)
An MDS 9000 switch with a Supervisor-2 module might switch over to the standby supervisor module with a reset reason of Kernel Panic. Although there is no workaround for this issue, it happens very rarely. Additional instrumentation and checks have been added to SAN-OS Release 3.3(1c) and later and to NX-OS Release 4.2(x) to ensure that kernel panic does not occur. DDTS CSCsx18173 describes this issue.
Limited ISSU Support on the MDS 9222i Switch
An in-service software upgrade (ISSU) from SAN-OS Release 3.3(5) to NX-OS Release 4.1(1b) or to NX-OS Release 4.1(1c) is not supported on the MDS 9222i switch. This limitation applies only to the MDS 9222i switch. You can perform an ISSU from SAN-OS Release 3.3(5) to NX-OS Release 4.1(1b) or NX-OS Release 4.1(1c) on other MDS switches.
ISSU upgrades from SAN-OS Release 3.3(5) to NX-OS Release 4.1(3a) and to NX-OS Release 4.13(a) are supported on the MDS 9222i switch.
PPRC Not Supported with FCIP Write Acceleration
IBM Peer to Peer Remote Copy (PPRC) is not supported with FCIP Write Acceleration.
Using IVR In a Fabric With Mixed Code Versions
If you are using IVR and you are running SAN-OS 3.x software on your MDS switches, make sure that all IVR switches run the same code version. Otherwise, if you have a fabric with mixed code versions, the switches running the higher version may not be able to see all IVR devices. The mixed fabric can cause an inconsistent database among IVR switches, which might affect IVR behavior. For this reason, it is important that all IVR switches run the same SAN-OS version, preferably SAN-OS Release 3.3(4a), which has device update (DU) support, or later.
HTTP Transport Method Not Supported in Call Home
Cisco SAN-OS Release 3.x does not support the HTTP transport method in the Call Home feature.
Caveats
This section lists the open and resolved caveats for this release. Use Table 12 to determine the status of a particular caveat. In the table, "O" indicates an open caveat and "R" indicates a resolved caveat.
Resolved Caveats
•CSCsu29375
Symptom: On Generation 2 modules, if a port speed is configured as auto 4 Gbps, then the port may stay in the initializing state and may not transition to the up state. In addition, the host does not receive a FLOGI acknowledgement. This symptom may be seen when interfaces are connected to hosts.
Workaround: This issue is resolved.
•CSCsu84919
Symptom: When hosts continuously log into virtual targets, the iSAPI process (VSD) leaks memory which might lead to an SSM failure.
Workaround: This issue is resolved.
•CSCsw38936
Symptom: If you have many port VSAN instances in a configuration, CPU usage may be very high. If you display the configuration, the supervisor module may fail.
Workaround: This issue is resolved.
•CSCsz84411
Symptom: An MDS 9124 switch may randomly reboot with a reset reason of unknown. This is a rare event and occurs only in systems that have a single power supply with a serial number beginning with QCS.
Workaround: This issue is resolved.
•CSCta13451
Symptom: Under certain rare conditions when FCP-2 error recovery procedures are invoked by the host to recover a READ operation, the FCIP or IOA engine may fail.
Workaround: This issue is resolved.
•CSCta22352
Symptom: SNMP failed because it was stuck in a loop waiting for a response from the Performance Manager, and the Performance Manager was stuck waiting for a response from the module. Following the SNMP failure, the switch reloaded.
Workaround: This issue is resolved.
•CSCta67430
Symptom: If a host issues a tape read command with the suppress incorrect-length indicator (SILI) bit set, it is possible for the target to return a good status and not send the full read data length requested in the read command. If this occurs, FCIP tape acceleration can leave the exchange entry in an error recovery state on the FCIP target side, and remove the exchange entry on the FCIP host side. As a result, FCIP loss of sync failure can occur.
Workaround: This issue is resolved.
•CSCtb50701
Symptom: VSD fails because an internal process exceeds its memory limit of 400 MB.
Workaround: This issue is resolved.
•CSCtb91560
Symptom: In some situations, the shrink operation for PSS files of fcdomain takes much longer than expected. Because of this, fcdomain fails due to a heartbeat failure.
Workaround: This issue is resolved.
•CSCtf06321
Symptom: Under certain conditions, when the switch receives a TMF command from the host, cached read exchanges as a part of Tape Read Acceleration are not flushed. This causes an incorrect sequence of data to be sent to the host when the next READ is presented. This in turn causes the exchange to abort.
Workaround: This issue is resolved.
•CSCtf07823
Symptom: On an MDS 9509 switch running SAN-OS Release 3.3(2), the supervisor module reset because of the scheduler service, as shown in the following output:
----- reset reason for Supervisor-module 6 (from Supervisor in slot 6)---1) At 567388 usecs after Thu Feb 11 02:31:59 2010Reason: Reset triggered due to HA policy of ResetService: Service "scheduler"Version: 3.3(2)switch# show cores
Module-num Process-name PID Core-create-time---------- ------------ --- ----------------6 scheduler 32032 Feb 11 02:36Workaround: This issue is resolved.
•CSCso49196
Symptom: During an upgrade from SAN-OS Release 3.2(3a) to Release 3.3(1a), when a switchover occurs to the supervisor running Release 3.3(1a), Cisco SME traffic flows for hosts that are not connected locally to the switch that is getting upgraded, may get flapped for a very short time. This can also occur during a switchover to a supervisor running Release 3.3(1a).
Workaround: None.
•CSCsx31168
Symptom: When activating a zone set with few changes, the zone server incorrectly warns the user that the zone set that is going to be activated is significantly smaller than the current active one. This situation occurs when more IVR zones are present as part of an active zone set.
Workaround: This issue is resolved.
•CSCsz01738
Symptom: A host behind an NPIV F port is unable to see the zoned LUNs if it is added to the zone and the zone set is activated after the ISSU. This symptom may be seen with NPIV F ports on the MDS 9124 and 9134 switches.
Workaround: This issue is resolved.
•CSCsz16768
Symptom: When NPV is enabled, IP access list commands are not accessible.
Workaround: This issue is resolved.
•CSCsz84022
Symptom: The TPC application is unable to discover an MDS 9509 switch when it is connected through an ISL trunk to an MDS 9020 switch.
Workaround: This issue is resolved.
•CSCta28642
Symptom: SNMP cannot gracefully handle interface counter request timeouts and it misses a heartbeat. As a result, the system manager terminates the SNMP process.
Workaround: This issue is resolved.
•CSCta34629
Symptom: Under certain conditions, the system manager core server does not clean up core files This symptom may be seen on an MDS 9513 switch with a Fabric 2 module running SAN-OS Release 3.2(3).
Workaround: This issue is resolved.
•CSCta49151
Symptom: A zone change state machine is stuck in UFC state as the TCAM state machine is stuck in Partial state. This situation can occur when a zoning mode is changed from basic to enhanced and the number of TCAM entries that need to be programmed for any Fibre Channel interface is more than 2500 and less than 5000.
Workaround: This issue is resolved.
•CSCta55819
Symptom: Cisco Fabric Services (CFS) callhome commands are not working in NPV mode, even though CFS is working in NPV mode.
Workaround: This issue is resolved.
•CSCtc03274
Symptom: When the zone server fails the zone check for the host and virtual target, the iSAPI rejects the host's PLOGI request. This situation occurs because of the two-second delay between the PLOGI sent from host to the target and the host port online RSCN. This symptom may be seen when the host goes down and comes back up after a zone set activation, and only when hosts are connected to a McData switch.
Workaround: This issue is resolved.
•CSCtc57553
Symptom: Under normal operating conditions, an association call that relates CISCO_ZoneAlias to CISCO_Vsan fails.
Workaround: This issue is resolved.
•CSCtc73992
Symptom: Under random conditions, the following harmless error message was displayed:
2009 Oct 22 14:48:50 sw-233-27 %KERN-6-SYSTEM_MSG: eth1: egiga: driver bug! interrupt while in poll, netif_running=1, LINK_STATE_RX_SCHED=1
Workaround: This issue is resolved.
•CSCtc86023
Symptom: When the customer enters the install all ssi command to upgrade the SSI image on the SSM module, the ilc_helper command will not run on the standby module because of the install all command. This situation affects SSI functionality if the device switches over to the standby module.
Workaround: This issue is resolved.
•CSCtd79222
Symptom: After executing the following series of commands, the switch reloaded:
–show hardware internal eobc stats
–show hardware internal mgmt0 stats
–show tech
Workaround: This issue is resolved.
•CSCte27874
Symptom: When you check CPU usage, you may notice that is close to 100 percent and it does not decrease. For example, if you enter the show process cpu command, the output shows that the vrrp-engine process is using close to or more than 90 percent of available CPU time:
1675 2215685686 268836864 1565842753 94.3 vrrp-engOccasionally, the vrrp-engine process gets into this state when the supervisor receives VRRP AH packets and the packets are not properly handled.
Workaround: This issue is resolved.
•CSCsw87910
Symptom: When running SAN-OS Release 3.3(2) with DPVM enabled, you may see the following messages in the output of the show logging log command if a link flaps for a DPVM enabled end device.
%DPVM-3-PSS_ERR: Failed to update Login info NPV contextpwwn: 50:00:00:00:aa:99:ee:44, syserr = no such pss keyWorkaround: This issue is resolved.
•CSCte51418
Symptom: Under rare conditions, some hardware error interrupts of ASIC devices on a Generation 2 or Generation 3 module do not bring down the affected ports because of high threshold limits.
Workaround: This issue is resolved.
•CSCsv01884
Symptom: Activating a standard VSAN zone set caused traffic disruption for IVR devices. This situation can occur when an IVR zoneset is active and the standard VSAN zone set is activated from an IVR disabled switch. This problem was fixed by activating a new zone set after adding all the IVR zones from the current active zone set to the new zone set.
Workaround: This issue is resolved.
•CSCtd65873
Symptom: Under rare conditions, some hardware error interrupts of an ASIC device on a Generation 2 or Generation 3 module do not bring down the affected ports because of high threshold limits for the following:
CRC_ERR_FRAMES_DETECTEDNI_QGRP4_P3_BAD_PKTCSUM_ERRTX_PKT_BAD_PARITYWorkaround: This issue is resolved.
Open Caveats
•CSCto68011
Symptom: The fcdomain service on both supervisor modules fails, which results in a reload of the device. An error message similar to the following is displayed:
'' %SYSMGR-2-SERVICE_CRASHED: Service ''fcdomain'' (PID 4688) hasn't caught signal 11 (core will be saved)''This issue affects the following products when they have SNMP configured:
–Cisco MDS 9000 Series Multilayer switches
–Cisco Nexus 5000 Series switches and Cisco Nexus 2000 Series, running in FC switching mode (NPV mode is not affected).
The following products are confirmed not vulnerable:
–Cisco Nexus 7000 Series switches
–Cisco Nexus 4000 Series switches
Workaround: The following workaround is available:
Infrastructure Access Control Lists
Caution Because the feature in this vulnerability uses UDP as a transport, it is possible to spoof the sender's IP address, which may defeat ACLs that permit communication to these ports from trusted IP addresses.
Although it is often difficult to block traffic that transits a network, it is possible to identify traffic that should never be allowed to target infrastructure devices and block that traffic at the border of networks. Infrastructure Access Control Lists (iACLs) are a network security best practice and should be considered as a long-term addition to good network security as well as a workaround for this specific vulnerability. The iACL example below should be included as part of the deployed infrastructure access-list which will protect all devices with IP addresses in the infrastructure IP address range:
!---!--- Feature: SNMP!---!---!--- Permit SNMP traffic from trusted sources.!---ip access-list 150 permit udp TRUSTED_SOURCE_ADDRESSES WILDCARDINFRASTRUCTURE_ADDRESSES WILDCARD eq port snmpip access-list 150 permit tcp TRUSTED_SOURCE_ADDRESSES WILDCARDINFRASTRUCTURE_ADDRESSES WILDCARD eq port snmp!---!--- Deny SNMP traffic from all other sources.!---ip access-list 150 deny udp any any eq port snmpip access-list 150 deny tcp any any eq port snmp!---!--- Permit/deny all other Layer 3 and Layer 4 traffic in!--- accordance with existing security policies and!--- configurations. Permit all other traffic to transit the!--- device.!---access-list 150 permit ip any any!--- Apply access-list to management interfaceinterface serial 2/0ip access-group 150 inFor more information on IP Access Control Lists see the "Configuring IPv4 and IPv6 Access Control List" section in the Cisco MDS 9000 Family NX-OS Security Configuration Guide at the following location:
For more information on IP Access Control Lists see the "Configuring ACLs" section in the Cisco Nexus 5000 Series NX-OS Software Configuration Guide at the following location:
•CSCsr85709
Symptom: Under certain conditions, the port manager can take a long time to respond to a port configuration, which can trigger a set-port-configuration failure. If this occurs, then the FCIP tunnel will not come up and will stay in a disabled state.
Workaround: Enter a shut command, followed by a no shut command on the FCIP interface at either end of the FCIP tunnel.
Related Documentation
The documentation set for the Cisco MDS 9000 Family includes the following documents. To find a document online, use the Cisco MDS SAN-OS Documentation Locator at:
http://www.cisco.com/en/US/products/ps5989/products_documentation_roadmaps_list.htm
For information on IBM TotalStorage SAN Volume Controller Storage Software for the Cisco MDS 9000 Family, refer to the IBM TotalStorage Support website.
Release Notes
•Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Releases
•Cisco MDS 9000 Family Release Notes for Storage Services Interface Images
•Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images
Compatibility Information
•Cisco MDS 9000 SAN-OS Hardware and Software Compatibility Information
•Cisco MDS 9000 Family Interoperability Support Matrix
•Cisco MDS SAN-OS Release Compatibility Matrix for IBM SAN Volume Controller Software for Cisco MDS 9000
•Cisco MDS SAN-OS Release Compatibility Matrix for Storage Service Interface Images
Regulatory Compliance and Safety Information
•Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family
Hardware Installation
•Cisco MDS 9500 Series Hardware Installation Guide
•Cisco MDS 9200 Series Hardware Installation Guide
•Cisco MDS 9216 Switch Hardware Installation Guide
•Cisco MDS 9100 Series Hardware Installation Guide
•Cisco MDS 9124 Multilayer Fabric Switch Quick Start Guide
•Cisco MDS 9020 Fabric Switch Hardware Installation Guide
Cisco Fabric Manager
•Cisco MDS 9000 Family Fabric Manager Quick Configuration Guide
•Cisco MDS 9000 Family Fabric Manager Configuration Guide
•Cisco MDS 9000 Fabric Manager Online Help
•Cisco MDS 9000 Fabric Manager Web Services Online Help
Command-Line Interface
•Cisco MDS 9000 Family Software Upgrade and Downgrade Guide
•Cisco MDS 9000 Family CLI Quick Configuration Guide
•Cisco MDS 9000 Family CLI Configuration Guide
•Cisco MDS 9000 Family Command Reference
•Cisco MDS 9000 Family Quick Command Reference
•Cisco MDS 9020 Fabric Switch Configuration Guide and Command Reference
•Cisco MDS 9000 Family SAN Volume Controller Configuration Guide
Intelligent Storage Networking Services
•Cisco MDS 9000 Family Data Mobility Manager Configuration Guide
•Cisco MDS 9000 Family Storage Media Encryption Configuration Guide
•Cisco MDS 9000 Family Secure Erase Configuration Guide - For Cisco MDS 9500 and 9200 Series
Troubleshooting and Reference
•Cisco MDS 9000 Family Troubleshooting Guide
•Cisco MDS 9000 Family MIB Quick Reference
•Cisco MDS 9020 Fabric Switch MIB Quick Reference
•Cisco MDS 9000 Family SMI-S Programming Reference
•Cisco MDS 9000 Family System Messages Reference
•Cisco MDS 9020 Fabric Switch System Messages Reference
Installation and Configuration Note
•Cisco MDS 9000 Family SSM Configuration Note
•Cisco MDS 9000 Family Port Analyzer Adapter Installation and Configuration Note
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.