Guest

Cisco MDS 9000 SAN-OS Software

Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.0(3)

Table Of Contents

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

Contents

Introduction

System Requirements

Components Supported

Determining the Software Version

Downloading Software

Upgrading Your Cisco MDS SAN-OS Software Image

Performing a Nondisruptive Software Upgrade on Generation 1 Modules

Upgrading with IVR Enabled

Selecting the Correct Software Image for an MDS 9500 Series Switch

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

Migrating from Supervisor-1 Modules to Supervisor-2 Modules

Configuring Generation 2 Switching Modules

Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch

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

Limitations and Restrictions

Downgrading from Cisco MDS SAN-OS Release 3.0(2b)

Downgrading from Cisco SAN-OS Release 3.2(1)

iSNS

Reconfiguring SSM Ports

CWDM SFPs

Maximum Number of Zones Supported in Interop Mode 4

Configuring Default Settings for the Default Zone

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


Release Date: January 22, 2007

Text Part Number: OL-8795-05 N0

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 on-line change history for this document.

Table 1 Online History Change

Revision
Date
Description

A0

01/22/2007

Created release notes

B0

02/01/2007

Added DDTS CSCsg03171.

C0

02/12/2007

Changed the state of DDTS CSCse67109 to Resolved.

D0

02/21/2007

Added DDTS CSCsd97376, CSCse99087, CSCsf27608, CSCsf30937, CSCsg05037, CSCsg12096, CSCsg29400, CSCsg31334, CSCsg35972, CSCsg52197, CSCsg62359, CSCsg80637, CSCsg82792, CSCsg94749, CSCsg96497, CSCsg99049, CSCsh27840, and CSCsh31236.

E0

02/27/2007

Added DDTS CSCsg72224, CSCsh40033, and CSCsh60422.

F0

04/04/2007

Added DDTS CSCsh66010 and CSCsh83200.

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

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

G0

06/11/2007

Added DDTS CSCsg41556, CSCsh24256, CSCsi27133, and CSCsi33540.

H0

07/18/2007

Added DDTS CSCsj07363 and CSCsj19105.

Removed DDTS CSCei82909.

I0

08/24/2007

Added DDTS CSCsg18834.

J0

09/28/2007

Added DDTS CSCeh35635, CSCsi49231, and CSCsj65565.

K0

10/23/2007

Removed DDTS CSCsh31236.

Added information about downgrading from Cisco SAN-OS Release 3.2(1) to the "Limitations and Restrictions" section.

L0

04/30/2008

Added DDTS CSCso63465.

M0

11/13/2008

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

N0

11/18/2008

Added DDTS CSCso72230.


Contents

This document includes the following sections:

Introduction

System Requirements

Upgrading Your Cisco MDS SAN-OS Software Image

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

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.

System Requirements

This section describes the system requirements for Cisco MDS SAN-OS Release 3.0(2b) and includes the following topics:

Components Supported

Determining the Software Version

Downloading Software

Components Supported

Table 2 lists the software 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.0.2b

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

MDS 9500 Series only

M95S1K9-3.0.2b

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

MDS 9500 Series only

M92S1K9-3.0.2b

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

MDS 9200 Series only

M91S1K9-3.0.2b

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

MDS 9100 Series only

License

M9500ENT1K9

Enterprise package.

MDS 9500 Series

M9200ENT1K9

Enterprise package.

MDS 9200 Series

M9100ENT1K9

Enterprise package.

MDS 9100 Series

M9500FIC1K9

Mainframe package.

MDS 9500 Series

M9200FIC1K9

Mainframe package.

MDS 9200 Series

M9100FIC1K9

Mainframe package.

MDS 9100 Series

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

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

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

MDS 9120 only

External
crossbar module

DS-13SLT-FAB1

MDS 9513 Crossbar Fabric Module

MDS 9513 only

Supervisor modules

DS-X9530-SF2-K9

MDS 9500 Supervisor-2, module.

MDS 9500 Series only

DS-X9530-SF1-K9

MDS 9500 Supervisor/Fabric-I module.

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 wavelength mode.

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

DS-X2-FC10G-LR

X2/SC optics, 10-Gbps Fibre Channel for long wavelength mode.

LC-type fiber-optic SFP

DS-SFP-FC-2G-SW2

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

MDS 9000 Family

DS-SFP-FC-2G-LW2

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

DS-SFP-FCGE-SW2

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

DS-SFP-FCGE-LW2

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

DS-SFP-GE-T2

1-Gbps Ethernet SFP.

DS-SFP-FC4G-SW3

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

DS-SFP-FC4G-MR3

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

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

CWDM4

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-W5 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 Supported on the DS-X9530-SF1-K9, MDS 9500 Series Supervisor module only

3 Supported on the DS-X9530-SF2-K9, MDS 9500 Series Supervisor-2 module only

4 CWDM = coarse wavelength division multiplexing

5 W = Watt


Determining the Software Version


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


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.

Downloading Software

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

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

Upgrading Your Cisco MDS SAN-OS Software Image

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.


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.


Use the following guidelines to nondisruptively upgrade your Cisco MDS SAN-OS Release 3.0(2b):

Install and configure dual supervisor modules.

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.

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

Follow this upgrade path for your current release:

Upgrading from Cisco SAN-OS Release 1.x to Release 3.x requires that you upgrade first to Release 1.3(4a), then upgrade to Release 2.1(2b), and then upgrade to Release 3.0(2b) .

Upgrading from Cisco SAN-OS Release 2.0(2b), 2.0(2c), 2.0(3), 2.1(2b), 2.1(2c), 2.1(2d), 2.1(2e), or 3.0(1) allows you to nondisruptively upgrade directly to Release 3.0(2b). If you do not have one of these releases installed, you must upgrade first to Cisco SAN-OS Release 2.1(2b) and then upgrade to Release 3.0(2b).

Upgrading from other Cisco SAN-OS Release 2.x releases to Release 3.x requires that you upgrade first to Release 2.1(2b), and then upgrade to Release 3.0(2b).

If you have IVR enabled and you are upgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a), then there are additional steps you should follow before upgrading. See "Upgrading with IVR Enabled" section.

If you have FICON enabled and you are upgrading from Cisco SAN-OS Release 1.x to Release 3.x then first upgrade to Release 1.3(4a), then upgrade to Release 2.0(2b), and then upgrade to Release 3.0(2b).

The traffic on all 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. This impacts those nodes that are members of VSANs traversing an FCIP ISL and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the upgrade is in progress.

Layer 3 switching on SSM ports is disrupted during upgrades or downgrades. Layer 2 switching 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.0(2b)" 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.

Use the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive.


Caution Upgrading to Cisco MDS SAN-OS Release 2.1(2) or later from any release can disrupt traffic on any SSM installed on your MDS switch.


Note Upgrading from Cisco MDS SAN-OS Release 1.x directly to Cisco SAN-OS Release 3.x is disruptive to all Fibre Channel and Gigabit Ethernet ports.



Note For more information on determining software compatibility, 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 CompactFlash 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 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 running might be disruptive. Some possible scenarios include:

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 RDI failure and the flapped ISL could remain in a down state because of a domain overlap. This is caused by conflicts between the allowed domains list and the virtual domain requested through RDI.

This issue was resolved in an earlier release, however upgrades from Cisco SAN-OS Release 2.1(1a), 2.1(1b), or 2.1(2a) to Release 3.0(2b) when IVR is enabled requires that you use the following workaround.

For VSANS in interop mode 2 or 3, issue an IVR refresh, and then follow the upgrade guidelines listed in "Upgrading Your Cisco MDS SAN-OS Software Image" section.

To upgrade from Cisco SAN-OS Release 2.1(1a), 2.1(1b), or 2.1(2a) to Release 3.0(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 3.0(2b) in the "Upgrading Your Cisco MDS SAN-OS Software Image" section.


If you are adding new switches running Cisco MDS SAN-OS Release 3.0(x), upgrade all your existing switches to Release 3.0(2b) as described in this procedure. Then add new switches.


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


Selecting the Correct Software Image for an MDS 9500 Series Switch

The system and kickstart image that you use for an MDS 9500 Series switch depends on whether the switch is based on a Supervisor-1 module or a Supervisor-2 module, as shown in Table 3.

Table 3 Software Image for Supervisor Type

Supervisor Type
Switch
Image

Supervisor-1 module

MDS 9506 and 9509

Filename begins with m9500-sf1ek9

Supervisor-2 module

MDS 9506, 9509, and 9513

Filename begins with m9500-sf2ek9


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

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

Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode. Because auto mode is the default for releases prior to Release 3.0(1), you should modify the configuration of the ports before upgrading a SAN-OS software image prior to Release 3.0(1) to Release 3.0(2b) to avoid any traffic disruption.

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 might cause a disruption if the port is currently operating in E mode.

To make the configuration change 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 Fx if the current operational port mode is 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. If the admin port mode of these ports is auto or E, change the admin port mode to Fx.

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

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

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 listed in this section, 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.

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

This section describes the new features introduced in this release. For more 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.


There are no new features available for this release.

Limitations and Restrictions

This section lists the limitations and restrictions for this release.

Downgrading from Cisco MDS SAN-OS Release 3.0(2b)

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

Install and configure dual supervisor modules.

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.

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.

Follow the downgrade path for your current release:

Downgrading to Cisco SAN-OS Release 1.x from Release 3.x requires that you downgrade first to Release 2.1(2b), then downgrade to Release 1.3(4a), and then downgrade to your 1.x release.

You can downgrade nondisruptively from Release 3.x to the following releases: 2.0(2b), 2.0(2c), 2.0(3), 2.1(2b), 2.1(2c), 2.1(2d), 2.1(2e), or 3.0(1). Downgrading to other Cisco SAN-OS Release 2.x releases from Release 3.x requires that you downgrade first to Release 2.1(2b) and then downgrade to an earlier 2.x release.

Downgrading for FICON to Cisco SAN-OS Release 1.x from Release 3.x requires that you downgrade first to Release 2.0(2b), then downgrade to Release 1.3(4a), and then downgrade to your 1.x release.

Traffic on all Gigabit Ethernet ports is disrupted on an upgrade or downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module. This impacts those nodes that are members of VSANs traversing an FCIP ISL or iSCSI initiators connected to the Gigabit Ethernet ports.

Enable iSCSI if an IPS module or an MPS-14/2 module is online in the switch. Otherwise, the downgrade will disrupt traffic.

Layer 3 switching on SSM ports is disrupted on upgrades or downgrades.

Layer 2 switching 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.

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.

Downgrading from Cisco SAN-OS Release 3.2(1)

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

iSNS

The iSNS client and server are not supported in this release.

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

CWDM SFPs

Some 2-Gbps CWDM SFPs do not have have speed capability encoded in EEPROM memory and they could negotiate and obtain synchronization up to 4-Gbps on modules that support 4-Gbps 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 fixed to 1- or 2-Gbps instead of Auto.

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 interop mode 4, the maximum number of zones supported, including IVR zones, in the active zone set is 2047. The limit for the maximum number of IVR zones per VSAN is 250 zones (two members per zone).

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.

Caveats

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

Table 4 Open Caveats and Resolved Caveats Reference 

DDTS Number
Software Release (Open or Resolved)
3.0(2a)
3.0(2b)

Severity 2

CSCec28084

O

O

CSCsc45880

O

O

CSCsd47064

O

O

CSCsd97376

O

O

CSCse35720

O

O

CSCse44834

O

O

CSCse57269

O

O

CSCse65400

O

O

CSCse67109

O

R

CSCse72182

O

O

CSCse85609

O

R

CSCsf18884

O

O

CSCsf18884

O

O

CSCsf21575

O

O

CSCsf30937

O

O

CSCsf98427

O

O

CSCsg01963

O

O

CSCsg35972

O

O

CSCsg37901

O

R

CSCsg72224

O

O

CSCsg93617

O

R

CSCsh25050

O

R

CSCsh27840

O

O

CSCsi33540

O

O

CSCsi49231

O

O

CSCsj19105

O

O

CSCsj65565

O

O

CSCso72230

O

O

Severity 3

CSCin95789

O

O

CSCsc95657

O

O

CSCsd15794

O

O

CSCsd19272

O

O

CSCsd21187

O

O

CSCsd51194

O

O

CSCsd52037

O

O

CSCsd79938

O

O

CSCsd81137

O

O

CSCsd89872

O

O

CSCsd99599

O

O

CSCse12209

O

O

CSCse22145

O

O

CSCse31881

O

O

CSCse41442

O

O

CSCse42040

O

O

CSCse48977

O

O

CSCse52582

O

O

CSCse62012

O

O

CSCse69783

O

O

CSCse70275

O

O

CSCse71420

O

O

CSCse79582

O

O

CSCse88606

O

O

CSCse88880

O

O

CSCse93991

O

O

CSCse98656

O

O

CSCse99087

O

O

CSCsf12069

O

O

CSCsf18552

O

O

CSCsf19419

O

O

CSCsf27608

O

O

CSCsf96043

O

O

CSCsf97117

O

O

CSCsg03171

O

O

CSCsg05037

O

O

CSCsg10555

O

O

CSCsg12020

O

O

CSCsg12096

O

O

CSCsg13769

O

O

CSCsg15392

O

O

CSCsg18834

O

O

CSCsg19198

O

O

CSCsg29400

O

O

CSCsg41556

O

O

CSCsg52197

O

O

CSCsg62359

O

O

CSCsg80637

O

O

CSCsg82792

O

O

CSCsg94749

O

O

CSCsg96497

O

O

CSCsg99049

O

O

CSCsh24256

O

O

CSCsh40033

O

O

CSCsh60422

-

O

CSCsh66010

O

O

CSCsh83200

O

O

CSCsi27133

O

O

CSCsj07363

O

O

CSCso63465

O

O

Severity 4

CSCsg31334

O

O