Guest

Cisco MDS 9000 NX-OS and SAN-OS Software

Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(2)

 Feedback

Table Of Contents

Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.1(2)

Contents

Introduction

Components Supported

Software Download Process

Determining the Software Version

Downloading Software

Selecting the Correct Software Image for an MDS 9100 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

Performing a Nondisruptive Software Upgrade on Generation 1 Modules

Upgrading Your Version of Cisco Fabric Manager

General Upgrading Guidelines

Upgrading with IVR Enabled

Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(2)

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

New Features in Cisco MDS SAN-OS Release 3.1(2)

Support for Cisco Fabric Switch for HP c-Class BladeSystem

Support for Cisco Fabric Switch for IBM BladeCenter

SAN Device Virtualization

Enable/Disable Link Traps

Daylight Saving Time Change

FCS Discovery of Virtual Devices

OHMS for the MDS 9124 Switch

Compact Flash Report in Cisco Fabric Manager

Fabric Manager New Login Procedure

Limitations and Restrictions

CWDM SFPs

Fabric Manager

iSNS

MTU Size Limitation

Reconfiguring SSM Ports

Virtual Router Redundancy Protocol (VRRP) Interfaces

QoS on an MDS 48-port Fibre Channel Module

Maximum Number of Zones Supported in Interop Mode 4

Using SDV on a Cisco MDS 9124 Switch, on a Cisco Fabric Switch for HP c-Class BladeSystem, or on a Cisco Fabric Switch for IBM BladeCenter

Configuring Default Settings for the Default Zone

PPRC Not Supported with FCIP Write Acceleration

Using IVR In a Fabric With Mixed Code Versions

Caveats

Resolved Caveats

Open Caveats

Related Documentation

Release Notes

Compatibility Information

Regulatory Compliance and Safety Information

Hardware Installation

Cisco Fabric Manager

Command-Line Interface

Troubleshooting and Reference

Installation and Configuration Note

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Product Alerts and Field Notices

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 3.1(2)


Release Date: February 05, 2007

Text Part Number: OL-12208-02 U0

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/hw/ps4159/ps4358/prod_release_notes_list.html


Table 1 shows the online change history for this document.

Table 1 Online History Change

Revision
Date
Description

A0

02/05/2007

Created release notes.

B0

02/07/2007

Added a "Maximum Number of Zones Supported in Interop Mode 4".

Revised the description of the Upgrade Path in Table 6 and the description of the Downgrade Path in Table 7.

Added the Limitation "Using SDV on a Cisco MDS 9124 Switch, on a Cisco Fabric Switch for HP c-Class BladeSystem, or on a Cisco Fabric Switch for IBM BladeCenter".

C0

02/14/2007

Added CSCsh69086 and CSCsh71985.

D0

02/27/2007

Added CSCsh66920.

Removed CSCsg19148.

E0

03/30/2007

Added DDTS CSCsg29630, CSCsh02602, CSCsh21262, CSCsh24256, CSCsh62126, CSCsh66010, CSCsh66920, CSCsh82676, CSCsh83200, CSCsh85505, CSCsh86629, CSCsh93540, CSCsh94906, and CSCsi24128.

Added the section "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch".

Added the section "Configuring Default Settings for the Default Zone".

F0

04/05/2007

Revised the section "Upgrading a Cisco MDS 9124 Switch".

Added the section "Fabric Manager New Login Procedure".

G0

05/03/2007

Added DDTS CSCsg52197.

H0

05/15/2007

Removed the Interop Mode 4 Support Limitation.

I0

05/31/2007

Added DDTS CSCsh75149, CSCsi27133, CSCsi31860, CSCsi33540, CSCsi41668, and CSCsi52049.

J0

07/18/2007

Added DDTS CSCsj04224, CSCsj07363, and CSCsj19105.

Removed DDTS CSCei82909.

K0

08/24/2007

Added DDTS CSCsh95415.

L0

09/24/2007

Added DDTS CSCsi72048.

M0

09/27/2007

Added DDTS CSCeh35635, CSCsg49151, CSCsg62704, CSCsh05721, CSCsh63658, CSCsi49231, CSCsi56949, CSCsj13175, CSCsj29134, CSCsj52389, CSCsj64048, CSCsj65565, and CSCsj95379.

N0

10/24/2007

Changed the status of DDTS CSCsh31236 to Resolved.

Added a Note about Downgrading from Cisco SAN-OS 3.2(1) to the "Downgrading Your Cisco MDS SAN-OS Software Image" section.

P0

04/23/2008

Added DDTS CSCsk48149.

Q0

04/30/2008

Added DDTS CSCso63465.

R0

11/13/2008

Added the "Performing a Nondisruptive Software Upgrade on Generation 1 Modules" section.

S0

11/18/2008

Added DDTS CSCso72230.

T0

07/30/2010

Added the "PPRC Not Supported with FCIP Write Acceleration" limitation.

Added the "Using IVR In a Fabric With Mixed Code Versions" limitation.

U0

11/04/2010

Added the Supervisor-2A module to Table 2.


Contents

This document includes the following sections:

Introduction

Components Supported

Software Download Process

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.1(2)

Limitations and Restrictions

Caveats

Related Documentation

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

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.1.2

MDS 9500 Supervisor/Fabric-2, SAN-OS software.

MDS 9500 Series only

 

M95S1K9-3.1.2

MDS 9500 Supervisor/Fabric-I, SAN-OS software.

MDS 9500 Series only

 

M92S1K9-3.1.2

MDS 9216 Supervisor/Fabric-I, SAN-OS software.

MDS 9200 Series only

 

M91S2K9-3.1.2

MDS 9100 Supervisor/Fabric-2, SAN-OS software.

MDS 9100 Series only

 

M91S1K9-3.1.2

NDS 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

M9500FMS1K9

Fabric Manager Server package.

MDS 9500 Series

M9200FMS1K9

Fabric Manager Server package.

MDS 9200 Series

M9100FMS1K9

Fabric Manager Server package.

MDS 9100 Series

M9500EXT1K9

SAN Extension over IP package for IPS-8 module.

MDS 9500 Series

M9200EXT1K9

SAN Extension over IP package for IPS-8 module.

MDS 9200 Series

M9500EXT14K9

SAN Extension over IP package for IPS-4 module.

MDS 9500 Series

M9200EXT14K9

SAN Extension over IP package for IPS-4 module.

MDS 9200 Series

M9500EXT12K9

SAN Extension over IP package for MPS 14+2 module.

MDS 9500 Series

M9200EXT12K9

SAN Extension over IP package for MPS 14+2 module.

MDS 9200 Series

M9500SSE1K9

Storage Services Enabler package.

MDS 9500 Series with SSM

M9200SSE1K9

Storage Services Enabler package.

MDS 9200 Series with SSM

M9124PL8-4G

On-Demand Ports Activation License

MDS 9124 Switch

HP-PL12-4G

On-Demand Ports Activation License

Cisco Fabric Switch for HP c-Class BladeSystem only

IBM-PL10-4G

On-Demand Ports Activation License

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 only

DS-C9509

MDS 9509 director, base configuration (9-slot modular chassis includes 7 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).

MDS 9509 only

DS-C9506

MDS 9506 director (6-slot modular chassis includes 4 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately).

MDS 9506 only

DS-C9216-K9

MDS 9216 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).

MDS 9216 only

DS-C9216A-K9

MDS 9216A 16-port semi-modular fabric switch (includes 16 1-Gbps/2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately).

MDS 9216A only

DS-C9216i-K9

MDS 9216i 16-port semi-modular fabric switch (includes 14 1-Gbps/2-Gbps Fibre Channel ports, 2 Gigabit Ethernet ports, power supply, and expansion slot—SFPs sold separately).

MDS 9216i only

DS-C9140-K9

MDS 9140 fixed configuration (non-modular) fabric switch (includes 8 full rate ports and 32 host-optimized ports).

MDS 9140 only

DS-C9124-K9

MDS 9124 fixed configuration (non-modular) multilayer fabric switch (includes 8 enabled ports; an on-demand ports activation license can enable 8 additional ports, up to 24 ports).

MDS 9124 only

DS-C9120-K9

MDS 9120 fixed configuration, non-modular, fabric switch (includes 4 full rate ports and 16 host-optimized ports).

MDS 9120 only

 

DS-HP-FC-K9

Cisco Fabric Switch for HP c-Class BladeSystem (includes sixteen internal and eight external active ports and four 4-Gb SFPs installed, or eight internal and four external active ports and two 4-Gb SFPs installed).

Cisco Fabric Switch for HP c-Class BladeSystem only

 

DS-IBM-FC-K9

Cisco Fabric Switch for IBM BladeCenter (includes fourteen internal and six external ports)

Cisco Fabric Switch for IBM BladeCenter only

External crossbar module

DS-13SLT-FAB1

MDS 9513 crossbar fabric module.

MDS 9513 only

Supervisor modules

DS-X9530-SF2-K9

MDS 9500 Supervisor-2 module.

MDS 9500 Series only

DS-X9530-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

DS-X9124

MDS 9000 24-port 4-Gbps Fibre Channel module (SFPs sold separately).

MDS 9500 Series and 9200 Series, except for the MDS 9216

DS-X9148

MDS 9000 48-port 4-Gbps Fibre Channel module (SFPs sold separately).

MDS 9500 Series and 9200 Series, except for the MDS 9216

DS-X9704

MDS 9000 4-port 10-Gbps Fibre Channel module (SFPs sold separately)

MDS 9500 Series and 9200 Series, except for the MDS 9216

Services modules

DS-X9308-SMIP

8-port Gigabit Ethernet IP Storage services module.

MDS 9500 Series and 9200 Series

DS-X9304-SMIP

4-port Gigabit Ethernet IP Storage services module.

DS-X9032-SSM

MDS 9000 32-port 1-Gbps/2-Gbps Fibre Channel Storage Services Module (SSM).

DS-X9302-14K9

14-port Fibre Channel/2-port Gigabit Ethernet Multiprotocol Services (MPS-14/2) module.

Optics

DS-X2-FC10G-SR

X2/SC optics, 10-Gbps Fibre Channel for Short Reach.

MDS 9500 Series and 9200 Series, except for the MDS 9216

DS-X2-FC10G-LR

X2/SC optics, 10-Gbps Fibre Channel for Long Reach.

DS-X2-FC10G-ER

X2/SC optics, 10-Gbps Fibre Channel for Extended Reach (40 km).

LC-type fiber-optic SFP

DS-SFP-FC-2G-SW

2-Gbps/1-Gbps Fibre Channel—short wavelength SFP.

MDS 9000 Family

DS-SFP-FC-2G-LW

2-Gbps/1-Gbps Fibre Channel—long wavelength SFP.

DS-SFP-FCGE-SW

1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—short wavelength SFP.

DS-SFP-FCGE-LW

1-Gbps Ethernet and 1-Gbps/2-Gbps Fibre Channel—long wavelength SFP.

DS-SFP-GE-T

1-Gbps Ethernet SFP.

DS-SFP-FC4G-SW

4-Gbps/2-Gbps/1-Gbps Fibre Channel—short wavelength SFP for DS-X91xx switching modules.

MDS 9500 Series and 9200 Series, except for the MDS 9216

DS-SFP-FC4G-MR

4-Gbps/2-Gbps/1-Gbps Fibre Channel—long wavelength SFP for DS-X91xx switching modules only. Supports distances up to 4 km.

DS-SFP-FC4G-LW

4-Gbps/2-Gbps/1-Gbps Fibre Channel—long wavelength SFP for DS-X91xx switching modules only. Supports distances up to 10 km.

CWDM2

DS-CWDM-xxxx

Gigabit Ethernet and 1-Gbps/2-Gbps Fibre Channel SFP LC interface xxxx nm, where xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm.

MDS 9000 Family

DS-CWDM-MUX-4

Add/drop multiplexer for four CWDM wavelengths.

DS-CWDM-MUX-8

Add/drop multiplexer for eight CWDM wavelengths.

DS-CWDMCHASSIS

Two slot chassis for CWDM add/drop multiplexers.

Power supplies

DS-CAC-6000W

6000-W AC power supply.

MDS 9513 only

DS-CAC-2500W

2500-W AC power supply.

MDS 9509 only

DS-CDC-2500W

2500-W DC power supply.

DS-CAC-3000W

3000-W AC power supply.

DS-CAC-4000W-US

4000-W AC power supply for US (cable attached).

DS-CAC-4000W-INT

4000-W AC power supply international (cable attached).

DS-CAC-1900W

1900-W AC power supply.

MDS 9506 only

DS-CDC-1900W

1900-W DC power supply.

DS-CAC-845W

845-W AC power supply.

MDS 9200 Series only

DS-CAC-300W

300-W3 AC power supply.

MDS 9100 Series only

CompactFlash

MEM-MDS-FLD512M

MDS 9500 supervisor CompactFlash disk, 512 MB.

MDS 9500 Series only

Port analyzer adapter

DS-PAA-2, DS-PAA

A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel traffic in a switched fabric.

MDS 9000 Family

CD-ROM

M90FM-CD-212=

MDS 9000 Management Software and Documentation CD-ROM, spare.

MDS 9000 Family

1 SFP = small form-factor pluggable

2 CWDM = coarse wavelength division multiplexing

3 W = Watt


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

Downloading Software

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

Determining the Software Version

To determine the version of Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the CLI, log in to the switch and enter the show version EXEC command.

To determine the version of Cisco MDS SAN-OS software currently running on a Cisco MDS 9000 Family switch using the Fabric Manager, view the Switches tab in the Information pane, locate the switch using the IP address, logical name, or WWN, and check its version in the Release column.


Note We strongly recommend that you use the latest available software release supported by your vendor for all Cisco MDS 9000 Family products.


Downloading Software

The Cisco MDS SAN-OS software is designed for mission-critical high availability environments. To realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules.

To download the latest Cisco MDS SAN-OS software, access the Software Center at this URL:

http://www.cisco.com/public/sw-center

See the following sections in this release note for details on how you can nondisruptively upgrade your Cisco MDS 9000 switch. Issuing the install all command from the CLI, or using Fabric Manager to perform the downgrade, enables the compatibility check. The check indicates if the upgrade can happen nondisruptively or disruptively depending on the current configuration of your switch and the reason.

Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
     1       yes  non-disruptive       rolling
     2       yes      disruptive       rolling  Hitless upgrade is not supported
     3       yes      disruptive       rolling  Hitless upgrade is not supported
     4       yes  non-disruptive       rolling
     5       yes  non-disruptive         reset
     6       yes  non-disruptive         reset

At a minimum, you need to disable the default device alias distribution feature using the no device-alias distribute command in global configuration mode. The show incompatibility system bootflash:1.3(x)_filename command determines which additional features need to be disabled.


Note Refer to the "Determining Software Compatibility" section of the Cisco MDS 9000 Family CLI Configuration Guide for more details.



Note If you would like to request a copy of the source code under the terms of either GPL or LGPL, please send an e-mail to 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 3.

Table 3 Software Image for MDS 9100 Series Switch

Switch
Image

MDS 9120 or MDS 9140

Filename begins with m9100-s1ek9

MDS 9124, Cisco Fabric Switch for HP BladeSystem, or Cisco Fabric Switch for IBM BladeCenter

Filename begins with m9100-s2ek9


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 4.

Table 4 Software Image for Supervisor Type

Supervisor Type
Switch
Image

Supervisor-1 module

MDS 9506 and 9509

Filename begins with m9500-sf1ek9

Supervisor-2 module

MDS 9506, 9509, and 9513

Filename begins with m9500-sf2ek9


Use the show module command to display the type of supervisor module in the switch.

For a Supervisor-1 module, the output might look like this:

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
...
...
5    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    active*
6    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    ha-standby

For a Supervisor-2 module, the output might look like this:

switch# show module
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
...
...
7    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    active *
8    0      Supervisor/Fabric-2              DS-X9530-SF2-K9    ha-standby

Migrating from Supervisor-1 Modules to Supervisor-2 Modules

As of Cisco MDS SAN-OS Release 3.0(1), the Cisco MDS 9509 and 9506 Directors support both Supervisor-1 and Supervisor-2 modules. Supervisor-1 and Supervisor-2 modules cannot be installed in the same switch, except during migration. Both the active and standby supervisor modules must be of the same type, either Supervisor-1 or Supervisor-2 modules. For Cisco MDS 9513 Directors, both supervisor modules must be Supervisor-2 modules.


Caution Migrating your supervisor modules is a disruptive operation.


Note Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported.


To migrate from a Supervisor-1 module to a Supervisor-2 module, refer to the step-by-step instructions in the Cisco MDS 9000 Family CLI Configuration Guide.

Configuring Generation 2 Switching Modules

The Cisco MDS 9500 Multilayer Directors are designed to operate with any combination of Cisco MDS 9000 Generation 1 and Generation 2 modules. However, there are limitations to consider when combining the various modules and supervisors in the Cisco MDS 9500 Series platform chassis. The references listed in this section provide specific information about configurations that combine different modules and supervisors.

For information on configuring Generation 2 switching modules, refer to:

http://www.cisco.com/en/US/products/ps5989/products_configuration_guide_chapter09186a0080664c6b.html

For information on port index availability, refer to:

http://www.cisco.com/en/US/products/ps5990/products_installation_guide_chapter09186a0080419599.html

For information on Cisco MDS 9000 hardware and software compatibility, refer to:

http://www.cisco.com/en/US/products/ps5989/products_device_support_table09186a00805037ee.html

Upgrading Your Cisco MDS SAN-OS Software Image

This section lists the guidelines recommended for upgrading your Cisco MDS SAN-OS software image and contains the following sections:

Performing a Nondisruptive Software Upgrade on Generation 1 Modules

Upgrading Your Version of Cisco Fabric Manager

Upgrading with IVR Enabled

Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(2)

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


Caution Before upgrading your Cisco MDS SAN-OS software image, you must run the Compact Flash Report utility described in the "Compact Flash Report in Cisco Fabric Manager" section. This reporting feature automatically scans your switch fabric and reports the status of Compact Flash on certain switch modules. To run this utility prior to upgrading your Cisco SAN-OS software image, upgrade Cisco Fabric Manager as described in the "Upgrading Your Version of Cisco Fabric Manager" section.

For instructions on how to scan your switch fabric and display the status of Compact Flash using CLI commands, refer to the Cisco MDS 9000 Family CLI Configuration Guide.

Performing a Nondisruptive Software Upgrade on Generation 1 Modules

Generation 1 modules may reload during a nondisruptive SAN-OS software upgrade because of the Compact Flash being unable to partition for the new code. If that happens, the installer aborts and reloads the module.

This issue affects the following modules:

DS-X9016, 16-port 1-Gbps/2-Gbps Fibre Channel module

DS-X9032, 32-port 1-Gbps/2-Gbps Fibre Channel module

DS-X9032-SSM, 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

This issue might be seen during an upgrade from Cisco SAN-OS Release 3.0(x), 3.1(x) or 3.2(x). It has been addressed for upgrades from SAN-OS Release 3.3(1) or higher. Therefore, you will not be impacted by this issue if you are running SAN-OS Release 3.3(1) when you upgrade to a higher SAN-OS release.

When this problem occurs, the module will automatically reload and may cause the Install All to stop, which will cause the upgrade to be unsuccessful. Error messages similar to the following may be displayed:

Install has failed. Return code 0x40930020 (Non-disruptive upgrade of a module failed).
Please identify the cause of the failure, and try 'install all' again.
Module 2: Non-disruptive upgrading.
-- FAIL. Return code 0x40690009 (Error in downloading image for image upgrade).

To avoid this kind of unplanned disruption, follow the methods for identifying and correcting this issue described in Cisco Field Notice 63099, before proceeding with the SAN-OS upgrade. This Field notice can be found under the Support, Products page for Cisco MDS9500 Series Multilayer Directors selection.

The caveat associated with this issue is CSCsm62295.

Upgrading Your Version of Cisco Fabric Manager

To upgrade your version of Cisco Fabric Manager, or install Cisco Fabric Manager for the first time, follow these steps:


Step 1 Download m9000-fm-3.1.2.jar from the Software Center on Cisco.com (http://www.cisco.com/pcgi-bin/tablebuild.pl/mds-fm). You must have a CCO account to access the files on Software Center.


Note As of Cisco MDS SAN-OS Release 3.1, Cisco Fabric Manager requires Java 1.5.


Step 2 Launch the Fabric Manager installation program by doing one of the following:

a. Navigate to the folder where you have downloaded the file and double-click it.

b. Open the file using Internet Explorer.

c. Enter java -jar m9000-fm-3.1.2.jar on the Windows or UNIX command line.

Step 3 Select an installation folder for Fabric Manager on your workstation. The default location is C:\Program Files\Cisco Systems\MDS 9000 for Windows. On a Solaris or Linux machine, the installation path name is /usr/local/cisco_mds9000 or $HOME/cisco_mds9000, depending on the permissions of the user performing the installation.


Note The Fabric Manager Server and the Fabric Manager Client must be able to communicate with each other at all times. They can be installed on different workstations or the same workstation.


Step 4 Check the Don't install and run FM Server check box if you are installing just the Fabric Manager Client on a remote workstation.


Note For other methods and details on upgrading, downgrading, and uninstalling Cisco Fabric Manager, refer to the Cisco MDS 9000 Family Fabric Manager Configuration Guide and the Cisco MDS 9000 Fabric Manager Quick Configuration Guide.


Step 5 Click Finish to complete the Cisco Fabric Manager installation.

General Upgrading Guidelines

Use the following guidelines when upgrading to Cisco MDS SAN-OS Release 3.1(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.

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 5 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. Those nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the upgrade is in progress.

IVR: With IVR enabled, you must follow additional steps if you are upgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the "Upgrading with IVR Enabled" section for these instructions.

FICON: If you have FICON enabled, the upgrade path is different. See Table 6.

Use Table 5 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.1(2). Find the image release number you are currently using in the Current column of the table and use the path recommended.


Note The software upgrade information in Table 5 applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and SSM intelligent services traffic.


Table 5 Nondisruptive Upgrade Path to SAN-OS Release 3.1(2) 

Current
Nondisruptive Upgrade Path

SAN-OS 3.1(1)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 3.0(3a)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 3.0(3)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 3.0(2a)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 3.0(2)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 3.0(1)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 2.1(3)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 2.1(2e)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 2.1(2d)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 2.1(2b)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 2.1(2)

Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.1(2).
or.
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.1(2).

SAN-OS 2.1(1b)

Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.1(2).

SAN-OS 2.1(1a)

Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.1(2).

SAN-OS 2.0(x)

Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.1(2).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.1(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.1(2).


Use Table 6 to determine your nondisruptive upgrade path to Cisco MDS SAN-OS Release 3.1(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.


Note Cisco MDS SAN-OS Release 3.1(2) is not FICON certified.


Table 6 FICON Nondisruptive Upgrade Path to SAN-OS 3.1(2)

Current Release with FICON Enabled
Upgrade Path

SAN-OS 3.0(2)

You can nondisruptively upgrade directly to SAN-OS Release 3.1(2).

SAN-OS 2.0(2b)

Use the interface shutdown command to administratively shut any Fibre Channel ports on Generation 1 modules that are in an operationally down state before nondisruptively upgrading from SAN-OS Release 2.0(2b) to SAN-OS Release 3.0(2), and then upgrade to Release 3.1(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).


Upgrading with IVR Enabled

An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive. Some possible scenarios include the following:

FCIP connection flapping during the upgrade process resulting in fabric segmentation or merge.

ISL flap results in fabric segmentation or merge because of hardware issues or a software bug.

ISL port becomes part of PCP results in fabric segmentation or merge because of a port flap.

If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state because of a domain overlap.

This issue was resolved in Cisco SAN-OS Release 2.1(2b); therefore, you must upgrade to Release 2.1(2b) before upgrading to Release 3.1(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. 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 interface 
port-channel 52 (reason: unknown failure)
2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$ 
Isolation of interface port-channel 51 
(reason: domain ID assignment failure)

Step 4 Issue the following commands for the isolated switches in Step 3:

switch(config)# vsan database
switch(config-vsan-db)# vsan vsan-id suspend
switch(config-vsan-db)# no vsan vsan-id suspend

Step 5 Issue the ivr refresh command to perform an IVR refresh on all the IVR enabled switches.

Step 6 Issue the copy running-config startup-config command to save the RDI mode in the startup configuration on all of the switches.

Step 7 Follow the normal upgrade guidelines for Release 2.1(2b). If you are adding new switches running Cisco MDS SAN-OS Release 2.1(2b) or later, upgrade all of your existing switches to Cisco SAN-OS Release 2.1(2b) as described in this workaround. Then follow the normal upgrade guidelines for Release 3.1(2).



Note RDI mode should not be disabled for VSANs running in interop mode 2 or interop mode 3.


Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(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.1(2).


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 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

Step 4 Save the running configuration to the startup configuration before the upgrade procedure to ensure that the changes are preserved during and after the upgrade. To save the configuration, enter the following command:

switch# copy running-config startup-config

Upgrading the SSI Image on Your SSM

Use the following guidelines to nondisruptively upgrade the SSI image on your SSM:

Install and configure dual supervisor modules.

SSM intelligent services traffic on SSM ports is disrupted during upgrades. Fibre Channel switching traffic is not disrupted under the following conditions:

Upgrade the SSI boot images on the SSMs on the switch to a release version supported by your Cisco SAN-OS release. Refer to the Cisco MDS SAN-OS Release Compatibility Matrix for Storage Service Interface Images.

All SSM applications are disabled. Use the show ssm provisioning CLI command to determine what applications are configured. Use the no ssm enable feature CLI command to disable these applications.

No SSM ports are in auto mode. See the "Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(2)" section.

The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld CLI command to determine your EPLD version. Refer to the Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images to upgrade your EPLD image.

Refer to the Cisco MDS Storage Services Module Interoperability Support Matrix and the "Managing Modules" chapter in the Cisco MDS 9000 Family CLI Configuration Guide, Release 3.x, for information on upgrading your SSM.


Caution Upgrading from Cisco MDS SAN-OS Release 2.1(1b) or earlier to Release 2.1.2 or later can disrupt traffic on any SSM installed on your MDS switch

Upgrading a Switch with Insufficient Space for Two Images on the Bootflash

To upgrade the SAN-OS image on a Cisco MDS 9000 Family switch requires enough space on the internal CompactFlash (also referred to as bootflash) to accommodate both the old software image and the new software image.

As of Cisco MDS SAN-OS Release 3.1(1), on MDS switches with a 256-MB CompactFlash, it is possible in some scenarios that a user might be unable to fit two images on the bootflash. This lack of space on the bootflash might cause the upgrade process to fail because new images are always copied onto the bootflash during an upgrade.

The following MDS switches are affected by this issue:

MDS 9216 and MDS 9216i

MDS 9120 and MDS 9140

MDS 9500 Series switches with a Supervisor 1 module

To work around an image upgrade failure caused by a lack of space on the bootflash, follow these steps:


Step 1 Prior to installing the new image, copy the old (existing) system image file to an external server. You may need to reinstall this file later.

Step 2 Delete the old system image file from the bootflash by using either the Fabric Manager install utility or the CLI delete bootflash: command. The system image file does not contain the word "kickstart" in the filename.
switch# delete bootflash:m9200-ek9-mz.3.0.3.bin


Note On MDS 9500 Series switches, you also need to delete the image file from the standby supervisor after deleting it from the active supervisor.
switch# delete bootflash://sup-standby/m9500-sf1ek9-mz.3.0.3.bin


Step 3 Start the image upgrade or installation process using the Fabric Manager install utility or the CLI install all command.

Step 4 If the new installation or upgrade fails while copying the image and you want to keep the old (existing) image, then copy the old image (that you saved to an external server in Step 1) to the bootflash using either Fabric Manager or the copy command.

Step 5 If the switch fails to boot, then follow the recovery procedure described in the "Troubleshooting Installs, Upgrades, and Reboots" section of the Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x.

Upgrading a Cisco MDS 9124 Switch

If you are upgrading from Cisco MDS SAN-OS Release 3.1(1) to Cisco SAN-OS Release 3.1(2) 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.


Note Before starting the upgrade, issue the no logging level all command. If you do not, the upgrade might fail because of many system log messages printing. This could result in the down time for control plane exceeding 80 seconds.



Note If the management interface of the fabric switch is connected to a Layer 2 switch, we recommend that you enable PortFast on the interface of the switch to which the management interface is connected. By doing so, you avoid spanning-tree convergence time on the switch and ensure packets from the fabric switch are forwarded immediately during the nondisruptive upgrade.


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 5, even though the upgrade is disruptive. Following the nondisruptive upgrade path ensures that the binary startup configuration remains intact.

If you do not follow the upgrade path, (for example, you upgrade directly from SAN-OS Release 2.1(2b) to SAN-OS Release 3.1(2b)), the binary startup configuration is deleted because it is not compatible with the new image, and the ASCII startup configuration file is applied when the switch comes up with the new upgraded image. When the ASCII startup configuration file is applied, there may be errors. Because of this, we recommend that you follow the nondisruptive upgrade path.

Downgrading Your Cisco MDS SAN-OS Software Image

This section lists the guidelines recommended for downgrading your Cisco MDS SAN-OS software image and contains the following sections:

General Downgrading Guidelines

Downgrading the SSI Image on Your SSM

General Downgrading Guidelines

Use the following guidelines to nondisruptively downgrade your Cisco MDS SAN-OS Release 3.1(2):

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 7 for the nondisruptive downgrade path for all SAN-OS releases.

SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write acceleration, is disrupted during a downgrade. SSM Fibre Channel traffic is not.

Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during a downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module. Those nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the downgrade is in progress.

iSCSI: If you are downgrading from SAN-OS version 3.0(x) to a lower version of SAN-OS, enable iSCSI if an IPS module or a MPS-14/2 module is online in the switch. Otherwise, the downgrade will disrupt traffic.

IVR: With IVR enabled, you must follow additional steps if you are downgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the "Upgrading with IVR Enabled" section for these instructions.

FICON: If you have FICON enabled, the downgrade path is different. See Table 8.

iSNS: The iSNS feature does not support a graceful downgrade from Cisco MDS SAN-OS Release 3.1(2) to any earlier SAN-OS release. Prior to a downgrade from Cisco SAN-OS 3.1(2), disable the MDS iSNS server and remove all configurations associated with the MDS iSNS client.

Use Table 7 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.1(2). 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 7 applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP and SSM intelligent services traffic.


Table 7 Nondisruptive Downgrade Path from SAN-OS Release 3.1(2)

To SAN-OS Release
Nondisruptive Downgrade Path

SAN-OS 3.1(1)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 3.0(3a)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 3.0(3)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 3.0(2a)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 3.0(2)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 3.0(1)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 2.1(3)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 2.1(2e)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 2.1(2d)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 2.1(2b)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 2.1(2)

Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(2).

SAN-OS 2.1(1b)

Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1b).

SAN-OS 2.1(1a)

Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1a).

SAN-OS 2.0(4a)

Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4a).

SAN-OS 2.0(4)

Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4).

SAN-OS 2.0(3)

Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(3).

SAN-OS 2.0(2b)

Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(2b).

SAN-OS 2.0(1b)

Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(1b).

SAN-OS 1.x

Downgrade to SAN-OS to Release 2.1(2b), then to Release 1.3(4a), and then downgrade to your SAN-OS 1.x release.


Use Table 8 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.1(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.


Note Cisco MDS SAN-OS Release 3.1(2) is not FICON certified.


Table 8 FICON Downgrade Path from SAN-OS 3.1(2)

To SAN-OS Release with FICON Enabled
Downgrade Path

SAN-OS 3.0(2)

You can nondisruptively downgrade directly from SAN-OS Release 3.1(2).

SAN-OS 2.0(2b)

Use the interface shutdown command to administratively shut any Fibre Channel ports on Generation 1 modules that are in an operationally down state before nondisruptively downgrading from SAN-OS Release 2.0(2b) to SAN-OS Release 3.0(2), and then downgrade to Release 3.1(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.3(4a)

Downgrade to SAN-OS Release 3.0(2). Use the shutdown command to shut all the ports operationally down and administratively up on all the Generation 1 modules before nondisruptively downgrading to Release 2.0(2b) and then downgrade to 1.3(4a).


Downgrading the SSI Image on Your SSM

Use the following guidelines when downgrading your SSI image on your SSM.

On a system with at least one SSM installed, the install all command might fail on an SSM when you downgrade from Cisco SAN-OS Release 3.1(2) to any SAN-OS 2.x release earlier than SAN-OS Release 2.1(2e). Power down the SSM and perform the downgrade. Bring up the SSM with the new bootvar set to the 2.x SSI image.

Downgrade the SSI boot images on the SSMs on the switch to a release version supported by your Cisco SAN-OS release. Refer to the Cisco MDS SAN-OS Release Compatibility Matrix for Storage Service Interface Images.

SSM intelligent services traffic switching on SSM ports is disrupted on upgrades or downgrades.

Fibre Channel switching traffic on SSM ports is not disrupted under the following conditions:

All SSM applications are disabled. Use the show ssm provisioning CLI command to determine if any applications are provisioned on the SSM. Use the no ssm enable feature configuration mode CLI command to disable these features.

The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld CLI command to determine your EPLD version. Refer to the Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images to upgrade your EPLD image.

Refer to the Cisco MDS Storage Services Module Interoperability Support Matrix and to the "Managing Modules" chapter in the Cisco MDS 9000 Family CLI Configuration Guide, Release 3.x for information on downgrading your SSM.


Note Following a downgrade from Cisco MDS SAN-OS Release 3.2(1) to an earlier SAN-OS release that does not support the Data Mobility Manager (DMM) feature that is offered from SAN-OS Release 3.2(1) onwards, you might have stale configuration information on the switch, if you had provisioned DMM on the SSM. In this situation, you can remove the stale configuration from the SSM by entering the following commands:
switch(config)# poweroff module slot
switch# purge module slot running-config


New Features in Cisco MDS SAN-OS Release 3.1(2)

This section briefly describes the new features introduced in this release. For detailed information about the features listed, refer to the Cisco MDS 9000 Family CLI Configuration Guide and the Cisco MDS 9000 Family Fabric Manager Configuration Guide.


Note These release notes are specific to this release. For the complete Release 3.x documentation set, see the "Related Documentation" section.


Support for Cisco Fabric Switch for HP c-Class BladeSystem

Cisco MDS SAN-OS 3.1(2) supports the new Cisco Fabric Switch for HP c-Class BladeSystem.Through the on-demand port activation license, this switch can be configured with sixteen internal and eight external active ports and four 4-Gb SFPs installed, or with eight internal and four external active ports and two 4-Gb SFPs installed. The Cisco Fabric Switch for HP c-Class BladeSystem also features nondisruptive software upgrades.

The Cisco Fabric Switch for HP c-Class BladeSystem does not support the following Cisco MDS SAN-OS features:

IVR

Remote SPAN

Translative loop support

FCC - no generation, quench reaction only

In addition, the following features are limited on the Cisco Fabric Switch for HP c-Class BladeSystem:

VSANs - 16 maximum

SPAN - 1 session maximum


Note The internal and external port names on a Cisco Fabric Switch for HP c-Class BladeSystem differ from the port names on an MDS 9000 Family switch. Internal ports are named bay1 through bay16. External ports are named ext1 through ext8. Refer to the Cisco MDS 9000 Family CLI Configuration Guide for additional information about port names and other important differences in the Cisco Fabric Switch for HP c-Class BladeSystem.


Support for Cisco Fabric Switch for IBM BladeCenter

Cisco MDS SAN-OS 3.1(2) supports the new Cisco Fabric Switch for IBM BladeCenter. This switch includes fourteen internal and six external ports, and it features an on-demand port activation license and nondisruptive software upgrades.

The Cisco Fabric Switch for IBM BladeCenter does not support the following Cisco MDS SAN-OS features:

IVR

Remote SPAN

Translative loop support

FCC - no generation, quench reaction only

In addition, the following features are limited on the Cisco Fabric Switch for IBM BladeCenter:

VSANs - 16 maximum

SPAN - 1 session maximum


Note The internal and external port names on a Cisco Fabric Switch for IBM BladeCenter differ from the port names on an MDS 9000 Family switch. Internal ports are named bay1 through bay14. External ports are named ext0, and ext15 through ext19. Refer to the Cisco MDS 9000 Family CLI Configuration Guide for additional information about port names and other important differences in the Cisco Fabric Switch for IBM BladeCenter.


SAN Device Virtualization

Cisco SAN device virtualization allows you to create virtual devices that represent physical end-devices when configuring switches with Cisco SAN-OS Release 3.1(2) and later. Virtualization of SAN devices accelerates swap-out or failover to a replacement disk.

SAN device virtualization enables you to:

Reduce the amount of time it takes for data migration, and ultimately, the overall amount of down time.

Improve ease-of-use and reduce the possibility of user-introduced errors when making configuration changes.

Cisco SAN-OS Release 3.1(2) supports only virtual targets in the SAN Device Virtualization feature. In addition, LUN zoning is not available for SDV devices in Cisco SAN-OS Release 3.1(2).

Enable/Disable Link Traps

A new command-line interface command has been added to Cisco SAN-OS 3.1(2) that allows you to control whether SNMP link state traps are enabled or disabled. By default, the link state traps are enabled, so that whenever a link toggles its state up or down, a trap is generated. Issuing the no link-state-trap command on the interface disables the traps. The state of the link trap, either enabled or disabled, is added to the running configuration for the switch.

Daylight Saving Time Change

Starting in 2007, daylight saving time (DST) in the U.S. begins on the second Sunday in March and ends on the first Sunday in November.

Cisco SAN-OS does not automatically adjust for daylight saving time. You must change the switch configuration to make the daylight saving time adjustment.

To change the clock on multiple MDS switches in a fabric, use the new Run CLI Commands feature in Cisco Fabric Manager. Follow these steps:


Step 1 Choose Tools > Run CLI Commands.

Step 2 In the Run CLI Commands dialog box, check the box for each switch where you want to change the time.

Step 3 Enter the folder name where the report should be saved that shows the output of the command execution.

Step 4 Enter the clock summer-time command in the text box. For example, if you want to change to daylight saving time in the Pacific time zone, enter the following commands:
config t
clock summer-time PDT 2 Sunday March 02:00 1 Sunday November 02:00 60
exit


Note You must enter exit following configuration mode commands.


Step 5 Click OK to run the command.

Step 6 Check the report that is saved for each switch to verify that the commands executed.


For additional information about the new Run CLI Commands feature in Cisco Fabric Manager, refer to the Cisco MDS 9000 Family Fabric Manager Configuration Guide.

To manually change the time on an MDS switch through the CLI, use the clock summer-time command:

switch# config t
switch(config)# clock summer-time daylight_timezone_name 2 Sunday March 02:00 1 Sunday November 02:00 60

For additional information about this procedure, refer to the Cisco MDS 9000 Family CLI Configuration Guide.

FCS Discovery of Virtual Devices

As of Cisco SAN-OS Release 3.1(2), Cisco Fabric Configuration Services (FCS) supports the discovery of virtual devices. The fcs virtual-device-add command, issued in FCS configuration submode, allows you to discover virtual devices in a particular VSAN or in all VSANs. For the devices that are zoned for IVR to be discovered with this command, they must have request domain_ID (RDI) enabled.

OHMS for the MDS 9124 Switch

The Online Health Management System (OHMS) system health feature is available on the Cisco MDS 9124 Switch. This online diagnostic feature can be used for hardware fault detection and recovery.

Compact Flash Report in Cisco Fabric Manager

Cisco MDS Fabric Manager Release 3.1(2) includes a reporting feature that automatically scans your switch fabric and reports the status of Compact Flash on certain modules.

The Compact Flash report can be used on switches running Cisco MDS 9000 SAN-OS Release 2.x and higher. Creating the report requires that you complete the following tasks:

Upgrade to Cisco Fabric Manager Release 3.1(2). See "Upgrading Your Version of Cisco Fabric Manager" section.

Download the Compact Flash Check Utility (m9000-lc1-gplug-mz.1.0.2.bin).

Run the Compact Flash Report.

To download the Compact Flash Check Utility (m9000-lc1-gplug-mz.1.0.2.bin), follow these steps:


Step 1 Download m9000-lc1-gplug-mz.1.0.2.bin from the Software Center on Cisco.com (http://www.cisco.com/pcgi-bin/tablebuild.pl/mds-utilities). You must have a CCO account to access the files on the Software Center.

Step 2 Save the Compact Flash Check Utility to a tftp server. You will need the tftp server address.


To run the Compact Flash report using Fabric Manager, follow these steps:


Step 1 Select Tools > Compact Flash Report.

You see the Compact Flash Report dialog box with all switches selected.

Step 2 Deselect the check box for the switch(es) for which you do not want to run the CompactFlash report.

Step 3 Specify where you want the report file to be saved.

Step 4 In the Flash Check Utility URL tftp:// field, enter the tftp server location where you saved the CompactFlash Check Utility.

Step 5 Click OK to run the report.

You see the Compact Flash Report dialog box showing the status of each switch.


Note A green indicator light showing Success: Finished Check only indicates that the switch was checked. You must examine the log file for Compact Flash status.


Step 6 If you see the message Error: Failed to copy plugin file, please verify that the path you entered in the Flash Check Utility URL tftp:// field is correct.

Step 7 If necessary, enter the correct location in the Flash Check Utility URL tftp:// field.

Step 8 Click OK to run the report again.

Step 9 Open the log file report for detailed information about Compact Flash status.

Step 10 Click Close to close the dialog box.


Fabric Manager New Login Procedure

As of Cisco SAN-OS Release 3.1(1), logging into Fabric Manger is a two-part process that involves entering your username and password twice, in two different dialog boxes. To successfully complete the login process, you must:

Log in to Fabric Manger Server by entering admin and password in the Fabric Manager Server dialog box

Enter your username, password, and seed switch address in the Discover New Fabric dialog box and then open the fabric

To log in to Fabric Manger Server, follow these steps:


Step 1 Double-click the Fabric Manager Client icon on your workstation.

Step 2 Enter admin, the default username, and password, the default password, in the Fabric Manager Server Login dialog box.

Step 3 Enter the the IP address of the FM Server or set it to it to localhost if you installed Fabric Manager Server on your local workstation.

Step 4 Click Login.


To discover new fabrics, follow these steps:


Step 1 In the Discover New Fabric dialog box, enter the IP address of the Cisco MDS 9000 Family seed switch that you want Fabric Manager to use.

Step 2 Enter your username and password.

Step 3 Choose the Auth-Privacy option MD5-DES (default) when you log in.

Step 4 Click Discover.

The Open Fabric dialog box displays.

Step 5 Check the check box(es) next to the fabric(s) you want to open in the Select column, or click Discover to add a new fabric.

Step 6 Click Open to open the fabric.


For additional information about logging in to Fabric Manager and setting the seed switch, refer to "Setting the Seed Switch in Cisco SAN-OS Release 3.1(1) and Later" in the Cisco MDS 9000 Family Fabric Manager Configuration Guide.

Limitations and Restrictions

This section lists the limitations and restrictions for this release. This section includes the following topics:

CWDM SFPs

Fabric Manager

iSNS

MTU Size Limitation

Reconfiguring SSM Ports

Virtual Router Redundancy Protocol (VRRP) Interfaces

QoS on an MDS 48-port Fibre Channel Module

Maximum Number of Zones Supported in Interop Mode 4

Using SDV on a Cisco MDS 9124 Switch, on a Cisco Fabric Switch for HP c-Class BladeSystem, or on a Cisco Fabric Switch for IBM BladeCenter

Configuring Default Settings for the Default Zone

PPRC Not Supported with FCIP Write Acceleration

Using IVR In a Fabric With Mixed Code Versions

CWDM SFPs

The 2-Gbps CWDM SFPs do not have have a maximum speed set in memory and they negotiate to 4-Gbps on modules that support the higher speed. As a result, the link comes up and appears to work, but then becomes disabled and connectivity problems occur. To correct this problem, both sides of the connection must have their speed hard coded to 2-Gbps.

Fabric Manager

Observe the following limitations or restrictions for the Cisco SAN-OS Release 3.1(2) for Fabric Manager:

The Microsoft Security Patch MS06-040 is known to break applications with a large heap memory. If you increase any Java application's heap (including Fabric Manager) beyond 64 M, we recommend you do not apply this patch.

If port 80 on the switch is blocked and you are using VPN, FM cannot detect NAT addresses. The timeout for URL connections is set for 500ms.

iSNS

Observe the following behaviors regarding the iSNS server and client:

The iSNS feature does not support a graceful downgrade from Cisco MDS SAN-OS Release 3.1(2) to any earlier SAN-OS release. Prior to a downgrade from Cisco SAN-OS 3.1(2), disable the MDS iSNS server and remove all configurations associated with the MDS iSNS client.

The Cisco MDS 9000 switches iSNS server does not support registration, query, or state change information from an actual iSCSI target.

The iSNS client registers all targets outside the permitted VSAN if you configure the iSCSI interface and targets to be part of different VSANs.

The iSNS client functionality on Cisco MDS 9000 switches does not work on VRRP interfaces.

The iSNS client functionality on Cisco MDS 9000 switches does not support registration of iSLB initiators.

MTU Size Limitation

The Cisco MDS 9216i switch and MPS-14/2 module do not support an MTU size greater than 8000 bytes. An attempt to set the MTU size greater than 8000 bytes will result in an error. As a workaround, reset the value of the MTU size (576 to 8000 bytes) and issue the no shutdown command on the interface for normal operation.

Reconfiguring SSM Ports

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.1(1). For instructions about how to modify the configuration of the ports before upgrading to SAN-OS Release 3.1(2), see the "Reconfiguring SSM Ports Before Upgrading to SAN-OS Release 3.1(2)" section.

Virtual Router Redundancy Protocol (VRRP) Interfaces

When a switchover occurs on a switch that is the master for Virtual Router Redundancy Protocol (VRRP) interfaces, the switchover may cause a minor delay. As a result, the VRRP backup (occurring elsewhere) may assume the role of the VRRP master. As a workaround, increase the VRRP advertisement interval for these interfaces.

QoS on an MDS 48-port Fibre Channel Module

Due to possible differences in parts per million between the MAC ASICs on both sides of an ISL link, there is a potential throughput issue when running QoS over an ISL on an MDS 48-port Fibre Channel module. Specifically, the user may not see traffic throughput that follows the programmed QoS ratios. The throughput ratio on the high and/or medium priority class of service (COS) relative to the low priority COS, may not be as high as the actual programmed ratio.

If this situation occurs, you can move the ISL to a port on a different port group on one and/or both sides of the link, or move the ISL to a port on a lower-density card if you require accurate QoS ratios.

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.

Using SDV on a Cisco MDS 9124 Switch, on a Cisco Fabric Switch for HP c-Class BladeSystem, or on a Cisco Fabric Switch for IBM BladeCenter

There must be at least one SAN device virtualization-enabled switch that is not a Cisco MDS 9124 switch, a Cisco Fabric Switch for HP c-Class BladeSystem, or a Cisco Fabric Switch for IBM BladeCenter between the server and the target that are being virtualized. In other words, SAN device virtualization does not work when initiators and primary targets are connected to the same Cisco MDS 9124 Switch or Cisco Fabric Switch for HP c-Class BladeSystem or Cisco Fabric Switch for IBM BladeCenter.

Configuring Default Settings for the Default Zone

Following an upgrade from any Cisco SAN-OS 2.x release to any Cisco SAN-OS 3.x release, the configuration defined by the zone default-zone permit vsan vsan-id command is applied only to the active VSAN. The configuration does not apply to unconfigured VSANs. In SAN-OS 3.x, you can apply the configuration to unconfigured VSANs by issuing the system default zone default-zone permit command.

Similarly, the zoneset distribute full vsan vsan-id command applies only to the active VSAN following an upgrade from any Cisco SAN-OS 2.x release to any Cisco SAN-OS 3.x release.

Although you can configure the default-zone settings in the setup script, these settings do not take effect for VSAN 1, because VSAN 1 already exits prior to running the setup script. To configure the default settings for the default-zone in VSAN 1, you must explicitly enter the zone default-zone permit command.

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.

Caveats

This section lists the open and resolved caveats for this release. Use Table 9 to determine the status of a particular caveat. In the table, "O" indicates an open caveat and "R" indicates a resolved caveat.

Table 9 Open Caveats and Resolved Caveats Reference 

DDTS Number
Software Release (Open or Resolved)
3.1(1)
3.1(2)

Severity 2

CSCsg49151

O

O

CSCsg72224

O

R

CSCsh02602

O

O

CSCsh27851

O

R

CSCsh31236

O

R

CSCsh56514

O

R

CSCsi24128

O

O

CSCsi31860

-

O

CSCsi33540

O

O

CSCsi49231

O

O

CSCsi72048

-

O

CSCsj04224

O

O

CSCsj19105

O

O

CSCsj64048

-

O

CSCsj65565

O

O

CSCso72230

O

O

Severity 3

CSCin95789

O

O

CSCsd21187

O

O

CSCse31881

O

O

CSCsg19303

O

O

CSCsg52197

O

R

CSCsg62704

O

O

CSCsg75925

O

R

CSCsh05721

O

O

CSCsh16546

O

R

CSCsh17787

O

R

CSCsh21262

O

O

CSCsh24256

O

O

CSCsh28390

O

R

CSCsh29188

O

R

CSCsh29199

O

R

CSCsh32426

O

R

CSCsh34515

O

R

CSCsh40033

O

R

CSCsh53560

O

R

CSCsh53578

O

R

CSCsh59895

O

R

CSCsh60422

O

R

CSCsh62126

O

O

CSCsh63658

-

O

CSCsh66010

O

O

CSCsh66920

O

O

CSCsh69086

O

O

CSCsh71985

-

O

CSCsh75149

O

O

CSCsh82676

O

O

CSCsh83200

O

O

CSCsh85505

O

O

CSCsh93540

O

O

CSCsh94906

-

O

CSCsh95415

O

R

CSCsi27133

O

O

CSCsi41668

-

O

CSCsi56949

-

O

CSCsj07363

O

O

CSCsj13175

-

O

CSCsj29134

-

O

CSCsj52389

-

O

CSCsj95379

-

O

CSCsk48149

O

O

CSCso63465

O

O

Severity 4

CSCsh86629

-

O

CSCsi52049

-

O

Severity 6

CSCeh35635

O

O

CSCsg29630

O

O


Resolved Caveats

CSCsg72224

Symptom: The fabric login (FLOGI) process fails while new hosts are initializing. The show flogi internal event error command shows that a module is not present.

Workaround: This issue is resolved

CSCsh27851

Symptom: If you create a PortChannel with a number higher than 128, IP over Fibre Channel (IPFC) ping does not work.

Workaround: This issue is resolved.

CSCsh31236

Symptom: On a Cisco MDS 9513 Switch, when there are more than 512 ports on a single chassis, some ports with indexes between 0x200 and 0x20f may not come up. In addition, some ports with indexes between 0x0 and 0xf may show unexpected behavior when the ports with indexes between 0x200 and 0x20f are brought up. To display the port indexes, issue the show system internal fcfwd idxmap port-to-interface command. The port indexes appear in the column with the heading "glob idx."

Workaround: This issue is resolved.

CSCsh56514

Symptom: Cisco Fabric Manager Server does not allow monitoring of unlicensed fabrics without a client connected. EMC Call Home needs to run continuously on multiple unlicensed fabrics, even if no client is connected.

Workaround: This issue is resolved.

CSCsg52197

Symptom: After you install an MPS-14/2 module, the power capacity level on the switch might be incorrect.

Workaround: This issue is resolved.

CSCsg75925

Symptom: An MDS switch does not respond to a query of the Fabric Configuration Server (FCS) for devices zoned through IVR.

Workaround: This issue is resolved. For additional information, see "FCS Discovery of Virtual Devices" section.

CSCsh16546

Symptom: On the Cisco MDS 9124 Switch, traffic may not flow to and from an FL port, if an F port and an FL port are part of the same port group. In addition, hard zoning may not be strictly enforced in that port group. This problem may not happen if the FL port has only one disk or device behind it.

Workaround: This issue is resolved.

CSCsh17787

Symptom: The Fabric Manager Web Server report for port group performance does not show the correct port groups for the MDS 9000 48-port 4-Gbps Fibre Channel module.

Workaround: This issue is resolved.

CSCsh28390

Symptom: Dynamic port VSAN membership (DPVM) entries are configured and activated in the DPVM database, but the output of the show dpvm ports vsan command is null. This occurs only with ports that are assigned a dynamic VSAN based on a device alias configuration in the DPVM, as opposed to ports that have a dynamic VSAN assigned based on nWWN or pWWN configuration.

Workaround: This issue is resolved.

CSCsh29188

Symptom: The Fabric Manager DPVM table does not support device types.

Workaround: This issue is resolved.

CSCsh29199

Symptom: The WWN Name value in the DPVM active database displays incorrectly in Fabric Manager.

Workaround: This issue is resolved.

CSCsh32426

Symptom: During a downgrade to a Cisco MDS SAN-OS software image, any activity that requires hardware programming results in a standby supervisor being reset and the downgrade being terminated.

Workaround: This issue is resolved.

CSCsh34515

Symptom: Occasionally, following an IVR zone set activation, IVR fails to export some devices to other VSANs. (For scalability reasons, IVR maintains a run-time cache of all devices in IVR zones that have been successfully activated. If activation fails in a VSAN and later succeeds, then devices that are member of that VSAN are not added to the cache.)

Workaround: This issue is resolved.

CSCsh40033

Symptom: When a device is removed from a remote switch, the device might still appear in the name server database, and the fcns refresh command might fail to remove the stale entry.

Workaround: This issue is resolved.

CSCsh53560

Symptom: Volatile memory might get full because captured IVR PLOGI records are not deleted after the PLOGIs are released. This situation occurs when one or more hosts send unexpectedly large number of PLOGIs in a short time, such as when a VMware host sends PLOGIs to disks with no LUNs exposed to the host SAN volume controller (SVC) environment.

Workaround: This issue is resolved.

CSCsh53578

Symptom: During a Cisco MDS SAN-OS software upgrade, the acltcam process may restart if an unexpected value is read from an unused hardware TCAM location. As a result, the upgrade of this module and subsequent modules may be terminated.

Workaround: This issue is resolved.

CSCsh59895

Symptom: During an upgrade to Cisco MDS SAN-OS Release 3.1(1), when IVR is configured in non-NAT mode, an access control list (ACL) process might occasionally exit if it encounters a specific error condition. This could cause the module to reload.

Workaround: This issue is resolved.

CSCsh60422

Symptom: In a manually configured IVR VSAN topology, IVR zone set activation might fail in interop mode 4 VSANs. If this happens, the following messages are logged:

2007 Jan 28 08:09:12 MDS1 %ZONE-2-ZS_CHANGE_ACA_FAILED: %$VSAN 1%$ ACA failed : domain 0x02 returns NO_REASON_CODE

2007 Jan 28 08:09:12 MDS1 %ZONE-2-ZS_CHANGE_ACTIVATION_FAILED:

Workaround: This issue is resolved.

CSCsh95415

Symptom: After setting the clock from Fabric Manager (using SNMP), I/O timeouts were observed. The network time protocol (NTP) was not sending the notification that the clock had changed.

Workaound: This issue is resolved.

Open Caveats

CSCsg49151

Symptom: If you bring up more than one link at a time between two VSANs that have overlapping domains and at least one of the switches is SDV enabled, one link will become isolated. The other links will come up, even though the domains are overlapping. In addition, the SDV virtual domains will change, causing traffic disruption on all devices associated with their old value.

Workaround: Bring up multiple links between two switches one at a time. Verify that the first link came up correctly before attempting to bring up the next link. If the first link fails to come up because of a domain ID overlap, resolve the domain conflict and then try again to bring up the links.

CSCsh02602

Symptom: On large fabrics with many PortChannels, the Fabric Manager Server may consume 99-100% of the CPU for extended periods of time.

Workaround: Restart the Fabric Manager Server.

CSCsi24128

Symptom: If you are using a Cisco MDS 16-port or 32-port 2-Gbps Fibre Channel switching module, a 4-port or 8-port Gigabit Ethernet IP Storage services module, the Storage Services Module (SSM), or the 14/2-port Multiprotocol Services (MPS-14/2) module and you perform a nondisruptive upgrade to Cisco SAN-OS 3.1(1), 3.1(2), or 3.1(2a), the modules do not correctly route traffic to any new modules that you insert following the upgrade.

Workaround: To workaround this issue, do one of the following:

Reload the Cisco MDS 16-port or 32-port 2-Gbps Fibre Channel switching module, the 4-port or 8-port Gigabit Ethernet IP Storage services module, the Storage Services Module (SSM), or the 14/2-port Multiprotocol Services (MPS-14/2) module

Reload the standby supervisor module (in slot 6/9 only)

Perform a supervisor switchover

Upgrade to Cisco SAN-OS Release 3.1(2b)

CSCsi31860

Symptom: If there is an interruption to the upgrade process on a given module during an upgrade to Cisco MDS SAN-OS Release 3.1(2), the install all command will fail. This may result in a condition where some modules and supervisors are running SAN-OS 3.1(2) and the remainder of modules in the chassis are running an older version of SAN-OS. You may not be able to execute the install all command again to upgrade the remaining modules to SAN-OS 3.1(2).

If you issue the show install all status command, you may see the following types of messages in the install logs:

Module X: Upgrading Bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
-- FAIL. Return code 0x40710001 (BIOS versions are identical).
CAUTION: The BIOS/loader/bootrom of above module may be in corrupted state. Please try programming it again and DO NOT reboot without programming it successfully, otherwise you have to manually take out the flash from the card and program it in a BIOS programming station.

Install has failed. Return code 0x40930015 (Pre-upgrade of a module failed).Please identify the cause of the failure, and try 'install all' again.

Workaround: Issue the install module module-number image forced hidden command to upgrade the modules that are running the lower version of SAN-OS following the failure of the install all command.

CSCsi33540

Symptom: On a 4-Gbps Fibre Channel module, PLOGI accepts were discarded because the port was initially an F port, but had been changed to an E port.

Workaround: To resolve this issue, follow these steps:

1. Remove the E port from the PortChannel.

2. Reconfigure the port as an F port.

3. Issue the shut command on the port.

4. Change the port to an E port

5. Add the port to the PortChannel.

6. Enter the no shut command on the port.

CSCsi49231

Symptom: 100% CPU utilization was seen on an MDS switch. It was caused by repeated fabric logins (FLOGIs) on a particular port. This situation can occur if a host cannot log in because the allocation of the FC ID fails, and keeps re-trying using a specific pattern of Source FC IDs (S_IDs) for the FLOGI frame.

Workaround: The interface will now be error-disabled for too many FLOGI failures.

To troubleshoot the configuration and find the reason for the FC ID allocation failure, examine the messages in the syslog. Refer to the Cisco MDS 9000 Family CLI Configuration Guide for detailed information about FLOGI, FC IDs, and FC ID allocation for HBAs.

CSCsi72048

Symptom: FCIP links may fail on an MDS 9216i switch that has compression set to auto when the other end of the FCIP link is terminated by an IPS-8 module. You may see the following message in the logs:

%IPS_SB_MGR-SLOT1-3-CRYPTO_FAILURE: Heartbeat failure in encryption engine (error 0x1)
%ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface GigabitEthernet1/1 is down (Port software failure)
%PORT-5-IF_DOWN_SOFTWARE_FAILURE: %$VSAN 1%$ Interface fcip99 is down (Port software failure)

Workaround: If both ends of an FCIP link are not on an MPS-14/2 module, do not use mode 1 and auto.

CSCsj04224

Symptom: If you install a feature license on any module, then the storage services module (SSM) with the SCSI flow feature will be reprovisioned and write acceleration on the flows will be affected.

Workaround: To work around this issue, please contact Cisco TAC. They can help you recover from this problem by guiding you through the following steps:

1. Enter the shutdown command to shut the host and storage ports that are using the SCSI flow.

2. Enter the no scsi-flow flow-id flow-id command to remove the SCSI flow.

3. Enter the no ssm enable feature scsi-flow force module slot-number command to unprovision the SCSI flow. This will reload the module.

4. When the module is up, enter the ssm enable feature scsi-flow module slot-number command to enable the SCSI flow feature.

5. Reconfigure the SCSI flow.

CSCsj19105

Symptom: A crash might occur in the intelligent line card (ILC) helper process when provisioning or deprovisioning a storage application on the SSM card.

Workaround: If the ILC helper dumps core memory three times, reboot the switch for it to function normally. Use the show cores command to determing if the ILC helper has dumped core memory.

CSCsj64048

Symptom: In rare situations, data virtual target (DVT) configurations might disappear following a reload of the SSM or an upgrade to the SSI 3.1(2m) image.

Workaround: Statically define the DVTs using the santap module command, as in the following example:

switch(config)# santap module slot-number dvt target-pwwn target-pwnn target-vsan target-vsan-id dvt-name dvt-name dvt-vsan dvt-vsan-id lun-size-handling 1

CSCsj65565

Symptom: Spectra Logic tape drives require a unique area ID.

Workaround: Add the company OUI ID to the swtich database so that the switch can assign unique area IDs to the Spectra Logic tape drives.

CSCso72230

Symptom: In rare instances, the following Generation 2 modules might reload:

12-port 4-Gbps Fibre Channel module

24-port 4-Gbps Fibre Channel module

48-port 4-Gbps Fibre Channel module

4-port 10-Gbps Fibre Channel module

The output of the show logging log command will have events like those shown below. In the following output, module 7 is the supervisor and module 12 is the module that reloaded.

2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 7 (serial: JAE1134UR88) 
reported warnings on ports 7/1-7/3 (Unknown) due to BE2 Arbiter experienced an error 
in device 65 (device error 0xc410d613)
2008 Jul 15 19:39:30 fcd95c41 %MODULE-4-MOD_WARNING: Module 8 (serial: JAE1134UOTD) 
reported warnings on ports 8/1-8/3 (Unknown) due to BE2 Arbiter experienced an error 
in device 65 (device error 0xc410d613)
2008 Jul 15 19:39:35 fcd95c41 %XBAR-5-XBAR_STATUS_REPORT: Module 12 reported status 
for component 88 code 0x40240015.
2008 Jul 15 19:39:35 fcd95c41 %MODULE-2-MOD_DIAG_FAIL: Module 12 (serial: JAE1136VU6L) 
reported failure on ports 12/1-12/24 (Fibre Channel) due to Fatal runtime Arb error. 
(DevErr is bitmap of failed modules) in device 88 (device error 0x800)
"show logging onboard" will show log similar to the one below for the reloaded module:
Logging time: Tue Jul 15 19:39:28 2008
machine check: process swapper (0), jiffies 0x744af3a4
Free pages in zone[0]:0x4a70,zone[1]:0x0,zone[2]:0x0
Stack: c000dd58 c001eefc c000b2c4 c000ae98 d2060e10 c003d7a4 c00f869c c0045cdc
d196c584 d196d100 c000c31c c000c3e4 c000ae90 c000c910 c000c924 c0008948 c01ca610 
c0000394
...................
..................

Workaround: None. The chance of a module reload occurring again on the same module is very rare. Therefore, continued use of the module is acceptable.

A software workaround for this issue exists in SAN-OS Release 3.3.(2) and NX-OS Release 4.(1b). Upgrading to one of those releases will help decrease instances of modules reloads.

CSCin95789

Symptom: When you configure Cisco Traffic Analyzer to capture traffic on one or more interfaces on a Windows platform, the configuration web page might not show that the interface has been selected for traffic capture even though traffic capture on that interface is enabled.

Workaround: Check the logs to clarify that the correct interface has been selected.

CSCsd21187

Symptom: If an iSNS client tries to register a portal separately after registering the network entity and storage node object with the Cisco MDS iSNS server, the portal registration might fail.

Workaround: Register the portal at the same time as the network entity and storage node object registration.

CSCse31881

Symptom: If there are IPFC interfaces configured on an SSM, you might experience issues if you downgrade from SAN-OS Release 3.x to Release 2.x.

Workaround: Before downgrading, remove the IPFC interface on the module and then recreate the IPFC interface after the downgrade is complete.

CSCsg19303

Symptom: Graceful shutdowns of ISLs are not supported for IVR traffic.

Workaround: Increase the fspf cost on the link before it is shut down, so that traffic will flow through an alternate path.

CSCsg62704

Symptom: On an MDS switch with dual supervisor modules, the bootflash on the standby supervisor is replaced with a new bootflash. Then there is a system switchover. Then the bootflash on the new standby supervisor (which was previously the active supervisor) is replaced. The copy running-config startup-config command is used to save the configuration, but the console speed does not get saved. Instead, the console speed is reset to 9600.

Workaround: After you replace the bootflash and the standby supervisor boots up, issue the copy running-config startup-config command to synchronize the configuration from the active supervisor to the standby supervisor.

CSCsh05721

Symptom: An association call from a VSAN to its logical switch returns a particular WWN, but an association call from the physical system to the virtual system does not return the same WWN, which indicates that the logical switch is not associated to the physical switch.

Workaround: None.

CSCsh21262

Symptom: Changing fabric credentials from a local SNMP user to a TACACS+ user in Cisco Fabric Manager using server > admin results in a Fabric Manager Server error.

Workaround: Close the fabric and then reopen it using the new TACACS+ user credentials, with Accelerate Discover unchecked.

CSCsh24256

Symptom: It is possible for the hardware interface that is used to access SFPs and temperature sensors on modules to lock up. This inhibits the detection of a subsequent removal or insertion of an SFP and results in the failure to read a module's temperature sensors.

Workaround: Reload the module to recover the sensor.

CSCsh62126

Symptom: When compression is enabled on an FCIP link, the throughput on the GigabitEthernet interface may be reduced, as compared to uncompressed throughput. Depending on the data pattern, this may or may not impact application throughput.

Workaround: If application throughput is reduced, disable compression on the FCIP link.

CSCsh63658

Symptom: Under rare circumstances, a customer running the Cisco MDS SAN-OS SANTap feature with EMC RecoverPoint might find that following a reload of the SSM module, the SSM CVT is stuck in UNKNOWN status in the RecoverPoint appliance.

Workaround: None.

CSCsh66010

Symptom: If the limit of 5000 iSCSI sessions is reached and new initiators try create sessions, a memory leak may occur.

Workaround: Do not exceed the 5000 session limit.

CSCsh66920

Symptom: In Cisco Fabric Manager Release 3.1(1), some tables in the database are cleared after a fabric is persisted to the database. This causes Fabric Manager Client to show empty ISLs or end ports in the Inventory page, as well as zero ISLs, zero end ports, or zero flows in the Performance page.

Workaround: None.

CSCsh69086

Symptom: Zone member configuration based on interface domain does not work correctly in Cisco MDS SAN-OS 3.1(1) and3.1(2) when you use CLI commands to configure interface-domain zones.

Workaround: Use Cisco Fabric Manager to configure interface-domain zones.

CSCsh71985

Symptom: The Performance Manager in Cisco Fabric Manager does not collect and report the correct Fibre Channel flow statistics.

Workaround: Download Cisco SAN-OS 3.1(2a), if you want to use the Performance Manager to manage the fabric.

CSCsh75149

Symptom: In rare situations, an upgrade to Cisco MDS SAN-OS 3.0(3) or higher may cause an MDS 9000 16-port Fibre Channel switching module to reload during the upgrade process. After the upgrade image is loaded on the module, a memory manager process reads the hardware to restore itself to its pre-upgrade state. While doing so, it finds an invalid entry in memory and then crashes while trying to process that entry. As a result, the module reloads, which clears the invalid entry and the module then comes up fully operational. However, the module reload may abort the upgrade process and the remaining modules may require manual upgrades.

You may see syslog messages similar to the following:

2007 Apr 2 11:15:35 MDS1 %IMAGE_DNLD-SLOT1-2-IMG_DNLD_STARTED: Module image
download process. Please wait until completion...
2007 Apr 2 11:15:49 MDS1 %IMAGE_DNLD-SLOT1-2-IMG_DNLD_COMPLETE: Module image
download process. Download successful.
2007 Apr 2 11:16:59 MDS1 %ACL-2-ACL_LINECARD_STATUS: Status from
linecard: 0, for module: acltcam(ID: 0), status : 0, error_id: 0x40320002,
catastrophic: FALSE, restart count: 0.
2007 Apr 2 11:17:48 MDS1 %ACL-2-ACL_LINECARD_STATUS: Status from
linecard: 0, for module: acltcam(ID: 0), status : 0, error_id: 0x40320002,
catastrophic: TRUE, restart count: 2.
2007 Apr 2 11:17:48 MDS1 %MODULE-5-MOD_REINIT: Re-initializing module 1(serial: xyz)
2007 Apr 2 11:18:07 MDS1 %PLATFORM-5-MOD_DETECT: Module 1 detected (Serial number xyz)
2007 Apr 2 11:18:07 MDS1 %PLATFORM-5-MOD_PWRUP: Module 1 powered up (Serial number xyz) ..
2007 Apr 2 11:18:53 MDS1 %MODULE-5-MOD_OK: Module 1 is online (serial: xyz)

Workaround: Upgrade to Cisco MDS SAN-OS Release 3.1(3). Alternatively, check for invalid hardware entries before attempting an upgrade. If no such entries are found, then the upgrade process will not encounter this issue. The following example shows the commands you can use to check for invalid entries on a module:

switch# attach module <module number>

module-<n># show process acltcam luxor 0 input dump | exclude e00000000000000000 | include ": e"
module-<n># show process acltcam luxor 0 input dump | exclude e00000000000000000 | include ": f"

module-<n># show process acltcam luxor 0 output dump | exclude e00000000000000000 | include ": e"

module-<n># show process acltcam luxor 0 output dump | exclude e00000000000000000 | include ": f"

module-<n># show process acltcam luxor 1 input dump | exclude e00000000000000000 | include ": e"

module-<n># show process acltcam luxor 1 input dump | exclude e00000000000000000 | include ": f"

module-<n># show process acltcam luxor 1 output dump | exclude e00000000000000000 | include ": e"

module-<n># show process acltcam luxor 1 output dump | exclude e00000000000000000 | include ": f"

CSCsh82676

Symptom: Cisco Fabric Manager may display a licensed fabric as unlicensed in the Open Fabric dialog box.

Workaround: Click the Refresh button to update the license information.

CSCsh83200

Symptom: If you remove a fan tray module from an MDS 9500 series switch that is running Cisco MDS SAN-OS Release 3.0(1), 3.0(2), 3.0(2a) 3.0(2b), 3.0(3), 3.1(1), 3.1(2) or 3.1(2a), the switch shuts down if you do not replace the fan tray module within 170 seconds. (In all other SAN-OS releases, you have 250 seconds to replace it.)

Workaround: None.

CSCsh85505

Symptom: The SNMP Getbulk request in Cisco SAN-OS 3.1(1) does not work correctly when the non-repeaters argument is set to a number other than zero. This results in an erroneous error.

Workaround: Set the non-repeaters argument to zero when issuing SNMP Getbulk requests.

CSCsh93540

Symptom: If the Fabric Manager client loses connectivity to the Fabric Manager server, the client displays the error "no such object in table." The user is then unable to manage the fabric.

Workaround: Close the Fabric Manager client and restart it.

CSCsh94906

Symptom: The export utility in Performance Manager does not work correctly in Cisco SAN-OS 3.1(2a).

Workaround: None.

CSCsi27133

Symptom: If an interface index map is not programmed correctly, the Port Manager continues to bring up the port, which results in an ACL programming failure and the following error message:

%ZONE-2-ZS_TCAM_PROGRAMMING_FAILED: %$VSAN xxx%$ TCAM operation failed : Unknown, Reason: idxmap ioctl failure

Because of the programming failure, the port is effectively useless, even though it is up.

Workaround: None.

CSCsi41668

Symptom: If there are IVR-NAT rewrite rules for FCIP interfaces on an MDS 9000 MPS-14/2 module in an IVR border switch, updates or modifications of the rewrite rules may fail after the MPS-14/2 module is upgraded to SAN-OS 3.1(2x) or lower. Stale IVR-NAT rules are left on the FCIP interfaces rather than the required IVR-NAT rules, and this impacts IVR traffic over the FCIP link.

There is no impact on traffic unless and until IVR rewrite rules need to be modified after an upgrade. However, if the IVR rewrite information changes (such as when a virtual domain ID changes) because of other events taking place in the fabric, then the stale IVR rewrite rules continue to re-write the frames entering the FCIP interface with the old rewrite information. This may result in frames with an invalid rewritten destination ID getting dropped or incorrectly forwarded in the network. Frames with a source ID that is incorrectly rewritten will eventually be rejected or incorrectly interpreted by the destination device.

Workaround: Upgrade to Cisco MDS SAN-OS Release 3.1(3). Otherwise, use one of the following workarounds:

Make sure the IVR rewrite information does not change by using an IVR static virtual domain configuration.

Plan a scheduled downtime and reload the affected 14/2-port Multiprotocol Services modules. Until then, use the previous workaround.

CSCsi56949

Symptom: When creating a new VSAN through Fabric Manager or through a script that can create a VSAN on each switch at the same time, the same domain ID is created for each switch. This causes the newly-created VSAN to be segmented on all links.

Workaround: Either create the VSAN using static domain IDs, or use the CLI to create new VSANs at different times.

CSCsj07363

Symptom: An SNMP Get-Next Request for the MIB object ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex on an MDS 9000 switch resolves by asking ifIndex for a loopback address. Because there is no hardware (ifIndex) for a loopback address, the ifIndex reply for this interface is skipped and the next possible instance of the object, which is IP-MIB::ipAdEntNetMask, is returned.

Workaround: There are two ways you can work around this issue. Do one of the following:

Use the CISCO-IP-IF-MIB, which has richer vocabulary than the standard MIB. The same information along with more details can be derived.

Use the Get-Next request in a series for ipAdEntAddr to learn about the all the address instances. Then do a series of specific Get Request requests for respective instances of ipAdEntIfIndex and ignore the loopback address.

CSCsj13175

Symptom: A fibre channel port on an MDS switching module remained out-of-service after the port was put back in service. As a result, it was not possible to configure the port.

Workaround: To put the module back in service, enter the commands shown in this example:

switch(config)# poweroff module slot-number
switch#
purge module slot-number running-config
switch(config)# no poweroff module slot-number

Configure the module again because the previous configuration will be lost.

CSCsj29134

Symptom: Following a Cisco SAN-OS software upgrade or downgrade, certain ports get stuck in link failure or in a not-connected state, even though the same SFP, cable, host, or storage device works in other ports on the same module.

Workaround: Reload the module, or contact Cisco TAC for a less disruptive workaround.

CSCsj52389

Symptom: When an fcalias is added as a zone member or a zone is added to a zone set via SNMP, there is an SNMPD memory leak.

Workaround: None.

CSCsj95379

Symptom: A data path processor (DPP) might fail on an MDS switch running Cisco SAN-OS Release 3.1(2b) with an SSM running SSI Release 3.1(2m) and with the SANTap feature provisioned. The failure occurs while the DPP is processing an unexpected transfer ready message.

Workaround: None.

CSCsk48149

Symptom: IVR zone set activation in Interop mode 4 results in a failure without an appropriate status message. This issue is seen if a successful IVR zone set activation results in more than 2047 zones in Interop mode 4. In Interop mode 4, the combined number of regular and IVR zones supported is 2047. If an IVR activation attempts to activate more than 2047 zones, the activation is rejected by the zone server module. An appropriate status message is not conveyed back to IVR.

Workaround: None.

CSCso63465

Symptom: FCP-CMD (for example, Inquiry) frames targeted to LUN 0x45F0 or LUN 0x50F0 are dropped by an MDS switch when traffic flows (egresses) thru Generation 2 modules. LUN 0x45F0 corresponds to HPUX's Volume Set Address <VBUS ID: 0xB, Target ID: 0xE, LUN: 0x0>.

Workaround: Do not use LUN 0x45F0 and LUN 0x50F0 when Generation 2 modules are present in the fabric.

CSCsh86629

Symptom: The RMON 64-bit alarms table can show large values as negative numbers.

Workaround: None.

CSCsi52049

Symptom: When enhanced zoning is enabled, an empty pop-up window displays in Fabric Manager after a zone set activation completes.

Workaround: None.

CSCeh35635

Symptom: For passwords authenticated by an AAA server, the MDS switch should inform the user when their password is about to expire.

Workaround: This is an enhancement. It is available only for CLI logins. Fabric Manager and Device currently do not support this feature.

CSCsg29630

Symptom: During a Fabric Manager upgrade, the following files were not preserved: AAA.properties and emccallhome.properties.

Workaround: None.

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 this URL: http://www.cisco.com/en/US/customer/products/ps5989/products_documentation_roadmap09186a00804500c1.html
For information on IBM TotalStorage SAN Volume Controller Storage Software for the Cisco MDS 9000 Family, refer to the IBM TotalStorage Support website: http://www.ibm.com/storage/support/2062-2300/

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 SVC Releases

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 Storage Services Module 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 9124 Multilayer Fabric Switch Quick Start Guide

Cisco MDS 9500 Series Hardware Installation Guide

Cisco MDS 9200 Series Hardware Installation Guide

Cisco MDS 9100 Series Hardware Installation 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

Cisco MDS 9000 Family Fabric Manager Database Schema

Command-Line Interface

Cisco MDS 9000 Family Software Upgrade and Downgrade Guide

Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade 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

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

Cisco 10-Gigabit Fibre Channel X2 Transceiver Module Installation Note

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:

http://www.cisco.com/univercd/home/home.htm

The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:

http://www.cisco.com/go/marketplace/docstore

Ordering Documentation

You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:

http://www.cisco.com/go/marketplace/docstore

If you do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Documentation Feedback

You can provide feedback about Cisco technical documentation on the Cisco Technical Support & Documentation site area by entering your comments in the feedback form available in every online document.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to do the following:

Report security vulnerabilities in Cisco products

Obtain assistance with security incidents that involve Cisco products

Register to receive security information from Cisco

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For emergencies only — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.


Product Alerts and Field Notices

Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.

To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en

Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification Tool to locate your product serial number before submitting a request for service online or by phone. You can access this tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link, clicking the All Tools (A-Z) tab, and then choosing Cisco Product Identification Tool from the alphabetical list. This tool offers three search options: by product ID or model name; by tree view; or, for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.



Tip Displaying and Searching on Cisco.com

If you suspect that the browser is not refreshing a web page, force the browser to update the web page by holding down the Ctrl key while pressing F5.

To find technical information, narrow your search to look in technical documentation, not the entire Cisco.com website. On the Cisco.com home page, click the Advanced Search link under the Search box and then click the Technical Support & Documentation radio button.

To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411
Australia: 1 800 805 227
EMEA: +32 2 704 55 55
USA: 1 800 553 2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—An existing network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Online Subscription Center is the website where you can sign up for a variety of Cisco e-mail newsletters and other communications. Create a profile and then select the subscriptions that you would like to receive. To visit the Cisco Online Subscription Center, go to this URL:

http://www.cisco.com/offer/subscribe

The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco channel product offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

http://www.cisco.com/go/guide

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training, and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

Networking Professionals Connection is an interactive website where networking professionals share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

"What's New in Cisco Documentation" is an online publication that provides information about the latest documentation releases for Cisco products. Updated monthly, this online publication is organized by product category to direct you quickly to the documentation for your products. You can view the latest release of "What's New in Cisco Documentation" at this URL:

http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html