Cisco SN6000C, Cisco MDS 8/24c, MDS 9513, MDS 9509, MDS 9506 Release Note

...

Send documentation comments to mdsfeedback-doc@cisco.com

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Release Date: January 13, 2011

Part Number: OL-21012-04 B0

This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the “Related Documentation” section on page 37.

Note As of Cisco Fabric Manager Release 4.2(1a), Fabric Manager information will no longer appear in the

Cisco MDS 9000 Family Release Notes for NX-OS releases. Cisco Fabric Manager Release Notes will include information that is exclusive to Fabric Manager as a management tool for Cisco MDS 9000 Family switches and Cisco Nexus 5000 Series switches. Refer to the following website for Release Notes for Cisco Fabric Manager:

http://www.cisco.com/en/US/partner/products/ps10495/prod_release_notes_list.html

Contents

Release notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Notes:

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

Table 1 shows the on-line change history for this document.

Table 1 Online History Change

Revision Date Description

A0 01/132011 Created release notes.

B0 02/09/2011 Updated the “Licensed Cisco NX-OS Software Packages”

section.

This document includes the following:

• Introduction, page 2

Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Introduction

Send documentation comments to mdsfeedback-doc@cisco.com

• Components Supported, page 3

• MDS 9000 Chassis and Module Support, page 9

• Migrating from Supervisor-1 Modules to Supervisor-2 Modules, page 12

• Software Download Process, page 12

• Upgrading Your Cisco MDS NX-OS Software Image, page 15

• Downgrading Your Cisco MDS SAN-OS Software Image, page 21

• New Features in Cisco MDS NX-OS Release 5.0(4b), page 25

• Licensed Cisco NX-OS Software Packages, page 26

• Limitations and Restrictions, page 27

• Caveats, page 34

• Related Documentation, page 37

• Obtaining Documentation and Submitting a Service Request, page 39

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.

Cisco MDS 9000 NX-OS Software powers the award winning Cisco MDS 9000 Series Multilayer Switches. It is designed to create a strategic SAN platform with superior reliability, performance, scalability, and features. Formerly known as Cisco SAN-OS, Cisco MDS 9000 NX Software is fully interoperable with earlier Cisco SAN-OS versions and enhances hardware platform and module support.

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Components Supported

Send documentation comments to mdsfeedback-doc@cisco.com

Components Supported

Table 2 lists the NX-OS software part numbers 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-5.0.4b MDS 9500 Supervisor/Fabric-2, NX-OS software MDS 9500 Series only

M92S2K9-5.0.4b MDS 9200 Supervisor/Fabric-2, NX-OS software MDS 9222i Switch only

M91S2K9-5.0.4b MDS 9100 Supervisor/Fabric-2, NX-OS software MDS 9124 Switch and

MDS 9134 Switch

M91S3K9-5.0.4b MDS 9148 Supervisor/Fabric-3 NX-OS software MDS 9148 Switch

SSI Interface SSI-M9K9-504b Storage Services Interface for NX-OS Release 5.0(4b) MDS 9000 Family

Licenses M9500SSE184K9 Storage Services Enabler License for one MSM-18/4 module MDS 9500 Series only

M9222ISSE1K9 Storage Services Enabler License MDS 9222i Switch only

M9200SSE184K9 Storage Services Enabler License for one MSM-18/4 module MDS 9200 Series only

M95DMM184K9 Data Mobility Manager License for one MSM-18/4 module MDS 9500 Series only

M9222IDMMK9 Data Mobility Manager License for Cisco MDS 9222i MDS 9222i Switch

M92DMM184K9 Data Mobility Manager License for one MSM-18/4 module MDS 9200 Series only

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Components Supported

Send documentation comments to mdsfeedback-doc@cisco.com

Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)

Component Part Number Description Applicable Product

Licenses (continued)

M95DMM184TSK9 Data Mobility Manager for one MSM-18/4 module — Time

MDS 9500 Series only

Limited to 180 days only

M9222IDMMTSK9 Data Mobility Manager — Time Limited to 180 days only MDS 9222i Switch only

M92DMM184TSK9 Data Mobility Manager for one MSM-18/4 module — Time

MDS 9200 Series only

Limited to 180 days only

M92SSESSNK9 Cisco Storage Services Enabler License for SSN-16

MDS 9200 Series only

(1 engine)

M95SSESSNK9 Cisco Storage Services Enabler License for SSN-16

MDS 9500 Series only

(1 engine)

M92SMESSNK9 Cisco Storage Media Encryption License for SSN-16

MDS 9200 Series only

(1 engine)

M95SMESSNK9 Cisco Storage Media Encryption License for SSN-16

MDS 9500 Series only

(1 engine)

M92IOASSN Cisco I/O Accelerator License for SSN-16 (1 engine) MDS 9200 Series only

M95IOASSN Cisco I/O Accelerator License for SSN-16 (1 engine) MDS 9500 Series only

M92IOA184 Cisco I/O Accelerator License for MSM-18/4 MDS 9200 Series only

M95IOA184 Cisco I/O Accelerator License for MSM-18/4 MDS 9500 Series only

M9222IIOA Cisco I/O Accelerator License for Cisco MDS 9222i base

MDS 9222i Switch only

switch

M92EXTSSNK9 Cisco SAN Extension License for SSN-16 (1 engine) MDS 9200 Series only

M95EXTSSNK9 Cisco SAN Extension License for SSN-16 (1 engine) MDS 9500 Series only

M9200XRC Cisco XRC Acceleration MDS 9200 Series only

M9500XRC Cisco XRC Acceleration MDS 9500 Series only

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Components Supported

Send documentation comments to mdsfeedback-doc@cisco.com

Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)

Component Part Number Description Applicable Product

Chassis DS-C9513 Cisco MDS 9513 Multilayer Director (13-slot multilayer

director with 2 slots for Supervisor-2 modules, with 11 slots available for switching modules — SFPs sold separately)

DS-C9509 Cisco MDS 9509 Multilayer Director (9-slot multilayer

director with 2 slots for Supervisor modules, with 7 slots available for switching modules — SFPs sold separately)

DS-C9506 Cisco MDS 9506 Multilayer Director (6-slot multilayer

director with 2 slots for Supervisor modules, with 4 slots available for switching modules — SFPs sold separately)

DS-C9222i-K9 Cisco MDS 9222i Multilayer Fabric Switch (3-rack-unit

(3RU) semimodular multilayer fabric switch with 18 4-Gbps Fibre Channel ports, 4 Gigabit Ethernet ports, and a modular expansion slot for Cisco MDS 9000 Family Switching and Services modules)

DS-C9148-K9 Cisco MDS 9148 48-Port Multilayer Fabric Switch (1RU

fixed-configuration multilayer fabric switch with 48 8-Gbps Fibre Channel ports)

DS-C9134-K9 Cisco MDS 9134 34-Port Multilayer Fabric Switch (1RU

fixed-configuration multilayer fabric switch with 32 4-Gbps and 2 10-Gbps Fibre Channel ports)

DS-C9124-K9 Cisco MDS 9124 24-Port Multilayer Fabric Switch (1RU

fixed-configuration multilayer fabric switch with 24 4-Gbps Fibre Channel ports)

Supervisor Modules

Switching Modules

DS-X9530-SF2-K9 Cisco MDS 9500 Series Supervisor-2 Module MDS 9500 Series

DS-X9530-SF2A-K9 Cisco MDS 9500 Series Supervisor-2A Module MDS 9500 Series

DS-X9112 Cisco MDS 9000 12-port 4-Gbps Fibre Channel Switching

Module with SFP LC connectors

DS-X9124 Cisco 24-port 4-Gbps Fibre Channel Switching Module with

SFP LC connectors

DS-X9148 Cisco MDS 9000 48-port 4-Gbps Fibre Channel Switching

Module with SFP LC

DS-X9704 Cisco MDS 9000 Family 4-Port 10-Gbps Fibre Channel

Switching Module with SFP LC

DS-X9224-96K9 Cisco MDS 9000 24-Port 8-Gbps Fibre Channel Switching

Module with SFP and SFP+ LC connectors

DS-X9248-96K9 Cisco MDS 9000 48-Port 8-Gbps Fibre Channel Switching

Module with SFP and SFP+ LC connectors

DS-X9248-48K9 Cisco MDS 9000 4/44-Port Host-Optimized 8-Gbps Fibre

Channel Switching Module with SFP and SFP+ LC connectors

MDS 9513 Switch

MDS 9509 Switch

MDS 9506 Switch

MDS 9222i Switch

MDS 9148 Switch

MDS 9134 Switch

MDS 9124 Switch

MDS 9500 Series

MDS 9200 Series

MDS 9500 Series

MDS 9200 Series

MDS 9500 Series

MdS 9200 Series

MDS 9500 Series

MDS 9200 Series

MDS 9500 Series

MDS 9222i Switch

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Components Supported

Send documentation comments to mdsfeedback-doc@cisco.com

Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)

Component Part Number Description Applicable Product

Services Modules

DS-X9316-SSNK9 Cisco MDS 9000 Family 16-Port Storage Services Node

(SSN-16) — 16 fixed 1-Gbps Ethernet ports, plus 4 service engines that support 16 Gigabit Ethernet IP storage services ports.

DS-X9304-18K9 Cisco MDS 9000 18/4-Port Multiservice Module

(MSM-18/4) — 18-port, 4-Gbps Fibre Channel plus 4-port Gigabit Ethernet IP services and switching module with SFP LC connectors

External crossbar module

DS-13SLT-FAB1 Cisco MDS 9513 Switching Fabric1 Module MDS 9513 Switch

DS-13SLT-FAB2 Cisco MDS 9513 Switching Fabric2 Module MDS 9513 Switch

Optics DS-X2-FC10G-SR X2 SC optics, 10-Gbps Fibre Channel for short reach MDS 9500 Series

DS-X2-FC10G-LR X2 SC optics, 10-Gbps Fibre Channel for long reach (10 km) MDS 9500 Series

DS-X2-FC10G-ER X2 SC optics, 10-Gbps Fibre Channel for extended reach (40

km)

DS-X2-FC10G-CX4 X2 SC optics, 10-Gbps Fibre Channel over copper MDS 9500 Series

DS-X2-E10G-SR X2 SC optics, 10-Gbps Ethernet for short reach MDS 9500 Series

MDS 9500 Series

MDS 9222i Switch

MDS 9500 Series

MDS 9200 Series

MDS 9200 Series MDS 9134 Switch

MDS 9500 Series MDS 9200 Series MDS 9134 Switch

MDS 9200 Series MDS 9134 Switch

MDS 9200 Series

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Components Supported

Send documentation comments to mdsfeedback-doc@cisco.com

Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)

Component Part Number Description Applicable Product

LC-type fiber-optic SFP

Cisco Coarse WavelengthDivision Multiplexing (CWDM)

DS-SFP-FC8G-SW SFP+ optics (LC type) for 2-, 4-, or 8-Gbps Fibre Channel for

shortwave mode

DS-SFP-FC8G-LW SFP+ optics (LC type) for 2-, 4-, or 8-Gbps Fibre Channel for

longwave mode; supports distances up to 10 km

DS-SFP-FC4G-SW SFP optics (LC type) for 1-, 2-, or 4-Gbps Fibre Channel for

shortwave mode

MDS DS-X9200 Series switching modules

MDS 9124, MDS 9134, MDS 9222i, DS-X9100, and DS-X9200 Series switching modules

DS-SFP-FC4G-MR SFP optics (LC type) for 1-, 2-, or 4-Gbps Fibre Channel for

longwave mode; supports distances up to 4 km

MDS 9124, MDS 9134, MDS 9222i, DS-X9100, and DS-X9200 Series switching modules

DS-SFP-FC4G-LW SFP optics (LC type) for 1-, 2-, or 4-Gbps Fibre Channel for

longwave mode; supports distances up to 10 km

MDS 9124, MDS 9134, MDS 9222i, DS-X9100, and DS-X9200 Series switching modules

DS-SFP-FC-2G-SW SFP optics (LC type) for 1- or 2-Gbps Fibre Channel for

MDS 9000 Series shortwave mode; not supported for use in 4-Gbps-capable ports

DS-SFP-FC-2G-LW SFP optics (LC type) for 1- or 2-Gbps Fibre Channel for

MDS 9000 Series longwave mode for Cisco MDS 9500, MDS 9200, and MDS 9100 Series; not supported for use in 4-Gbps-capable ports

DS-SFP-FCGE-SW SFP optics (LC type) for 1-Gbps Ethernet and 1- or 2-Gbps

MDS 9000 Series Fibre Channel for shortwave mode; not supported for use in 4-Gbps-capable ports

DS-SFP-FCGE-LW SFP optics (LC type) for 1-Gbps Ethernet and 1- or 2-Gbps

MDS 9000 Series Fibre Channel for longwave mode; not supported for use in 4-Gbps-capable ports

DS-SFP-GE-T SFP (RJ-45 connector) for Gigabit Ethernet over copper MDS 9000 Series

DS-CWDM-xxxx CWDM Gigabit Ethernet and 1- or 2-Gbps Fibre Channel

MDS 9000 Family SFP LC type, where product number xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm

DS-CWDM4Gxxxx CWDM 4-Gbps Fibre Channel SFP LC type, where product

MDS 9000 Family number xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Components Supported

Send documentation comments to mdsfeedback-doc@cisco.com

Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components (continued)

Component Part Number Description Applicable Product

Dense WavelengthDivision Multiplexing (DWDM)

DWDM-X2-xx.xx DWDM X2 SC optics for 10-Gbps Fibre Channel

connectivity to an existing Ethernet DWDM infrastructure, with 15xx.xx nm wavelength, where xx.xx = 60.61, 59.79,

58.98, 58.17, 56.55, 55.75, 54.94, 54.13, 52.52, 51.72, 50.92,

50.12, 48.51, 47.72, 46.92, 46.12, 44.53, 43.73, 42.94, 42.14,

40.56, 39.77, 38.98, 38.19, 36.61, 35.82, 35.04, 34.25, 32.68,

31.90, 31.12, or 30.33

DWDM-SFP-xxxx DWDM Gigabit Ethernet and 1- or 2-Gbps Fibre Channel

SFP LC type, where product number xxxx = 3033, 3112, 3190, 3268, 3425, 3504, 3582, 3661, 3819, 3898, 3977, 4056, 4214, 4294, 4373, 4453, 4612, 4692, 4772, 4851, 5012, 5092, 5172, 5252, 5413, 5494, 5575, 5655, 5817, 5898, 5979, or 6061nm

Add/Drop Multiplexer (ADM)

DS-CWDMOADM4A4-channel CWDM optical ADM (OADM) module (Cisco

CWDM 1470, 1490, 1510, or 1530 NM Add/Drop Module)

DS-CWDMOADM4B4-channel CWDM OADM module (Cisco CWDM 1550,

1570, 1590, or 1610 NM Add/Drop Module)

DS-CWDM-MUX8A ADM for 8 CWDM wavelengths MDS 9000 Family

CWDM

DS-CWDMCHASSIS2-slot chassis for CWDM ADMs MDS 9000 Family Multiplexer Chassis

Power Supplies

DS-CAC-300W 300W AC power supply MDS 9100 Series

DS-C24-300AC 300W AC power supply MDS 9124 Switch

DS-CAC-845W 845W AC power supply for Cisco MDS 9200 Series MDS9200 Series

DS-CAC-3000W 3000W AC power supply for Cisco MDS 9509 MDS 9509 Switch

DS-CAC-2500W 2500W AC power supply MDS 9509 Switch

DS-CDC-2500W 2500W DC power supply MDS 9509 Switch

DS-CAC-6000W 6000W AC power supply for Cisco MDS 9513 MDS 9513 Switch

DS-CAC-1900W 1900W AC power supply for Cisco MDS 9506 MDS 9506 Switch

CompactFlash MEM-MDS-FLD512MExternal 512-MB CompactFlash memory for supervisor

module

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

Smart Card

DS-SCR-K9 Storage Media Encryption (SME) Smart Card Reader MDS 9000 Family Reader

Smart Card DS-SC-K9 SME Smart Card MDS 9000 Family

CD-ROM M90FM-CD-441 Cisco MDS 9000 Management Software and Documentation

CD-ROM for Cisco MDS 9000 NX-OS Software Release

4.1(3a)

MDS 9500 Series

MDS 9200 Series

MDS 9000 Family

MDS 9500 Series

MDS 9000 Family

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

MDS 9000 Chassis and Module Support

Send documentation comments to mdsfeedback-doc@cisco.com

MDS 9000 Chassis and Module Support

Table 3 lists the MDS hardware chassis supported by Cisco MDS NX-OS 5.x.

Table 3 Cisco MDS NX-OS 5.x Chassis Support Matrix

Switch NX-OS 5.x Support

MDS 9513 Yes

MDS 9509 Yes

MDS 9506 Yes

MDS 9222i Yes

MDS 9148 Yes

MDS 9134 Yes

MD S 9124 Yes

Cisco Fabric Switch for HP c-Class BladeSystem and Cisco Fabric Switch for IBM BladeCenter

Yes

Note As of Cisco MDS NX-OS Release 5.0(1a), support for the MDS 9216i switch is discontinued.

Table 4 lists the MDS hardware modules supported by Cisco MDS NX-OS 5.x. For the list of MDS

hardware modules supported by Cisco MDS SAN-OS 4.x, see Table 5. For the list of MDS hardware modules supported by Cisco MDS SAN-OS 3.x, see Table 6.

Note As of Cisco MDS NX-OS Release 5.0(1a), support for the following Generation 1 modules is

discontinued:

• DS-X9302-14K9, 14/2-port Multiprotocol Services (MPS-14/2) Module

• DS-X9016, 16-port 1-, 2-Gbps Fibre Channel Switching Module

• DS-X9032, 32-port 1-, 2-Gbps Fibre Channel Switching Module

• DS-X9032SSM, 32-port Storage Services Module (SSM)

Generation 1 modules should be removed from a switch chassis before the installation of NX-OS Release

5.0(4b) begins.

Table 4 Module Support Matrix for Cisco MDS NX-OS 5.x

Module Description MDS 9500 Series MDS 9222i

DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes N/A

DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes N/A

DS-13SLT-FAB2 MDS 9513 Fabric Module 2 Yes N/A

DS-13SLT-FAB1 MDS 9513 Fabric Module 1 Yes N/A

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

MDS 9000 Chassis and Module Support

Send documentation comments to mdsfeedback-doc@cisco.com

Table 4 Module Support Matrix for Cisco MDS NX-OS 5.x (continued)

Module Description MDS 9500 Series MDS 9222i

DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching

Module

DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching

Module

DS-X9248-48K9 4/44-port Host Optimized8-Gbps Fibre

Channel Switching Module

DS-X9316-SSNK9 16-port Storage Services Node (SSN-16) Yes Yes

DS-X9304-18K9 18/4-Port Multiservice Module (MSM-18/4) Yes Yes

DS-X9112 12-port 4-Gbps Fibre Channel Switching

Module

DS-X9124 24-port 4-Gbps Fibre Channel Switching

Module

DS-X9148 48-port 4-Gbps Fibre Channel Switching

Module

DS-X9704 4-port 10-Gbps Fibre Channel Switching

Module

1. Requires DS-13SLT-FAB2 in the MDS 9513.

Yes

Yes Yes

Table 5 lists the MDS hardware modules supported by Cisco MDS NX-OS 4.x. For the list of MDS

hardware modules supported by Cisco MDS SAN-OS 3.x, see Table 6.

Table 5 Module Support Matrix for Cisco MDS NX-OS 4.x

Module Description MDS 9500 Series MDS 9222i MDS 9216i

DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes N/A N/A

DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes

N/A N/A

DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module No N/A N/A

DS-13SLT-FAB2 MDS 9513 Fabric Module 2 Yes N/A N/A

DS-13SLT-FAB1 MDS 9513 Fabric Module 1 Yes N/A N/A

DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching Module Yes

DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching Module Yes

DS-X9248-48K9 4/44-port Host Optimized8-Gbps Fibre Channel

No No

Yes Yes No

Switching Module

DS-X9316-SSNK9 16-port Storage Services Node (SSN-16) Yes Yes Yes

DS-X9304-18K9 18/4-Port Multiservice Module (MSM-18/4) Yes Yes Yes

DS-X9112 12-port 4-Gbps Fibre Channel Switching Module Yes Yes Yes

DS-X9124 24-port 4-Gbps Fibre Channel Switching Module Yes Yes Yes

DS-X9148 48-port 4-Gbps Fibre Channel Switching Module Yes Yes Yes

DS-X9704 4-port 10-Gbps Fibre Channel Switching Module Yes Yes Yes

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

MDS 9000 Chassis and Module Support

Send documentation comments to mdsfeedback-doc@cisco.com

Table 5 Module Support Matrix for Cisco MDS NX-OS 4.x (continued)

Module Description MDS 9500 Series MDS 9222i MDS 9216i

DS-X9302-14K9 14/2-port Multiprotocol Services (MPS-14/2)

Module

DS-X9016 16-port 1-, 2-Gbps Fibre Channel Switching

Module

DS-X9032 32-port 1-, 2-Gbps Fibre Channel Switching

Module

DS-X9032-SSM 32-port Storage Services Module (SSM) Yes Yes Yes

DS-X9308-SMIP 8-port 1-, 2-Gbps IP Switching Module No No No

DS-X9304-SMIP 4-port 1-, 2-Gbps IP Switching Module No No No

1. In software releases earlier than Cisco NX-OS Release 4.2(7a), the Supervisor-2A module appears as unsupported hardware in Device Manager, but the Supervisor-2A module does work with Cisco NX-OS release 4.x software.

2. Requires DS-13SLT-FAB2 in the MDS 9513.

Table 6 lists the MDS hardware modules supported by Cisco MDS SAN-OS 3.x.

Yes No Yes

Table 6 Module Support Matrix for Cisco MDS SAN-OS 3.x

Module Description

MDS 9500 Series

MDS 9222i

MDS 9216i

MDS 9216A

MDS 9216

DS-X9530-SF2-K9 MDS 9500 Supervisor-2 Module Yes N/A N/A N/A N/A

DS-X9530-SF2A-K9 MDS 9500 Supervisor-2A Module Yes

N/A N/A N/A N/A

DS-X9530-SF1-K9 MDS 9500 Supervisor-1 Module Yes N/A N/A N/A N/A

DS-13SLT-FAB2 MDS 9513 Fabric Module 2 Yes N/A N/A N/A N/A

DS-13SLT-FAB1 MDS 9513 Fabric Module 1 Yes N/A N/A N/A N/A

DS-X9224-96K9 24-port 8-Gbps Fibre Channel Switching

No No No No No

Module

DS-X9248-96K9 48-port 8-Gbps Fibre Channel Switching

No No No No No

Module

DS-X9248-48K9 4/44-port Host Optimized8-Gbps Fibre

No No No No No

Channel Switching Module

DS-X9316-SSNK9 16-port Storage Services Node (SSN-16) No No No No No

DS-X9304-18K9 18/4-Port Multiservice Module

(MSM-18/4)

DS-X9112 12-port 4-Gbps Fibre Channel Switching

Yes Ye s Ye s Ye s N o

Module

DS-X9124 24-port 4-Gbps Fibre Channel Switching

Yes Ye s Ye s Ye s N o

Module

DS-X9148 48-port 4-Gbps Fibre Channel Switching

Yes Ye s Ye s Ye s N o

Module

DS-X9704 4-port 10-Gbps Fibre Channel Switching

Yes Ye s Ye s Ye s N o

Module

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Migrating from Supervisor-1 Modules to Supervisor-2 Modules

Send documentation comments to mdsfeedback-doc@cisco.com

Table 6 Module Support Matrix for Cisco MDS SAN-OS 3.x (continued)

MDS 9500

Module Description

DS-X9302-14K9 14/2-port Multiprotocol Services

(MPS-14/2) Module

DS-X9016 16-port 1-, 2-Gbps Fibre Channel Switching

Module

DS-X9032 32-port 1-, 2-Gbps Fibre Channel Switching

Module

DS-X9032-SSM 32-port Storage Services Module (SSM) Yes Yes Yes Yes Yes

DS-X9308-SMIP 8-port 1-, 2-Gbps IP Switching Module Yes No Yes Yes Yes

DS-X9304-SMIP 4-port 1-, 2-Gbps IP Switching Module Yes Yes Yes Yes Yes

1. In software releases earlier than Cisco NX-OS Release 3.3(5a), the Supervisor-2A module appears as unsupported hardware in Device Manager, but the Supervisor-2A module does work with Cisco NX-OS release 3.x software.

2. Cisco SAN-OS Release 3.2(1) and later support the 18/4-Port Multiservice Module (MSM-18/4).

Series

Yes N o Ye s Yes Ye s

MDS 9222i

MDS 9216i

MDS 9216A

MDS 9216

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 NX-OS Release 4.1(x) and SAN-OS 3(x) Software Upgrade and Downgrade

Guide.

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 NX-OS software and includes the following topics:

• Determining the Software Version, page 13

• Determining Software Version Compatibility, page 13

• Downloading Software, page 13

• Selecting the Correct Software Image for an MDS 9100 Series Switch, page 14

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Software Download Process

Send documentation comments to mdsfeedback-doc@cisco.com

• Selecting the Correct Software Image for an MDS 9200 Series Switch, page 14

• Selecting the Correct Software Image for an MDS 9500 Series Switch, page 15

Determining the Software Version

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

Determining Software Version Compatibility

Table 7 lists the software versions that are compatible in a mixed SAN environment, the minimum

software versions that are supported, and the versions that have been tested. We recommend that you use the latest software release supported by your vendor for all Cisco MDS 9000 Family products.

Table 7 Software Release Compatibility

NX-OS Software

NX-OS Release 5.0(4b) SAN-OS Release 3.3(1c) or later SAN-OS Releases 3.3(1c), 3.3(5)

Fabric Manager Software

Fabric Manager Release

5.0(4b)

Downloading Software

The Cisco MDS NX-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 NX-OS software, access the Software Center at this URL:

Minimum NX-OS or SAN-OS Release

NX-OS Release 4.1(1b) or later NX-OS Releases 4.1(1b), 4.2(7a)

Minimum NX-OS or SAN-OS Release

SAN-OS Release 3.3(1c) or later SAN-OS Release 3.3(1c), 3.3(5)

NX-OS Release 4.1(1b) or later NX-OS Release 4.1(1b), 4.2(7a)

NX-OS Release 5.0(4b) or later NX-OS Release 5.0(4b)

Tested NX-OS and SAN-OS Releases

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

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Software Download Process

Send documentation comments to mdsfeedback-doc@cisco.com

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

image filename command determines which additional features need to be disabled.

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

Table 8 Software Images for MDS 9100 Series Switches

Cisco MDS 9100 Series Switch Type Naming Convention

MDS 9134, 9124, Cisco Fabric Switch for

Filename begins with m9100-s2ek9 HP c-Class BladeSystem, Cisco Fabric Switch for IBM BladeCenter

MDS 9148 Filename begins with m9100-s3ek9

Selecting the Correct Software Image for an MDS 9200 Series Switch

The system and kickstart image that you use for an MDS 9200 series switch depends on which switch you use, as shown in Table 9.

Table 9 Software Images for MDS 9200 Series Switches

Cisco MDS 9200 Series Switch Type Naming Convention

MDS 9222i Filename begins with m9200-s2ek9

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Upgrading Your Cisco MDS NX-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

Selecting the Correct Software Image for an MDS 9500 Series Switch

The system and kickstart image that you use for an MDS 9500 Series are for switches with a Supervisor-2 module, as shown in Ta bl e 10. Cisco NX-OS Release 5.x and Release 4.x do not support the Supervisor-1 module.

Table 10 Software Images for Supervisor Type

Cisco MDS 9500 Series Switch Type Supervisor Module Type Naming Convention

MDS 9513, 9509, and 9506 Supervisor-2 module

Supervisor-2A module

Use the show module command to display the type of supervisor module in the switch. The following is sample output from the show module command on a Supervisor 2 module:

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

Filename begins with m9500-sf2ek9

Upgrading Your Cisco MDS NX-OS Software Image

This section lists the guidelines recommended for upgrading your Cisco MDS NX-OS software image and includes the following topics:

• General Upgrading Guidelines, page 16

• Upgrading Effect on VSAN 4079, page 19

• FICON Supported Releases and Upgrade Paths, page 18

• Upgrading with IVR Enabled, page 19

• Upgrading a Cisco MDS 9124 or Cisco MDS 9134 Switch, page 20

• Performing a Disruptive Upgrade on an MDS 9000 Family Switch, page 21

• Resetting SNMP Notifications, page 21

Note Before you begin the upgrade process, review the list of chassis and modules that Cisco MDS NX-OS

Release 5.0(4b) supports. See the “MDS 9000 Chassis and Module Support” section on page 9.

For detailed instructions for performing a software upgrade using Cisco Fabric Manager, see the Cisco Fabric Manager Release Notes for Release 4.2(1a), which is available from the following website:

http://www.cisco.com/en/US/partner/products/ps10495/prod_release_notes_list.html

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Upgrading Your Cisco MDS NX-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

General Upgrading Guidelines

Note To upgrade to NX-OS Release 5.0(4b) from SAN-OS Release 3.2(3a) or earlier, first upgrade to SAN-OS

Release 3.3(x), then upgrade to NX-OS Release 4.1(x) or 4.2(x), and then upgrade to NX-OS Release

5.0(4b).

Use the following guidelines when upgrading to Cisco MDS NX-OS Release 5.0(4b):

• 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 or MDS 9134 Switch as

described in “Upgrading a Cisco MDS 9124 or Cisco MDS 9134 Switch” section on page 20.

• Follow the guidelines for upgrading a single supervisor switch as described in “Performing a

Disruptive Upgrade on an MDS 9000 Family Switch” section on page 21.

• Be aware of the impact of an upgrade on VSAN 4079 if you are upgrading from SAN-OS Release

3.x to NX-OS 5.0(4b). See the “Upgrading Effect on VSAN 4079” section on page 19 for details.

• Be aware that some features impact whether an upgrade is disruptive or nondisruptive:

–

Fibre Channel Ports: Fibre Channel ports can be nondisruptively upgraded without affecting traffic on the ports. See Tab l e 11 for the nondisruptive upgrade path for all NX-OS and SAN-OS releases.

–

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

–

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

–

Inter-VSAN Routing (IVR): With IVR enabled, you must follow additional steps if you are upgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the “Upgrading with

IVR Enabled” section on page 19 for these instructions.

–

FICON: If you have FICON enabled, the upgrade path is different. See the “FICON Supported

Releases and Upgrade Paths” section on page 18.

Note In addition to these guidelines, you may want to review the information in the “Limitations and

Restrictions” section prior to a software upgrade to determine if a feature may possibly behave

differently following the upgrade.

Use Tab l e 11 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 5.0(4b), 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 11 applies only to Fibre Channel switching traffic.

Upgrading system software disrupts IP traffic and SSM intelligent services traffic.

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Upgrading Your Cisco MDS NX-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

Table 11 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 5.0(4b)

Current Release Nondisruptive Upgrade Path

NX-OS:

5.0(4)

5.0(1a)

4.2(7a)

4.2(5)

4.2(3a)

4.2(3)

4.2(1b)

4.2(1a)

4.1(3a)

4.1(1c)

4.1(1b)

SAN-OS:

3.3(5)

3.3(4a)

3.3(4)

3.3(3)

3.3(2)

3.3(1c)

3.3(1a)

3.2(3a)

3.2(3)

3.2(2c)

3.2(1a)

3.1(4)

3.1(3a)

3.1(2b)

3.1(2a)

3.1(2)

3.1(1)

3.0(3a)

3.0(3)

3.0(2a)

3.0(2)

3.0(1)

2.1(3)

2.1(2e)

2.1(2d)

2.1(2b)

You can nondisruptively upgrade directly to NX-OS Release 5.0(4b)

Upgrade to NX-OS 4.1(x) or 4.2(x) and then upgrade to NX-OS Release 5.0(4b).

Upgrade to SAN-OS Release 3.3(x), then upgrade to NX-OS 4.1(x) or 4.2(x), and then upgrade to NX-OS Release 5.0(4b).

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Upgrading Your Cisco MDS NX-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

Table 11 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 5.0(4b) (continued)

Current Release Nondisruptive Upgrade Path

2.1(2)

2.1(1b)

2.1(1a)

2.0(x)

Upgrade to SAN-OS Release 2.1(2b), then upgrade to Release 3.3(x), then upgrade to NX-OS 4.1(x) or 4.2(x), and then upgrade to NX-OS Release 5.0(4b) or Upgrade to SAN-OS Release 2.1(2d), then upgrade to Release 3.3(x), then upgrade to NX-OS 4.1(x) or 4.2(x), and then upgrade to NX-OS Release 5.0(4b) or Upgrade to SAN-OS Release 2.1(2e), then upgrade to Release 3.3(x), then upgrade to NX-OS 4.1(x) or 4.2(x), and then upgrade to NX-OS Release 5.0(4b) or Upgrade to SAN-OS Release 2.1(3), then upgrade to Release 3.3(x), then upgrade to NX-OS 4.1(x) or 4.2(x), and then upgrade to NX-OS Release 5.0(4b)

1.x Upgrade to SAN-OS Release 1.3(4a), then upgrade to Release 2.1(2b), then upgrade to Release 3.3(x), then upgrade to NX-OS 4.1(x) or 4.2(x), and then upgrade to NX-OS Release 5.0(4b).

FICON Supported Releases and Upgrade Paths

Cisco MDS NX-OS Release 5.0(4b) does not support FICON

Table 12 lists the SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes

for FICON upgrade path information.

Table 12 FICON Supported Releases

FICON Supported Releases

NX-OS Release 4.2(1b)

Release 4.1(1c)

SAN-OS Release 3.3(1c)

Release 3.2(2c)

Release 3.0(3b)

Release 3.0(3)

Release 3.0(2)

Release 2.0(2b)

Use Table 13 to determine your FICON nondisruptive upgrade path to Cisco MDS NX-OS Release 5.0 Find the image release number you are currently using in the Current Release with FICON Enabled column of the table and follow the recommended path.

Table 13 FICON Nondisruptive Upgrade Path to MDS NX-OS Release 4.2(1b)

Current Release with FICON Enabled Upgrade Path

NX-OS 4.1(1c) You can nondisruptively upgrade directly to NX-OS Release 4.2(1b).

SAN-OS 3.3(1c) You can nondisruptively upgrade directly to NX-OS Release 4.2(1b).

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Upgrading Your Cisco MDS NX-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

Table 13 FICON Nondisruptive Upgrade Path to MDS NX-OS Release 4.2(1b) (continued)

Current Release with FICON Enabled Upgrade Path

SAN-OS 3.2(2c) First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS

SAN-OS 3.0(3b)

SAN-OS 3.0(3)

SAN-OS 3.0(2)

SAN-OS 2.0(2b) Use the interface shutdown command to administratively shut any Fibre

SAN-OS 1.x Upgrade to SAN-OS Release 3.0(2). Use the interface shutdown

Release 4.2(1b).

Channel ports on Generation 1 modules that are in an operationally down state before nondisruptively upgrading from SAN-OS Release 2.0(2b) to SAN-OS Release 3.0(2) or SAN-OS Release 3.0(3b), and then upgrade to Release 3.3(1c). An operationally down state includes

or not-connected, SFP not present

, or Error Disabled status in the

Link failure

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.

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 Effect on VSAN 4079

If you upgrade to NX-OS Release 5.0(4b), and you have not created VSAN 4079, the NX-OS software will automatically create VSAN 4079 and reserve it for EVFP use.

If VSAN 4079 is reserved for EVFP use, the switchport trunk allowed vsan command will filter out VSAN 4079 from the allowed list. In the following example, the allowed list appears on a separate line following the command:

switch(config-if)# switchport trunk allowed vsan 1-4080 1-4078,4080 switch(config-if)#

If you have created VSAN 4079, the upgrade to NX-OS Release 5.0(4b) will have no affect on VSAN

4079.

If you downgrade to a release of NX-OS lower than NX-OS Release 4.1(x) after NX-OS Release 5.0(4b) creates VSAN 4079 and reserves it for EVFP use, the VSAN will no longer be reserved.

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.

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Upgrading Your Cisco MDS NX-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

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

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

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

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

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

Step 6 Issue the copy running-config startup-config command to save the RDI mode in the startup

configuration on all of the switches.

Step 7 Follow the normal upgrade guidelines for Release 2.1(2b). If you are adding new switches running Cisco

MDS SAN-OS Release 2.1(2b) or later, upgrade all of your existing switches to Cisco SAN-OS Release

2.1(2b) as described in this workaround. Then follow the normal upgrade guidelines for Release 3.3(1c).

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

Upgrading a Cisco MDS 9124 or Cisco MDS 9134 Switch

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Downgrading Your Cisco MDS SAN-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

If you are upgrading from Cisco MDS SAN-OS Release 3.1(1) to Cisco NX-OS Release 4.2(1b) before upgrading to NX-OS Release 5.0(4b) on a Cisco MDS 9124 or MDS 9134 Switch, follow these guidelines:

• During the upgrade, configuration is not allowed and the fabric is expected to be stable.

• The Fabric Shortest Path First (FSPF) timers must be configured to the default value of 20 seconds;

otherwise, the nondisruptive upgrade is blocked to ensure that the maximum down time for the control plane can be 80 seconds.

• If there are any CFS commits in the fabric, the nondisruptive upgrade will fail.

• If there is a zone server merge in progress in the fabric, the nondisruptive upgrade will fail.

• If a service terminates the nondisruptive upgrade, the show install all failure-reason command can

display the reason that the nondisruptive upgrade cannot proceed.

• If there is not enough memory in the system to load the new images, the upgrade will be made

disruptive due to insufficient resources and the user will be notified in the compatibility table.

Performing a Disruptive Upgrade on an MDS 9000 Family Switch

If you do not follow the upgrade path when performing a disruptive upgrade on an MDS 9000 Family switch, (for example, you upgrade directly from SAN-OS Release 2.1(2) or earlier version to NX-OS Release 4.2(x)), 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.

Note You cannot upgrade the software image on an MDS 9120 switch, an MDS 9140 switch, or an MDS 9216i

switch to Cisco NX-OS Release 5.x. See Table 3 for the list of switches that support Cisco NX-OS Release 5.0(4b).

Resetting SNMP Notifications

Following a software upgrade or downgrade, SNMP notifications will reset as follows:

• When you upgrade from SAN-OS Release 3.x to NX-OS Release 4.1(x), and then to NX-OS Release

5.x, SNMP notifications will reset to their default settings.

• When you upgrade from SAN-OS Release 3.x to NX-OS Release 4.2(x), and then to NX-OS Release

5.x, SNMP notifications will not reset to their default settings.

• When you downgrade from any NX-OS Release 4.2(x), SNMP notifications will reset to their

default configuration settings.

Use the snmp-server enable traps command to reenable your required SNMP notifications.

Downgrading Your Cisco MDS SAN-OS Software Image

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

• General Downgrading Guidelines, page 22

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Downgrading Your Cisco MDS SAN-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

• New Features in Cisco MDS NX-OS Release 5.0(4b), page 25

General Downgrading Guidelines

Use the following guidelines to nondisruptively downgrade your Cisco MDS NX-OS Release 5.0(4b):

• 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 command to determine what you need to disable.

• Use the show install all impact downgrade-image 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: Fibre Channel ports can be nondisruptively downgraded without affecting traffic on the ports. See Ta ble 14 for the nondisruptive downgrade path for all SAN-OS releases.

–

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

–

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

–

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

on page 19 for these instructions.

–

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

Downgrade Paths” section on page 25.

Note A downgrade from NX-OS Release 4.2(1b) to SAN-OS Release 3.3(1x) is not supported on MDS

switches, when FC-Redirect based applications, such as Data Mobility Manager or Storage Media Encryption, are configured in the fabric if either of the following conditions are satisfied:

1. A target for which FC-Redirect is configured is connected locally and there are Generation 1

modules with ISLs configured in the switch.

2. A host, for which FC-redirect is configured, is connected locally on a Generation 1 module.

If these conditions exist, remove the application configuration for these targets and hosts before proceeding with the downgrade.

Use Table 14 to determine the nondisruptive downgrade path from Cisco NX-OS Release 4.2(1b). 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.

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Downgrading Your Cisco MDS SAN-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

Note The software downgrade information in Tabl e 14 applies only to Fibre Channel switching traffic.

Downgrading system software disrupts IP and SSM intelligent services traffic.

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Downgrading Your Cisco MDS SAN-OS Software Image

Send documentation comments to mdsfeedback-doc@cisco.com

Table 14 Nondisruptive Downgrade Path from NX-OS Release 5.0(4b)

To NX-OS or SAN-OS Release Nondisruptive Downgrade Path

NX-OS:

5.0(4)

5.0(1a)

4.2(7a)

4.2(5)

4.2(3a)

4.2(3)

4.2(1b)

4.2(1a)

4.1(3a)

4.1(1c)

4.1(1b)

SAN-OS:

3.3(5)

3.3(4a)

3.3(4)

3.3(3)

3.3(2)

3.3(1c)

3.3(1a)

3.2(3a)

3.2(3)

3.2(2c)

3.2(1a)

3.2(1)

3.1(4)

3.1(3a)

3.1(3)

3.1(2b)

3.1(2a)

3.1(2)

3.0(3a)

3.0(3)

3.0(2a)

3.0(2)

3.0(1)

2.1(3)

2.1(2e)

2.1(2d)

2.1(2b)

2.1(2)

2.1(2b)

2.1(1a)

You can nondisruptively downgrade directly from NX-OS Release 5.0(4b).

Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, and then downgrade to SAN-OS Release 3.3(x).

Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade to SAN-OS Release 3.3(x), and then downgrade to Release 3.2(x), Release

3.1(x)., Release 3.0(x), or Release 2.1(x).

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

New Features in Cisco MDS NX-OS Release 5.0(4b)

Send documentation comments to mdsfeedback-doc@cisco.com

Table 14 Nondisruptive Downgrade Path from NX-OS Release 5.0(4b) (continued)

To NX-OS or SAN-OS Release Nondisruptive Downgrade Path

2.0(4a)

2.0(4)

2.0(3)

Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade to SAN-OS Release 3.3(x), then downgrade to Release 2.1(2x), and then downgrade to Release 2.0(x).

2.0(2b)

2.0(1b)

1.x Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade to SAN-OS Release 3.3(x), then 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.

FICON Downgrade Paths

Table 15 lists the downgrade paths for FICON releases. Find the image release number that you want to

downgrade to in the To Release with FICON Enabled column of the table and follow the recommended downgrade path.

Table 15 FICON Downgrade Path from NX-OS Release 4.1(1c)

To Release with FICON Enabled Downgrade Path

SAN-OS 3.3(1c) You can nondisruptively downgrade directly from NX-OS Release 4.1(1c).

SAN-OS 3.2(2c) First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release

3.2(2c).

SAN-OS 3.0(3b) First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release

3.0(3b).

SAN-OS 3.0(2) First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release

3.0(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 NX-OS Release 4.1 to SAN-OS Release 3.3(1c) then to SAN-OS Release 3.0(3b) or SAN-OS Release 3.0(2), and then to SAN-OS Release 2.0(2b). An operationally down state includes

Error Disabled

an interface is administratively shut it will then show as

. Interfaces that are currently up or trunking do not need to be shut

down

Link failure or not-connected, SFP not present, or

status in the output of a show interface command. When

Administratively

down.

SAN-OS 1.3(4a) Downgrade to SAN-OS Release 3.3(1c) and then to 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).

New Features in Cisco MDS NX-OS Release 5.0(4b)

Cisco MDS NX-OS Release 5.0(4b) is a hot fix release. It does not include new features.

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Licensed Cisco NX-OS Software Packages

Send documentation comments to mdsfeedback-doc@cisco.com

Licensed Cisco NX-OS Software Packages

Most Cisco MDS 9000 family software features are included in the standard package. However, some features are logically grouped into add-on packages that must be licensed separately, such as the Cisco MDS 9000 Enterprise package, SAN Extension over IP package, Mainframe package, Fabric Manager Server (FMS) package, Storage Services Enabler (SSE) package, Storage Media Encryption package, and Data Mobility Manager package. On-demand ports activation licenses are also available for the Cisco MDS Blade Switch Series and 4-Gbps Cisco MDS 9100 Series Multilayer Fabric switches.

Enterprise Package

The standard software package that is bundled at no charge with the Cisco MDS 9000 Family switches includes the base set of features that Cisco believes are required by most customers for building a SAN. The Cisco MDS 9000 family also has a set of advanced features that are recommended for all enterprise SANs. These features are bundled together in the Cisco MDS 9000 Enterprise package. Refer to the Cisco MDS 9000 Enterprise package fact sheet for more information.

SAN Extension over IP Package

The Cisco MDS 9000 SAN Extension over IP package allows the customer to use FCIP to extend SANs over wide distances on IP networks using the Cisco MDS 9000 family IP storage services. Refer to the Cisco MDS 9000 SAN Extension over IP package fact sheet for more information.

Mainframe Package

The Cisco MDS 9000 Mainframe package uses the FICON protocol and allows control unit port management for in-band management from IBM S/390 and z/900 processors. FICON VSAN support is provided to help ensure true hardware-based separation of FICON and open systems. Switch cascading, fabric binding, and intermixing are also included in this package. Refer to the Cisco MDS 9000 Mainframe package fact sheet for more information.

Storage Services Enabler Package

The Cisco MDS 9000 SSE package allows network-based storage applications and services to run on the Cisco MDS 9000 family SSMs, Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4), and Cisco MDS 9222i. Intelligent fabric applications simplify complex IT storage environments and help organizations gain control of capital and operating costs by providing consistent and automated storage management. Refer to the Cisco MDS 9000 SSE package fact sheet for more information.

On-Demand Port Activation License

On-demand ports allow customers to benefit from Cisco NX-OS Software features while initially purchasing only a small number of activated ports on 8-Gbps or 4-Gbps Cisco MDS 9100 Series Multilayer Fabric switches. As needed, customers can expand switch connectivity by licensing additional ports.

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

I/O Accelerator Package

The Cisco I/O Accelerator (IOA) package activates IOA on the Cisco MDS 9222i fabric switch, the Cisco MDS 9000 18/4 Multiservice Module (MSM-18/4), and on the SSN-16 module. The IOA package is licensed per service engine and is tied to the chassis. The number of licenses required is equal to the number of service engines on which the intelligent fabric application is used.The SSN-16 requires a separate license for each engine on which you want to run IOA. Each SSN-16 engine that you configure for IOA checks out a license from the pool managed at the chassis level. SSN-16 IOA licenses are available as single licenses.

XRC Acceleration License

The Cisco Extended Remote Copy (XRC) acceleration license activates FICON XRC acceleration on the Cisco MDS 9222i switch and on the MSM-18/4 in the Cisco MDS 9500 Series directors. One license per chassis is required. You must install the Mainframe Package and the SAN Extension over FCIP Package before you install the XRC acceleration license. The Mainframe Package enables the underlying FICON support, and the FCIP license or licenses enable the underlying FCIP support. XRC acceleration is not supported on the SSN-16.

Limitations and Restrictions

This section lists the limitations and restrictions for this release. The following limitations are described:

• Support for Generation One Modules, page 28

• IPv6, page 28

• User Roles, page 28

• Red Hat Enterprise Linux, page 28

• Generation 1 Module Limitation, page 28

• Schedule Job Configurations, page 29

• Maximum Number of Zones Supported in Interop Mode 4, page 29

• InterVSAN Routing, page 29

• Java Web Start, page 29

• VRRP Availability, page 29

• Using a RSA Version 1 Key for SSH Following an Upgrade, page 29

• CFS Cannot Distribute All Call Home Information, page 30

• Availability of F Port Trunking and F Port Channels, page 31

• Reserved VSAN Range and Isolated VSAN Range Guidelines, page 31

• Applying Zone Configurations to VSAN 1, page 32

• Running Storage Applications on the MSM-18/4, page 32

• RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching Modules, page 32

• I/O Accelerator Feature Limitations, page 32

• Support for FCIP Compression Modes, page 32

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

• Saving Copies of the Running Kickstart and System Images, page 33

• Configuring Buffer Credits on a Generation 2 or Generation 3 Module, page 33

• Features Not Supported on the Cisco MDS 9148 Switch, page 33

• PPRC Not Supported with FCIP Write Acceleration, page 33

Support for Generation One Modules

As of Cisco MDS NX-OS Release 5.0(1a), support for Generation One modules has been discontinued. See the “Support for Generation One Modules” section for more information.

IPv6

The management port on Cisco MDS switches supports one user-configured IPv6 address, but does not support auto-configuration of an IPv6 address.

User Roles

In SAN-OS Release 3.3(x) and earlier, when a user belongs to a role which has a VSAN policy set to Deny and the role allows access to a specific set of VSANs (for example, 1 through 10), the user is restricted from performing the configuration, clear, execute, and debug commands which had a VSAN parameter outside this specified set. Beginning with NX-OS Release 4.1(1b), these users are still prevented from performing configuration, clear, execute, and debug commands as before, however, they are allowed to perform show commands for all VSANs. The ability to execute the show command addresses the following:

• In a network environment, users often need to view information in other VSANs even though they

do not have permission to modify configurations in those VSANs.

• This behavior makes Cisco MDS 9000 Series switches consistent with other Cisco products, such

as Cisco Nexus 7000 Series switches, that exhibit the same behavior for those roles (when they apply to the VLAN policy).

Red Hat Enterprise Linux

The Linux kernel core dump is not supported in NX-OS Release 4.1(1b) and later versions and therefore the CLI command has been removed. A syntax error message will be displayed if you import configurations from SAN-OS Release 3.3(x) and earlier to NX-OS Release 4.1(1b) and later. These syntax errors do not affect the application of other commands in the configuration and can be safely ignored. To address this, remove the kernel core configuration from the ASCII configuration file before importing the configuration.

Generation 1 Module Limitation

When a Cisco or other vendor switch port is connected to a Generation 1 module port (ISL connection), the receive buffer-to-buffer credit of the port connected to a Generation 1 module port should not exceed

255.

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

Schedule Job Configurations

As of MDS NX-OS Release 4.1(1b) and later, the scheduler job configurations need to be entered in a single line with a semicolon(;) as the delimiter.

Job configuration files created with SAN-OS Release 3.3(1c) and earlier, are not supported. However, you can edit the job configuration file and add the delimiter to support Cisco NX-OS Release 4.1(3a).

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.

InterVSAN Routing

When using InterVSAN Routing (IVR), it is recommended to enable Cisco Fabric Services (CFS) on all IVR-enabled switches. Failure to do so may cause mismatched active zone sets if an error occurs during zone set activation.

Java Web Start

When using Java Web Start, it is recommended that you do not use an HTML cache or proxy server. You can use the Java Web Start Preferences panel to view or edit the proxy configuration. To do this, launch the Application Manager, either by clicking the desktop icon (Microsoft Windows), or type ./javaws in the Java Web Start installation directory (Solaris Operating Environment and Linux), and then select Edit> Preferences.

If you fail to change these settings, you may encounter installation issues regarding a version mismatch. If this occurs, you should clear your Java cache and retry.

VRRP Availability

The Virtual Router Redundancy Protocol (VRRP) is not available on the Gigabit Ethernet interfaces on the MSM-18/4 module or module 1 of the MDS 9222i switch, even though it is visible on these modules. The feature is not implemented in the current release.

Using a RSA Version 1 Key for SSH Following an Upgrade

For security reasons, NX-OS Release 4.2(1b) does not support RSA version 1 keys. As a result, if you upgrade to NX-OS Release 4.2(1b) from an earlier version that did support RSA version 1 keys, and you had configured a RSA version 1 key for SSH, then you will not be able to log in through SSH following the upgrade.

If you have a RSA version 1 key configured for SSH, before upgrading to NX-OS Release 4.1(3a), follow these steps:

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

Step 1 Disable SSH.

Step 2 Create RSA version 2 DSA keys.

Step 3 Enable SSH.

Step 4 Delete any RSA version 1 keys on any remote SSH clients and replace the version 1 keys with the new

version 2 keys from the switch.

Proceed with the upgrade to NX-OS Release 4.2(1b).

If you upgrade before disabling SSH and creating RSA version 2 keys, follow these steps:

Step 1 Open a Telnet session and log in through the console.

Step 2 Issue the no feature ssh command to disable SSH.

Step 3 Issue the ssh key rsa 1024 command to create RSA version 2 keys.

Step 4 Issue the feature ssh command to enable SSH.

CFS Cannot Distribute All Call Home Information

In MDS NX-OS Release 4.2(1b), CFS cannot distribute the following Call Home commands that can be configured with the destination-profile command:

• destination-profile profile_name transport-method

• destination-profile profile_name http

The output of the show running-config callhome command shows configured Call Home commands:

switch# show running-config callhome > version 4.1(3) > callhome > email-contact abc@cisco.com <mailto:abc@cisco.com> > phone-contact +14087994089 > streetaddress xyxxyx > distribute > destination-profile testProfile > destination-profile testProfile format XML > no destination-profile testProfile transport-method email > destination-profile testProfile transport-method http > destination-profile testProfile http https://xyz.abc.com > destination-profile testProfile alert-group all > transport email smtp-server 64.104.140.134 port 25 use-vrf management > transport email from abc@cisco.com <mailto:abc@cisco.com> > enable > commit

When you attempt to apply these commands in the ASCII configuration, the following commands fail:

> no destination-profile testProfile transport-method email > destination-profile testProfile transport-method http > destination-profile testProfile http https://xyz.abc.com

To work around this issue, issue these commands after the commit command.

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

Availability of F Port Trunking and F Port Channels

Trunking F ports and trunking F port channels are not supported on the following MDS 9000 components:

• DS-C9134-K9, Cisco MDS 9134 Multilayer Fabric Switch, if NPIV is enabled and the switch is

used as the NPV core switch

• DS-C9124-K9, Cisco MDS 9124 Multilayer Fabric Switch, if NPIV is enabled and the switch is

used as the NPV core switch

Trunking F ports, trunking F port channels and regular F port channels are not supported on the following MDS 9000 components:

• DS-X9016, Cisco MDS 9000 2-Gbps16-Port Fibre Channel Switching Module

• DS-X9032, Cisco MDS 9000 2-Gbps 32-Port Fibre Channel Switching Module

• DS-X9032-14K9, Cisco MDS 9000 14/2-Port Multiprotocol Services Module (MPS-14/2)

For configuration information, refer to the “Configuring Trunking” section in the Cisco MDS 9000 NX-OS Interfaces Configuration Guide.

Reserved VSAN Range and Isolated VSAN Range Guidelines

On an NPV switch with a trunking configuration on any interface, or on a regular switch where the feature fport_channel_trunk command has been issued to enable the Trunking F PortChannels feature, follow these configuration guidelines for reserved VSANs and the isolated VSAN:

• If trunk mode is on for any of the interfaces or NP PortChannel is up, the reserved VSANs are 3040

to 4078, and they are not available for user configuration.

• The Exchange Virtual Fabric Protocol (EVFP) isolated VSAN is 4079, and it is not available for user

configuration.

• VSAN 4079 will be impacted by an upgrade to NX-OS Release 4.1(3a), depending on whether or

not VSAN 4079 was created prior to the upgrade. See the “Upgrading Effect on VSAN 4079”

section on page 19 for details.

The following VSAN IDs are assigned in the Fibre Channel Framing and Signaling (FC-FS) interface standard:

VF_ID Value Value Description

00h Do not use as a Virtual Fabric Identifier.

001h ... EFFh Available as a Virtual Fabric Identifier.

F00h ... FEEh Reserved.

FEFh Control VF-ID (see Fibre Channel Link Services

(FC-LS) and Fibre Channel Switch Fabric Generation 4 (FC-SW-4) standards).

FF0h ... FFEh Vendor specific.

FFFh Do not use as a Virtual Fabric Identifier.

FEFh = 4079

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

Applying Zone Configurations to VSAN 1

In the setup script, you can configure system default values for the default-zone to be permit or deny, and you can configure default values for the zone distribution method and for the zone mode.

These default settings are applied when a new VSAN is created. However, the settings will not take effect on VSAN 1, because it exists prior to running the setup script. Therefore, when you need those settings for VSAN 1, you must explicitly issue the following commands:

• zone default-zone permit vsan 1

• zoneset distribute full vsan 1

• zone mode enhanced vsan 1

Running Storage Applications on the MSM-18/4

The Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4) does not support multiple, concurrent storage applications. Only one application, such as SME or DMM, can run on the MSM-18/4 at a time.

RSPAN Traffic Not Supported on CTS Ports on 8-Gbps Switching Modules

An inter-switch link (ISL) that is enabled for Cisco TrustSec (CTS) encryption must be brought up in non-CTS mode to support remote SPAN (RSPAN) traffic on the following modules:

• DS-X9248-96K9: Cisco MDS 9000 48-Port 8-Gbps Fibre Channel Switching Module

• DS-X9224-96K9: Cisco MDS 9000 24-Port 8-Gbps Fibre Channel Switching Module

• DS-X9248-48K9: Cisco MDS 9000 4/44-Port Host-Optimized 8-Gbps Fibre Channel Switching

Module

If the ISL link is brought up with CTS enabled, random packets drops of both RSPAN traffic and normal traffic will occur on the receiver port switch.

I/O Accelerator Feature Limitations

IOA does not support the following NX-OS features:

• F port trunking

• F port channeling

• IOA cannot be configured on flows in topologies that have devices with NPV and NPIV enabled.

For example, IOA is not supported in a topology where a host logs in from a NPV edge switch and IOA is deployed on a NPV core switch for this host.

Support for FCIP Compression Modes

In Cisco NX-OS Release 4.2(1b) and later, FCIP compression mode 1 and compression mode 3 are not supported on the Cisco MSM-18/4 module and on the SSN-16 module.

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

Saving Copies of the Running Kickstart and System Images

After you upgrade to MDS NX-OS Release 4.2(1b), you are not allowed to delete, rename, move, or overwrite the kickstart and system images that are in the current system bootvar settings on an active or standby MDS Supervisor-2 module on any Cisco MDS 9500 Series switch. This restriction does not apply to the integrated supervisor module on the MDS 9200 and MDS 9100 series switches.

Configuring Buffer Credits on a Generation 2 or Generation 3 Module

When you configure port mode to auto or E on a Generation 2 module, one of the ports will not come up for the following configuration:

• Port Mode: auto or E for all of the ports

• Rate Mode: dedicated

• Buffer Credits: default value

When you configure port mode to auto or E on a Generation 3 module, one or two of the ports will not come up for the following configuration:

• Port Mode: auto or E for the first half of the ports, the second half of the ports, or for all of the ports

• Rate Mode: dedicated

• Buffer Credits: default value

When you configure port mode to auto or E for all ports in the global buffer pool, you need to reconfigure buffer credits on one or more of the ports. The total number of buffer credits configured for all the ports in the global buffer pool should be reduced by 64.

Features Not Supported on the Cisco MDS 9148 Switch

The Cisco MDS 9148 Multilayer Fabric Switch does not support the following NX-OS features:

• IVR

• Remote Span

• Translative loop support

• FCC - no generation, quench reaction only

• FC-Redirect

In addition, the following features have these limits:

• VSANs - 31 maximum

• SPAN - 1 session maximum

PPRC Not Supported with FCIP Write Acceleration

IBM Peer to Peer Remote Copy (PPRC) is not supported with FCIP Write Acceleration.

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Caveats

Send documentation comments to mdsfeedback-doc@cisco.com

Caveats

This section lists the open and resolved caveats for this release. Use Tab le 16 to determine the status of a particular caveat. In the table, “O” indicates an open caveat and “R” indicates a resolved caveat.

Table 16 Open Caveats and Resolved Caveats Reference

DDTS Number

O 5.0(4) 5.0(4b)

Severity 2

CSCtf16263 OO

CSCtj47693 —R

CSCtj56122 OR

CSCtj87140 OR

CSCtk47039 OR

Severity 3

CSCsq20408 OO

CSCtd04154 OR

CSCti38286 OR

CSCtj84690 OR

Severity 6

CSCtk18444 OR

Resolved Caveats

NX-OS Software Release (Open or Resolved)

• CSCtj47693

Symptom: When the SME Tape feature is in use, the performance of the IBM LT03 device is lower than when SME Tape is not in use.

Workaround: This issue is resolved.

• CSCtj56122

Symptom: The IPS processor does not compact IO packets whose compressed length is 256.

Workaround: This issue is resolved.

• CSCtj87140

Symptom: IOA does not work correctly for an IBM TSM backup application system that uses the IBM A tape driver to communicate with an IBM LTO-5 drive. When IOA is introduced, the backup fails. The underlying reason is that a vendor-specific command is sent by the driver to the LTO-5 tape drive and IOA does not recognize the command.

Workaround: This issue is resolved.

• CSCtk47039

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Caveats

Send documentation comments to mdsfeedback-doc@cisco.com

Symptom: A Cisco MDS 9000 switch does not respond to an FDISC request from an attached switch with NPV enabled if the MDS 9000 switch is already processing an FDISC request for the same pWWN. This symptom might be seen if the downstream device has NPV mode enabled, and the MDS 9000 switch is processing an FDISC request for the same pWWN and no ABTS request is sent to cancel the in-progress FDISC request.

Workaround: This issue is resolved.

• CSCtd04154

Symptom: The DMM CPP interface cpp1/1/1 does not come up unless there is an active port in VSAN 1, which is the DMM management VSAN. This symptom might be seen when an interface is either not defined or is not up in VSAN 1.

Workaround: This issue is resolved.

• CSCti38286

Symptom: When you create a DMM job, DMM might intermittently display the following message:

DMM_JOB_INFRA_FC_REDIRECT_SETUP_ERR.

This symptom might be seen when there are two or more paths to a host, multiple paths to existing storage, and multiple paths to the new storage.

Workaround: This issue is resolved.

• CSCtj84690

Symptom: When you upgrade from Cisco NX-OS Release 4.1(3a) to NX-OS Release 5.0(1a), certain ports are brought down because of diagnostics failure. Messages similar to the following are displayed:

2010 Jul 5 19:33:39 MDSSWITCH %IMAGE_DNLD-SLOT5-2-IMG_DNLD_STARTED: Module image download process. Please wait until completion... 2010 Jul 5 19:33:57 MDSSWITCH %IMAGE_DNLD-SLOT5-2-IMG_DNLD_COMPLETE: Module image download process. Download successful. 2010 Jul 5 19:35:00 MDSSWITCH %MODULE-5-LCM_MODULE_UPGRADE_END: Upgrade of module 5 ended 2010 Jul 5 19:35:00 MDSSWITCH %PLATFORM-5-MOD_STATUS: Module 5 current-status is MOD_STATUS_ONLINE/OK 2010 Jul 5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: %$VSAN 10%$ Interface fc5/37 is down (Diag failure) 2010 Jul 5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: %$VSAN 10%$ Interface fc5/38 is down (Diag failure) 2010 Jul 5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: %$VSAN 10%$ Interface fc5/39 is down (Diag failure)

The following information is written to the logs:

5) Event:E_DEBUG, length:84, at 242335 usecs after Mon Jul 5 19:35:00 2010 [103] 3170:ohms_lc_exception: ERROR: Exception from module 5 PortBits 0xfff000000000

All interfaces that were brought down with “Diag failure” were listed in an exception that happened before the upgrade occurred.

Workaround: This issue is resolved.

• CSCtk18444

Symptom: When a ICMP error packet (type 3 code 4) is received, there is no way to track the sender of the error packet or to determine the MTU size provided in the error packet.

Workaround: This issue is resolved. The code has been enhanced to print the entire ICMP packet in both the receive and send path when the debug ips ipstack icmp port command is enabled.

OL-21012-04

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

Caveats

Send documentation comments to mdsfeedback-doc@cisco.com

Open Caveats

• CSCtf16263

Symptom: Following an upgrade from Cisco MDS NX-OS Release 4.2(3a) to Release 5.0(1a) on an MDS 9222i switch, the Encapsulating Security Protocol (ESP) configuration is not applied to members of a PortChannel. This issue occurs only on the MDS 9222i switch.

Workaround: To workaround this issue, following these steps:

1. Enable Fibre Channel Security Protocol (FCSP) on the interface and enter

configuration-interface-esp submode.

switch(config)# interface po103 switch(config-if)# fcsp on switch(config-if)# fcsp esp manual

2. Add the old egress Security Association (egress-sa) configuration on the switch. Egress-sa is the

other side of the active ingress-sa.

switch(config-if-esp)# egress-sa 258

3. Add a new ingress-sa on the switch. Do not use the previous SA.

switch(config-if-esp)# ingress-sa 256

4. On the other side of the PortChannel, reconfigure egress with 256.

switch(config)# interface po103 switch(config-if)# fcsp esp manual switch(config-if-esp)# egress-sa 256

At this point, the link is fully secured on both sides.

5. Clean up the old ingress-sa, by deleting it. An error message displays, but the ingress-sa does get

deleted.

switch(config-if-esp)# no ingress-sa 258 ERROR: SA 258 not in ingress list

If you fail to delete the old ingress-sa, an error message displays:

switch(config-if-esp)# ingress-sa 258 ERROR: SA 258 already in ingress list

6. Add the old ingress-sa.

switch(config-if-esp)# ingress-sa 258

• CSCsq20408

Symptom: The show startup command displays aspects of the running configuration when SANTap is configured and/or SANTap objects are created. When a user creates objects such as a CVT or DVT, the configuration is showing in the running-configuration and in the startup-configuration without copying the configuration into the startup-configuration.

Workaround: Issue a copy running-config startup-config command whenever you create objects such as a CVT or DVT so that the running-configuration and startup-configuration are synchronized.

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b)

OL-21012-04

Cisco SN6000C, Cisco MDS 8/24c, MDS 9513, MDS 9509, MDS 9506 Release Note

Specifications and Main Features

Frequently Asked Questions

User Manual