Guest

Cisco MDS 9000 NX-OS and SAN-OS Software

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1)

  • Viewing Options

  • PDF (650.1 KB)
  • Feedback

Table of Contents

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1)

Contents

Introduction

Components Supported

MDS 9000 Chassis and Module Support

Software Download Process

Determining the Software Version

Determining Software Version Compatibility

Downloading Software

Selecting the Correct Software Image for an MDS 9100 Series Switch

Selecting the Correct Software Image for an MDS 9200 Series Switch

Selecting the Correct Software Image for an MDS 9500 Series Switch

NPE Software Images

Upgrading Your Cisco MDS NX-OS Software Image

Upgrading to Cisco NX-OS Release 5.2 from Release 5.0(8)

Upgrading Guidelines Specific to NX-OS Release 5.2(1)

General Upgrading Guidelines

Nondisruptive Upgrade Paths

FICON Supported Releases and Upgrade Paths

Downgrading Your Cisco MDS SAN-OS Software Image

Downgrading Guidelines Specific to NX-OS Release 5.2(1)

General Downgrading Guidelines

NX-OS Release 5.2(x) and Release 5.0(x) Software Downgrade and Upgrade Matrix for Cisco MDS 9509 and 9506 Switches

FICON Downgrade Paths

New Features in Cisco MDS NX-OS Release 5.2(1)

New Software Features

New Hardware

Licensed Cisco NX-OS Software Packages

Enterprise Package

SAN Extension over IP Package

Mainframe Package

Storage Media Encryption Package

Data Mobility Manager Package

Storage Services Enabler Package

On-Demand Port Activation License

I/O Accelerator Package

XRC Acceleration License

Deprecated Features

Zoning Features

SNIA Common Information Model

IVR Non-NAT Mode

Limitations and Restrictions

FCoE Module

IPv6

User Roles

Schedule Job Configurations

Maximum Number of Zones Supported in Interop Mode 4

InterVSAN Routing

Java Web Start

VRRP Availability

Using a RSA Version 1 Key for SSH Following an Upgrade

CFS Cannot Distribute All Call Home Information

Availability of F Port Trunking and F Port Channels

Reserved VSAN Range and Isolated VSAN Range Guidelines

Applying Zone Configurations to VSAN 1

Running Storage Applications on the MSM-18/4

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

I/O Accelerator Feature Limitations

Support for FCIP Compression Modes

Saving Copies of the Running Kickstart and System Images

Configuring Buffer Credits on a Generation 2 or Generation 3 Module

Features Not Supported on the Cisco MDS 9148 Switch

PPRC Not Supported with FCIP Write Acceleration

Configuring a Persistent FCID in an IVR Configuration with Brocade Switches

Configuring NPIV

Caveats

Resolved Caveats

Open Caveats

Related Documentation

Release Notes

Regulatory Compliance and Safety Information

Compatibility Information

Hardware Installation

Software Installation and Upgrade

Cisco NX-OS

Command-Line Interface

Intelligent Storage Networking Services Configuration Guides

Troubleshooting and Reference

Obtaining Documentation and Submitting a Service Request

Cisco MDS 9000 Family Release Notes
for Cisco MDS NX-OS Release 5.2(1)

Release Date: July 17, 2011

Part Number: OL-25090-01 P0

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.

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

July 17, 2011

Created the Cisco MDS NX-OS Release 5.2(1) release notes.

B0

September 7, 2011

Updated the upgrade path to Release 5.2(1) in Table 11 and the downgrade path to Release 5.2(1) in Table 15 .

C0

September 8, 2011

Added a guideline to the “Upgrading Guidelines Specific to NX-OS Release 5.2(1)” section and added a Caution to the “Nondisruptive Upgrade Paths” section.

D0

September 10, 2011

Added the limitation “Configuring a Persistent FCID in an IVR Configuration with Brocade Switches”.

E0

September 27, 2011

Replaced the Deprecated Features section with the“Deprecated Features” section and revised the descriptions of the features previoulsy described as “deprecated” to reflect how they are changed in Release 5.2(1).

F0

February 23, 2012

Removed caveat CSCtr52721.

G0

March 5, 2012

  • Added the section.
  • Updated the upgrade path information in Table 11 .

H0

April 2, 2012

Updated Table 11 .

I0

April 30, 2012

J0

May 7, 2012

Added open caveat CSCty97827.

K0

May 24, 2012

Added open caveat CSCty85364.

L0

June 20, 2012

Added open caveat CSCts88422.

M0

June 25, 2012

Added open caveat CSCua61044.

N0

July 2, 2012

Added a Note before Table 11 stating that a switch reload might be required following the software upgrade if a Generation 4 module is to be installed.

O0

September 28, 2012

Updated the “Deprecated Features” section.

P0

November 8, 2012

Added the “NPE Software Images” section.

Q0

June 30, 2014

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.

Components Supported

Table 2 lists the NX-OS software part numbers and hardware components supported by the Cisco MDS 9000 Family.


Note For the latest information about supported transceivers, see the Cisco MDS 9000 Family Pluggable Transceivers data sheet.


 

Table 2 Cisco MDS 9000 Family Supported Software and Hardware Components

Component
Part Number
Description
Applicable Product

Software

M95S2K9-5.2.1

MDS 9500 Supervisor/Fabric-2, NX-OS software

MDS 9500 Series only

M92S2K9-5.2.1

MDS 9200 Supervisor/Fabric-2, NX-OS software

MDS 9222i Switch only

M91S3K9-5.2.1

MDS 9148 Supervisor/Fabric-3 NX-OS software

MDS 9148 Switch

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

M95DMM184TSK9

Data Mobility Manager for one MSM-18/4 module — Time Limited to 180 days only

MDS 9500 Series 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 Limited to 180 days only

MDS 9200 Series only

M92SSESSNK9

Cisco Storage Services Enabler License for SSN-16
(1 engine)

MDS 9200 Series only

M95SSESSNK9

Cisco Storage Services Enabler License for SSN-16
(1 engine)

MDS 9500 Series only

M92SMESSNK9

Cisco Storage Media Encryption License for SSN-16
(1 engine)

MDS 9200 Series only

M95SMESSNK9

Cisco Storage Media Encryption License for SSN-16
(1 engine)

MDS 9500 Series only

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 switch

MDS 9222i Switch only

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

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)

MDS 9513 Switch

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)

MDS 9509 Switch

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)

MDS 9506 Switch

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)

MDS 9222i Switch

DS-C9148-K9

Cisco MDS 9148 48-Port Multilayer Fabric Switch (1RU fixed-configuration multilayer fabric switch with 48 8-Gbps Fibre Channel ports)

MDS 9148 Switch

Supervisor 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

Switching Modules

DS-X9112

Cisco MDS 9000 12-port 4-Gbps Fibre Channel Switching Module with SFP LC connectors

MDS 9500 Series

MDS 9200 Series

DS-X9124

Cisco 24-port 4-Gbps Fibre Channel Switching Module with SFP LC connectors

MDS 9500 Series

MDS 9200 Series

DS-X9148

Cisco MDS 9000 48-port 4-Gbps Fibre Channel Switching Module with SFP LC

MDS 9500 Series

MdS 9200 Series

DS-X9704

Cisco MDS 9000 Family 4-Port 10-Gbps Fibre Channel Switching Module with SFP LC

MDS 9500 Series

MDS 9200 Series

DS-X9224-96K9

Cisco MDS 9000 24-Port 8-Gbps Fibre Channel Switching Module with SFP and SFP+ LC connectors

MDS 9500 Series

DS-X9248-96K9

Cisco MDS 9000 48-Port 8-Gbps Fibre Channel Switching Module with SFP and SFP+ LC connectors

MDS 9500 Series

DS-X9248-48K9

Cisco MDS 9000 4/44-Port Host-Optimized 8-Gbps Fibre Channel Switching Module with SFP and SFP+ LC connectors

MDS 9500 Series

MDS 9222i Switch

DS-X9708-K9

Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) Module

MDS 9500 Series

DS-X9232-256K9

Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching Module

MDS 9500 Series

DS-X9248-256K9

Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching Module

MDS 9500 Series

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.

MDS 9500 Series

MDS 9222i Switch

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

MDS 9500 Series

MDS 9200 Series

External crossbar module

DS-13SLT-FAB1

Cisco MDS 9513 Switching Fabric 1 Module

MDS 9513 Switch

DS-13SLT-FAB2

Cisco MDS 9513 Switching Fabric 2 Module

MDS 9513 Switch

DS-13SLT-FAB3

Cisco MDS 9513 Switching Fabric 3 Module

MDS 9513 Switch

Optics

SFP-10G-SR

10GBASE-SR SFP+ Module

MDS 9500 Series,
8-port 10-Gbps FCoE Module (DS-X9708-K9)

SFP-10G-LR

10GBASE-LR SFP+ Module

MDS 9500 Series,
8-port 10-Gbps FCoE Module (DS-X9708-K9)

SFP-H10GB-CU1M

10GBASE-CU SFP+ cable 1 meter

MDS 9500 Series,
8-port 10-Gbps FCoE Module (DS-X9708-K9)

SFP-H10GB-CU3M

10GBASE-CU SFP+ cable 3 meter

MDS 9500 Series,
8-port 10-Gbps FCoE Module (DS-X9708-K9)

SFP-H10GB-CU5M

10GBASE-CU SFP+ cable 5 meter

MDS 9500 Series,
8-port 10-Gbps FCoE Module (DS-X9708-K9)

SFP-H10GB-ACU7M

10GBASE-CU SFP+ active copper cable 7 meter

MDS 9500 Series,
8-port 10-Gbps FCoE Module (DS-X9708-K9)

SFP-H10GB-ACU10M

10GBASE-CU SFP+ active copper cable 10 meter

MDS 9500 Series,
8-port 10-Gbps FCoE Module (DS-X9708-K9)

LC-type fiber-optic SFP

DS-FC10G-SW

SFP+ optics (LC type)for 10-Gbps Fibre Channel for shortwave mode

32-port 8-Gbps Advanced Fibre Channel Module (DS-X9232-256K9),
48-port 8-Gbps Advanced Fibre Channel Module (DS-X9248-256-K9)

DS-FC10G-LW

SFP+ optics (LC type)for 10-Gbps Fibre Channel for longwave mode

32-port 8-Gbps Advanced Fibre Channel Module (DS-X9232-256K9),
48-port 8-Gbps Advanced Fibre Channel Module (DS-X9248-256-K9)

DS-SFP-FC8G-ER

SFP+ optics (LC type) for 2-, 4-, or 8-Gbps Fibre Channel for extended reach (40 km reach)

MDS DS-X9200 Series switching modules,
MDS 9148

DS-SFP-FC8G-SW

SFP+ optics (LC type) for 2-, 4-, or 8-Gbps Fibre Channel for shortwave mode

MDS DS-X9200 Series switching modules

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

MDS DS-X9200 Series switching modules

DS-SFP-FC4G-SW

SFP optics (LC type) for 1-, 2-, or 4-Gbps Fibre Channel for shortwave mode

MDS 9124, MDS 9134, MDS 9148, 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-FCGE-SW

SFP optics (LC type) for 1-Gbps Ethernet and 1- or 2-Gbps Fibre Channel for shortwave mode; not supported for use in 4-Gbps-capable ports

MDS 9000 Series

DS-SFP-FCGE-LW

SFP optics (LC type) for 1-Gbps Ethernet and 1- or 2-Gbps Fibre Channel for longwave mode; not supported for use in 4-Gbps-capable ports

MDS 9000 Series

DS-SFP-GE-T

SFP (RJ-45 connector) for Gigabit Ethernet over copper

MDS 9000 Series

Cisco Coarse Wavelength- Division Multiplexing (CWDM)

DS-CWDM-xxxx

CWDM Gigabit Ethernet and 1- or 2-Gbps Fibre Channel SFP LC type, where product number xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm

MDS 9000 Family

DS-CWDM4Gxxxx

CWDM 4-Gbps Fibre Channel SFP LC type, where product number xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm

MDS 9000 Family

Dense Wavelength- Division 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

MDS 9500 Series

MDS 9200 Series

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

MDS 9000 Family

Add/Drop Multiplexer (ADM)

DS-CWDMOADM4A

4-channel CWDM optical ADM (OADM) module (Cisco CWDM 1470, 1490, 1510, or 1530 NM Add/Drop Module)

MDS 9000 Family

DS-CWDMOADM4B

4-channel CWDM OADM module (Cisco CWDM 1550, 1570, 1590, or 1610 NM Add/Drop Module)

MDS 9000 Family

DS-CWDM-MUX8A

ADM for 8 CWDM wavelengths

MDS 9000 Family

CWDM Multiplexer Chassis

DS-CWDMCHASSIS

2-slot chassis for CWDM ADMs

MDS 9000 Family

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

External 512-MB CompactFlash memory for supervisor module

MDS 9500 Series

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

Smart Card Reader

DS-SCR-K9

Storage Media Encryption (SME) Smart Card Reader

MDS 9000 Family

Smart Card

DS-SC-K9

SME Smart Card

MDS 9000 Family

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

Cisco MDS 8-Gb Fabric Switch for HP c-Class Blade System

Yes

MDS 9134

Yes1

MDS 9124

Yes 1

Cisco MDS 4-Gbps Fabric Switch for HP c-Class BladeSystem

Yes 1

Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter

Yes 1

1.Cisco NX-OS Release 5.2 is not supported on this switch; Cisco NX-OS Release 5.0 is supported.


Note NX-OS Release 5.2(1) software images are not available for these switches: Cisco MDS 9134, Cisco MDS 9124, Cisco MDs 4-Gbps Fabric Switch for HP c-Class BladeSystem, and Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter.


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 .

 

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

Module
Description
MDS 9500 Series
MDS 9222i
NX-OS 5.2(1)
NX-OS 5.0(x)
NX-OS 5.2(1)
NX-OS 5.0(x)

DS-X9530-SF2-K9

MDS 9500 Supervisor-2 Module

Yes

Yes

N/A

N/A

DS-X9530-SF2A-K9

MDS 9500 Supervisor-2A Module

Yes

Yes

N/A

N/A

DS-13SLT-FAB3

MDS 9513 Fabric Module 3

Yes

No

N/A

N/A

DS-13SLT-FAB2

MDS 9513 Fabric Module 2

Yes

Yes

N/A

N/A

DS-13SLT-FAB1

MDS 9513 Fabric Module 1

Yes

Yes

N/A

N/A

DS-X9708-K9

8-port 10-Gbps FCoE Module

Yes2,3

No

No

No

DS-X9232-256K9

32-port 8-Gbps Advanced Fibre Channel Switching Module

Yes 1

No

No

No

DS-X9248-256K9

48-port 8-Gbps Advanced Fibre Channel Switching Module

Yes 1

No

No

No

DS-X9224-96K9

24-port 8-Gbps Fibre Channel Switching Module

Yes 1

Yes4

No

No

DS-X9248-96K9

48-port 8-Gbps Fibre Channel Switching Module

Yes 1

Yes 3

No

No

DS-X9248-48K9

4/44-port Host Optimized8-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

DS-X9316-SSNK9

16-port Storage Services Node (SSN-16)

Yes

Yes

Yes

Yes

DS-X9304-18K9

18/4-Port Multiservice Module (MSM-18/4)

Yes

Yes

Yes

Yes

DS-X9112

12-port 4-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

DS-X9124

24-port 4-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

DS-X9148

48-port 4-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

DS-X9704

4-port 10-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

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

3.Requires the Supervisor-2A module.

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

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

Yes5

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

Yes6

No

No

DS-X9248-96K9

48-port 8-Gbps Fibre Channel Switching Module

Yes 2

No

No

DS-X9248-48K9

4/44-port Host Optimized8-Gbps Fibre Channel Switching Module

Yes

Yes

No

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

DS-X9302-14K9

14/2-port Multiprotocol Services (MPS-14/2) Module

Yes

No

Yes

DS-X9016

16-port 1-, 2-Gbps Fibre Channel Switching Module

Yes

No

Yes

DS-X9032

32-port 1-, 2-Gbps Fibre Channel Switching Module

Yes

No

Yes

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

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

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

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

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

Yes7

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 Module

No

No

No

No

No

DS-X9248-96K9

48-port 8-Gbps Fibre Channel Switching Module

No

No

No

No

No

DS-X9248-48K9

4/44-port Host Optimized8-Gbps Fibre Channel Switching Module

No

No

No

No

No

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

Yes

Yes

Yes

Yes

No

DS-X9112

12-port 4-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

No

DS-X9124

24-port 4-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

No

DS-X9148

48-port 4-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

No

DS-X9704

4-port 10-Gbps Fibre Channel Switching Module

Yes

Yes

Yes

Yes

No

DS-X9302-14K9

14/2-port Multiprotocol Services (MPS-14/2) Module

Yes

No

Yes

Yes

Yes

DS-X9016

16-port 1-, 2-Gbps Fibre Channel Switching Module

Yes

No

Yes

Yes

Yes

DS-X9032

32-port 1-, 2-Gbps Fibre Channel Switching Module

Yes

No

Yes

Yes

Yes

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

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

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

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

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 Cisco DCNM for SAN, 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

Cisco NX-OS Software
Minimum NX-OS or SAN-OS Release
Tested NX-OS and SAN-OS Releases

NX-OS Release 5.2(1)

NX-OS Release 5.0(1a) or later

NX-OS Release 5.0(1a) and later

NX-OS Release 4.2(3) or later

NX-OS Release 4.2(3) and later

SAN-OS Release 3.3(5) or later

SAN-OS Release 3.3(5) and later

Cisco DCNM for SAN Software
Minimum NX-OS or SAN-OS Release
Tested NX-OS and SAN-OS Releases

DCNM for SAN Release 5.2(1)

NX-OS Release 5.0(1a) or later

NX-OS Release 5.0(1a) and 5.0(4b)

NX-OS Release 4.2(3) or later

NX-OS Release 4.2(3) and 4.2(7e)

SAN-OS Release 3.3(5) or later

SAN-OS Release 3.3(5) and 3.3(5b)

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:

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 Cisco DCNM for SAN to perform the downgrade, enables the compatibility check. The check indicates if the upgrade can happen nondisruptively or disruptively depending on the current configuration of your switch and the reason.

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

At a minimum, you need to disable the default device alias distribution feature using the no device-alias distribute command in global configuration mode. The show incompatibility system bootflash: 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,
MDS 9124,
Cisco MDs 4-Gbps Fabric Switch for HP c-Class BladeSystem,
Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter

NX-OS Release 5.2(1) software images are not available for these switches.

MDS 9148,
Cisco MDS 8Gb Fabric Switch for HP c-Class BladeSystem

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

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

Filename begins with m9500-sf2ek9

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
 

NPE Software Images

No payload encryption (NPE) images are available with some releases of Cisco MDS NX-OS Release 5.2(x) software. The NPE images are intended for countries who have import restrictions on products that encrypt payload data.

To differentiate an NPE image from the standard software image, the letters npe are included in the image name as follows:

  • m9500-sf2ek9-kickstart-mz-npe.5.2.2.bin
  • m9500-sf2ek9-mz-npe.5.2.2.bin

When downloading software, ensure that you select the correct software images for you Cisco MDS 9000 Series switch. Nondisruptive software upgrades or downgrades between NPE images and non-NPE images are not supported.

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:


Note Before you begin the upgrade process, review the list of chassis and modules that Cisco MDS NX-OS Release 5.2(1) supports. See the “MDS 9000 Chassis and Module Support” section.


For detailed instructions for performing a software upgrade using Cisco DCNM, see the Cisco DCNM Release Notes, Release 5.2 , which is available from the following website:

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

Upgrading to Cisco NX-OS Release 5.2 from Release 5.0(8)

A nondisruptive software upgrade from NX-OS Release 5.0(8) to any NX-OS Release 5.2(x) requires a module reload if you have any of the following modules deployed in your Cisco MDS 9000 system:

  • 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 Optimized 8-Gbps Fibre Channel Switching Module
  • DS-X9304-18K9, 18/4-Port Multiservice Module (MSM-18/4)

If you perform a nondisruptive software upgrade from NX-OS Release 5.0(8) to any NX-OS Release 5.2(x) on a Cisco MDS 9222i switch, you must reload the switch following the upgrade.

In addition, some features and applications might stop working if they are running on a Cisco MDS 9000 system that uses the hardware devices mentioned previously. These features and applications include IVR, IOA, SME, DMM, fcflow, and SPAN.

For additional information, see Field Notice 63504. The open caveat CSCty32238 also provides details.

Upgrading Guidelines Specific to NX-OS Release 5.2(1)

Follow these guidelines when upgrading to Cisco MDS NX-OS Release 5.2(1):

  • Follow the upgrade path to NX-OS Release 5.2(1) that is specified in Table 11 . The only supported upgrade path is from Release 5.0(x).
  • Upgrade to NX-OS Release 5.2(1) before you install any Generation 4 module in an MDS 9500 Series switch. Generation 4 modules include the FCoE module and the 32-port and 48-port 8-Gbps Advanced Fibre Channel modules. (See the “New Hardware” section for a list of Generation 4 hardware.) NX-OS Release 5.2(1) is needed for the switch to recognize the new hardware.
  • Perform a full switch reload on an MDS 9509 or MDS 9506 switch after you install NX-OS Release 5.2(1) and install any Generation 4 module, including the FCoE module. The switch reload is required for the new hardware to come up. Once you perform the switch reload, the fabric mode changes to support the Generation 4 hardware. Because of the changed fabric mode, you cannot subsequently perform a nondisruptive software downgrade from NX-OS Release 5.2(1). For additional information, see the “Downgrading Guidelines Specific to NX-OS Release 5.2(1)” section
  • Ensure that you have a Supervisor-2A module (DS-X9530-SF2A-K9) installed in a MDS 9500 Series switch if you plan to use the Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) (DS-X9708-K9).
  • We recommend that you delete any SPAN configuration, Fibre Channel tunnel, or tunnel-ID map configuration from your switch before you start the upgrade to NX-OS Release 5.2(1). You can save the SPAN destination and SPAN target configuration and then reconfigure the SPAN session following the upgrade. All SPAN destination and SPAN target ports are reinitialized after the upgrade. To gather information about SPAN sessions and delete them, use the following commands in this order:

show incompatibility systems bootflash: image_name to display any incompatible configurations

show span session to check the current configuration for a SPAN session

no span session session-number to delete a SPAN session

show running-config | include fc-tunnel to check the current Fibre Channel tunnel configuration

no interface fc-tunne l y to delete a Fibre Channel tunnel on the switch that is the source for the Fibre Channel tunnel

show interface brief | include SD to check the current configuration for a SPAN destination port configuration

show interface brief | include ST to check the current configuration for a SPAN target port configuration

no fc-tunnel tunnel-map z interface x/y to remove an Fibre Channel tunnel map

no switchport mode sd to negate the SPAN destination port mode for the SPAN destination port

no switchport mode st to negate the SPAN target port mode for the SPAN target port

  • If you are using IVR non-NAT mode, migrate to IVR-NAT mode before you upgrade to NX-OS Release 5.2(1). IVR non-NAT mode is deprecated in NX-OS Release 5.2(1).

Note In dual SAN fabrics, IVR traffic can use one fabric while the other fabric is migrating. Only IVR traffic is disrupted during the migration. Regular traffic within the VSAN is not disrupted during the migration.


To migrate to IVR-NAT mode, follow these steps:

1. Stop or divert all applications on servers that depend on IVR.

If CFS distribution is not enabled for IVR, then perform steps 2 through 4 on all switches where IVR is enabled.

If CFS distribution is enabled for IVR, then enter the ivr commit command following step 2, step 3, and step 4 to distribute the changes to other switches.

2. Deactivate the IVR zone set by entering the no ivr zoneset activate command.

3. Enable IVR NAT by entering the ivr nat command.

4. Activate the IVR zone set by entering the ivr zoneset activate command.

5. Start or re-establish all application that were stopped in step 1.

The network can now run in IVR-NAT mode.

General Upgrading Guidelines

Follow these general guidelines before performing a software upgrade:

  • Review the nondisruptive upgrade path to release 5.2(1) in Table 11 .
  • Install and configure dual supervisor modules before the upgrade.
  • Issue the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive.
  • 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 Table 11 for the nondisruptive upgrade path for all NX-OS and SAN-OS releases.

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

FICON : If you have FICON enabled, the upgrade path is different. See the “FICON Supported Releases and Upgrade Paths” section.


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.


Nondisruptive Upgrade Paths

Use Table 11 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 5.2(1). Find the image release number you are currently using in the “Current Release” column of the table and follow the steps in the order specified to perform the upgrade.


Note See Table 14 before performing a software upgrade on a Cisco MDS 9509 or 9506 switch to dertermine if the upgrade is disruptive or nondisruptive.



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



Note If you plan to install a Generation 4 module after you upgrade to Cisco MDS NX-OS Release 5.2(1), you may need to reload the switch to enable the increased bandwidth that is available in the Generation 4 module. See the Cisco MDS 9500 Series Hardware Installation Guide for instructions on migrating to the Generation 4 8-Gbps Advanced Fibre Channel switching modules.



Caution Upgrading to Cisco NX-OS Release 5.2(1) without first upgrading to Release 5.0(x) is not recommended and not supported, and might result in configuration loss. The only supported upgrade path to Release 5.2(1) is from Release 5.0(x).

 

Table 11 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 5.2(1)

Current Release
Nondisruptive Upgrade Path and Ordered Upgrade Steps

NX-OS:

All 5.0(x) releases

Upgrade directly to NX-OS Release 5.2(1)9.

All 4.2(x) releases

1. Upgrade to NX-OS Release 5.0(x).

2. Upgrade to NX-OS Release 5.2(1).

All 4.1(x) releases

1. Upgrade to NX-OS Release 5.0(x).

2. Upgrade to NX-OS Release 5.2(1).

SAN-OS:

Release 3.3(1c), 3.3(2), 3.3(3), 3.3(4x), and 3.3(5x).

1. Upgrade to NX-OS Release 4.1(x) or 4.2(x).

2. Upgrade to NX-OS Release 5.0(x).

3. Upgrade to NX-OS Release 5.2(1).

Release 3.2(1a), all 3.2(x), 3.1(x), and 3.0(x) releases, and release 2.1(3), 2.1(2e), 2.1(2d), and 2.1(2b)

1. Upgrade to SAN-OS Release 3.3(1c).

2. Upgrade to NX-OS Release 4.1(x) or 4.2(x).

3. Upgrade to NX-OS Release 5.0(x).

4. Upgrade to NX-OS Release 5.2(1).

Release 2.1(2), 2.1(1b), 2.1(1a), and
2.0(x)

1. Upgrade to SAN-OS Release 2.1(2b), 2.1(2d), 2.1(2e), or 2.1(3).

2. Upgrade to SAN-OS Release 3.3(1c).

3. Upgrade to NX-OS Release 4.1(x) or 4.2(x).

4. Upgrade to NX-OS Release 5.0(x).

5. Upgrade to NX-OS Release 5.2(1).

Release 1.x

1. Upgrade to SAN-OS Release 1.3(4a).

2. Upgrade to SAN-OS Release 2.1(2b).

3. Upgrade to SAN-OS Release 3.3(1c).

4. Upgrade to NX-OS Release 4.1(x) or 4.2(x).

5. Upgrade to NX-OS Release 5.0(x).

6. Upgrade to NX-OS Release 5.2(1).

9.If you are upgrading from Cisco NX-OS Release 5.0(8) see the “Upgrading to Cisco NX-OS Release 5.2 from Release 5.0(8)” section before you begin the upgrade process.

FICON Supported Releases and Upgrade Paths

Cisco MDS NX-OS Release 5.2(1) is not a FICON-certified release.

Table 12 lists the SAN-OS and NX-OS releases that are certified for 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(7b)

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 the nondisruptive upgrade path for FICON-certified releases. 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

Current Release with FICON Enabled
Upgrade Path

NX-OS Release 4.2(1b)

You can nondisruptively upgrade directly to NX-OS Release 4.2(7b).

NX-OS Release 4.1(1c)

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

SAN-OS Release 3.3(1c)

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

SAN-OS Release 3.2(2c), 3.0(3b), 3.0(3), and 3.0(2).

First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS Release 4.2(1b).

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:

Downgrading Guidelines Specific to NX-OS Release 5.2(1)

The following guideline applies to a downgrade from Cisco MDS NX-OS Release 5.2(1):

  • You cannot nondisruptively downgrade from NX-OS Release 5.2(1) to NX-OS Release 5.0(x) if you installed NX-OS Release 5.2(1) on an MDS 9509 or MDS 9506 switch and you installed a Generation 4 module in the switch and performed a full switch reload. The reason for this restriction is the change in fabric mode that occurs following the switch reload with the Generation 4 hardware installed. The downgrade will be disruptive, even if you remove the Generation 4 module prior to starting the downgrade.

If you do not install Generation 4 hardware or perform a full switch reload following the installation of NX-OS Release 5.2(1) on an MDS 9509 or MDS 9506 switch, then you can nondisruptively downgrade to NX-OS Release 5.0(x).

  • We recommend that you delete any SPAN configuration, Fibre Channel tunnel, or tunnel-ID map configuration from your switch before you downgrade from NX-OS Release 5.2(1) to a lower version. If any SPAN session, SPAN destination, SPAN target, or Fibre Channel tunnel interface is configured, the installer should detect it and prompt you to delete these configurations.

To gather information about SPAN sessions and delete them, use the following commands in this order:

show incompatibility systems bootflash: image_name to display any incompatible configurations

show span session to check the current configuration for a SPAN session

no span session session-number to delete a SPAN session

show running-config | include fc-tunnel to check the current Fibre Channel tunnel configuration

no interface fc-tunne l y to delete a Fibre Channel tunnel on the switch that is the source for the Fibre Channel tunnel

show interface brief | include SD to check the current configuration for a SPAN destination port configuration

show interface brief | include ST to check the current configuration for a SPAN target port configuration

no fc-tunnel tunnel-map z interface x/y to remove an Fibre Channel tunnel map

no switchport mode sd to negate the SPAN destination port mode for the SPAN destination port

no switchport mode st to negate the SPAN target port mode for the SPAN target port

General Downgrading Guidelines

Follow these general guidelines before you perform a a software downgrade:

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

FCoE: Fibre Channel over Ethernet requires Cisco NX-OS Release 5.2(1). A downgrade from Release 5.2(1) disrupts and stops all FCoE traffic.

Fibre Channel Ports : Fibre Channel ports can be nondisruptively downgraded without affecting traffic on the ports. See Table 15 for the nondisruptive downgrade path for all SAN-OS releases.

Gigabit Ethernet Ports : Traffic on Gigabit Ethernet ports is disrupted during a downgrade. This includes IPS modules and the Gigabit Ethernet ports on 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.

FICON : If you have FICON enabled, the downgrade path is different. See the “FICON Downgrade Paths” section.

NX-OS Release 5.2(x) and Release 5.0(x) Software Downgrade and Upgrade Matrix for Cisco MDS 9509 and 9506 Switches

See the compatibility information in Table 14 to determine if a downgrade to, or upgrade from Release 5.0(x) software is disruptive or nondisruptive on a Cisco MDS 9509 or 9506 switch.

Table 14 NX-OS Release 5.2(x) and Release 5.0(x) Downgrade and Upgrade Matrix

Downgrade Path on a Cisco MDS 9509 or 9506 Switch
Current Release
Desired Release
Expected Behavior
Observed Behavior

5.2(1)

5.0(7) or 5.0(8)

Disruptive

Disruptive

5.0(7) or 5.0(8)

5.0(1a), 5.0(1b), or 5.0(4)

Disruptive

Nondisruptive
The user is expected to explicitly reload the switch using the reload command.

5.0(7) or 5.0(8)

4.2(x) or 4.1(x)

Disruptive

Disruptive

5.0(4)

5.0(1a)

Nondisruptive

Nondisruptive

5.0(1a), 5.0(1b), or 5.0(4)

4.2(x) or 4.1(x)

Nondisruptive

Nondisruptive

Upgrade Path on a Cisco MDS 9509 or 9506 Switch
Current Release
Desired Release
Expected Behavior
Observed Behavior

5.2(1) or 5.2(2a)

5.2(2d)

Nondisruptive

Nondisruptive

5.0(7) or 5.0(8)

5.2(x)

Nondisruptive
Support for Generation 4 modules is available.

Nondisruptive
Support for Generation 4 modules is available.

5.0(1a), 5.0(1b), or 5.0(4)

5.2(x)

Nondisruptive
Support for Generation 4 modules is not available.

Nondisruptive
Support for Generation 4 modules is not available.

Use Table 15 to determine the nondisruptive downgrade path from Cisco NX-OS Release 5.2(1). Find the NX-OS or SAN-OS image tha you want to downgrade to in the “To SAN-OS Release” column of the table and follow the steps in the order specified to perform the downgrade.


Note The software downgrade information in Table 15 applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP and intelligent services traffic.


 

Table 15 Nondisruptive Downgrade Path from NX-OS Release 5.2(1)

To NX-OS or SAN-OS Release
Nondisruptive Downgrade Path and Ordered Downgrade Steps

NX-OS:

All 5.0(x) releases

Downgrade directly from NX-OS Release 5.2(1).10, 11, 12

All 4.2(x) and 4.1(x) releases

1. Downgrade to NX-OS Release 5.0(x). 2

2. Downgrade to NX-OS Release 4.2(x) or 4.1(x).

SAN-OS:

All 3.3(x) releases

1. Downgrade to NX-OS Release 5.0(x).

2. Downgrade to NX-OS Release 4.2(x) or Release 4.1(x).

3. Downgrade to SAN-OS Release 3.3(x).

All 3.2(x), 3.1(x), 3.0(x) releases, and all 2.1(x) releases.

1. Downgrade to NX-OS Release 5.0(x).

2. Downgrade to NX-OS Release 4.2(x) or Release 4.1(x).

3. Downgrade to SAN-OS Release 3.3(x).

4. Downgrade to SAN-OS Release 3.2(x), Release 3.1(x)., Release 3.0(x), or Release 2.1(x).

All 2.0(x) releases.

1. Downgrade to NX-OS Release 5.0(x).

2. Downgrade to NX-OS Release 4.2(x) or Release 4.1(x).

3. Downgrade to SAN-OS Release 3.3(x).

4. Downgrade to SAN-OS Release 2.1(2x).

5. Downgrade to SAN-OS Release 2.0(x).

Release 1.x

1. Downgrade to NX-OS Release 5.0(x).

2. Downgrade to NX-OS Release 4.2(x) or Release 4.1(x).

3. Downgrade to SAN-OS Release 3.3(x).

4. Downgrade to SAN-OS Release 2.1(2b).

5. Downgrade to SAN-OS Release 1.3(4a).

6. Downgrade to SAN-OS Release 1.x.

10.Before downgrading to NX-OS RElease 5.0(8) or Release 5.0(7) on an MDS 9509 or MDS 9506 switch, see the “NX-OS Release 5.2(x) and Release 5.0(x) Software Downgrade and Upgrade Matrix for Cisco MDS 9509 and 9506 Switches” section.

11.If you install a Generation 4 module in an MDS 9509 or MDS 9506 switch and perform a full switch reload following the installation of NX-OS Release 5.2(1), then you cannot nondisruptively downgrade from NX-OS Release 5.2(1) to NX-OS 5.0(x).

12.A downgrade from NX-OS Release 5.2(1) disrupts and stops all FCoE traffic because FCoE requires Cisco NX-OS Release 5.2(x).

FICON Downgrade Paths

Table 16 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 16 FICON Downgrade Path

To Release with FICON Enabled
Downgrade Path

NX-OS Release 4.2(1b)

You can nondisruptively downgrade directly from NX-OS Release 4.2(7b).

NX-OS Release 4.1(1c)

You can nondisruptively downgrade directly from NX-OS Release 4.2(1b).

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

New Features in Cisco MDS NX-OS Release 5.2(1)

Cisco MDS NX-OS Release 5.2(1) is a major software release that includes new features, enhancements, new hardware, and bug fixes. Enhancements in this release to Cisco MDS 9000 switches enable convergence, scale, and intelligence in the data center.

In addition to the information about new features that is included in this Release Notes document, you can find more product information about Cisco MDS 9000 NX-OS and SAN-OS Software at this link:

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

New Software Features

Cisco NX-OS Release 5.2(1) supports the following software features:

  • Software support for the MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) module

The MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) module is a multihop-capable FCoE module for the core data center. This full line-rate FCoE module for the MDS 9500 Series Director switches allows you to extend FCoE benefits beyond the access Layer into the data center core. FCoE supports I/O consolidation by preserving all Fibre Channel constructs, and maintaining the same latency, security, and traffic management attributes of Fibre Channel. In addition, FCoE extends Fibre Channel SAN connectivity to Cisco Nexus 7000 switches that are FCoE capable.

  • Software support for Cisco MDS 9000 Family 8-Gbps Advanced Fibre Channel Switching Modules

Cisco NX-OS Release 5.2(1) includes software support for the 32-port and the 48-port 8-Gbps Advanced Fibre Channel switching modules that can be used in the MDS 9500 Series Directors. The MDS 9513 Multilayer Director can be upgraded with the new Generation 4 Fabric-3 module to increase bandwidth to 256 Gbps per slot. In addition, the 8-Gbps Advance Fibre Channel switching module support speeds of 10 Gbps on the MDS 9513 with the Fabric-3 module installed. The upgrade from the Fabric-2 module to the Fabric-3 module is nondisruptive.

Cisco MDS 9000 8-Gbps Advanced Fibre Channel switching modules support Cisco FlexSpeed technology that enables ports to be configured as either 1-, 2-, 4-, or 8-Gbps, or 10-Gbps Fibre Channel interfaces.

Cisco MDS 9000 8-Gbps Advanced Fibre Channel switching modules support Arbitrated Local Switching to locally switch traffic at line rate 8-Gbps in a fair manner across all ports on the module through central arbitration.

  • Storage Media Encryption for Disk

The Storage Media Encryption (SME) solution, which currently protects data at rest on heterogeneous tape drives and virtual tape libraries (VTLs), has been enhanced to encrypt data on disk arrays in a SAN environment using secure IEEE-standard Advanced Encryption Standard (AES) algorithms.

SME Disk requires the Storage Media Encryption Package license.

See the Cisco MDS 9000 Family Storage Media Encryption Configuration Guide for more information on configuring and deploying SME Disk.

  • Cisco Data Center Network Manager for SAN

Cisco Fabric Manager and Cisco Data Center Network Manager have merged into a unified product that can now manage and monitor both SAN and LAN environments. As a part of this merger, Cisco Fabric Manager has been rebranded as Cisco DCNM for SAN.

As a part of NX-OS Release 5.2(1), DCNM for SAN introduces server-based licenses that allow you to purchase a pool of DCNM for SAN licenses instead of a switch-based Fabric Manager Server (FMS) license. The installed base of existing FMS licenses are grandfathered into DCNM for SAN, which means that you do not have to purchase a new license to use DCNM for SAN if you have an existing FMS license.

There are many new features in DCNM for SAN, including:

Summary and host dashboards

VMware topology and performance

Performance forecasting charts

External SMI-S 1.4 agent

FCoE provisioning and management

Detailed information about these new features is available in the Cisco DCNM Release Notes, Release 5.2 , and in the feature configuration guides for DCNM for SAN.

New Hardware

Cisco MDS NX-OS Release 5.2(1) supports the following new Generation 4 hardware devices:

  • Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) module (DS-X9708-K9)
  • Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching module (DS-X9232-256K9)
  • Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching module (DS-X9248-256K9)
  • Cisco MDS 9513 Switching Fabric 3 module (DS-13SLT-FAB3)

See the Cisco MDS 9500 Series Hardware Installation Guide for descriptions of, and specifications for the new Generation 4 modules. This guide also provides instructions for migrating to the new Fabric 3 module and guidelines for installing the new 8-Gbps Advanced Fibre Channel switching modules.

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


Note A license is not required to use the Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) module (DS-X9708-K9).


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 Media Encryption Package

The Cisco MDS 9000 Storage Media Encryption package enables encryption of data at rest on heterogeneous tape devices, virtual tape libraries, and disk arrays as a transparent fabric service. Cisco SME is completely integrated with Cisco MDS 9000 Family switches and the Cisco DCNM for SAN application, enabling highly available encryption services to be deployed without rewiring or reconfiguring SANs, and allowing them to be managed easily without installing additional management software. Refer to the Cisco MDS 9000 Storage Media Encryption package fact sheet for more information. The Storage Media Encryption package is for use only with Cisco MDS 9000 Family switches.

Data Mobility Manager Package

The Cisco MDS 9000 Data Mobility Manager package enables data migration between heterogeneous disk arrays without introducing a virtualization layer or rewiring or reconfiguring SANs. Cisco DMM allows concurrent migration between multiple LUNs of unequal size. Rate-adjusted migration, data verification, dual Fibre Channel fabric support, and management using Cisco DCNM for SAN provide a complete solution that greatly simplifies and eliminates most downtime associated with data migration. Refer to the Cisco MDS 9000 Data Mobility Manager package fact sheet for more information. The Data Mobility Manager package is for use only with Cisco MDS 9000 Family switches.

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.

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.

Deprecated Features

Cisco MDS NX-OS Release 5.2 no longer supports the features listed in the following sections:

Zoning Features

LUN zoning, read-only zones, and broadcast zones are no longer supported. These features affect the following hardware:

  • Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) module
  • Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching module
  • Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching module

You cannot bring up these modules if these features are already configured. You should completely remove all configurations that include these features before you attempt to bring up these modules. In addition, you cannot configure these features after you bring up these modules.

SNIA Common Information Model

SNIA Common Information Model (CIM or cimserver) commands are no longer supported. CIM is supported in Cisco DCNM-SAN Release 5.2. The SMI-S agent that is installed on the Cisco DCNM-SAN server allows external application to access fabric and switch profiles as specified in SNIA CIM. For additional information, see the Cisco DCNM Release Notes, Release 5.2.

IVR Non-NAT Mode

IVR non-NAT mode is not supported in Cisco NX-OS Release 5.2(x). If you have IVR non-NAT mode configured, see the “Upgrading Guidelines Specific to NX-OS Release 5.2(1)” section for instructions on how to migrate to IVR NAT mode before upgrading to Cisco NX-OS Release 5.2(1).

Limitations and Restrictions

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

FCoE Module

  • In Cisco MDS NX-OS Release 5.2(1), you cannot install a FCoE module in a switch that is running DMM, SME, or IOA.
  • Link traps for FCoE devices are sent only when a VFC interface flaps.

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

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:


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.

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.

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

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.

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.

Configuring a Persistent FCID in an IVR Configuration with Brocade Switches

The following information is relevant if you have a fabric that consists of Cisco MDS 9000 switches and Brocade switches, and the Cisco MDS switches are running either NX-OS Release 4.x or Release 5.x and Brocade is running FOS higher than 6.x. In an IVR configuration, when IVR NAT is enabled on a Cisco MDS 9000 switch, the device in the native VSAN should be configured with a persistent FCID. Assuming the FCID is 0xAABBCC, AA should be configured with the virtual IVR domain ID of the VSAN that contains the ISLs and BB should be configured in the following range:

  • 1 through 64 if the Brocade switch is operating in native interop mode.
  • 1 through 30 if the Brocade switch is operating in McData Fabric mode or McData Open Fabric Mode.

This configuration ensures that the devices connected to the Cisco MDS 9000 switch can be seen in the name server database on the Brocade switch.

Configuring NPIV

N port identifier virtualization (NPIV) provides a means to assign multiple port IDs to a single N Port. This feature allows multiple applications on the N port to use different identifiers and allows access control, zoning, and port security to be implemented at the application level.

You must globally enable NPIV for all VSANs on the MDS switch to allow the NPIV-enabled applications to use multiple N port identifiers.

Use the feature npiv command in configuration mode to enable NPIV for all VSANs on a switch. Enabling NPIV is nondisruptive.

Caveats

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

.

Table 17 Open Caveats and Resolved Caveats Reference

DDTS Number
NX-OS Software Release (Open or Resolved)
NX-OS Software Release (Open or Resolved)
5.0(4d)
5.2(1)

Severity 1

CSCto68011

O

R

Severity 2

CSCtf11784

O

R

CSCth10234

O

R

CSCth80324

O

R

CSCti73204

O

R

CSCtj92295

R

CSCtk47039

O

R

CSCtl86272

O

R

CSCtn01631

O

R

CSCtn88331

O

R

CSCtn72391

O

O

CSCtq41235

O

CSCtq60165

O

R

CSCtq76711

O

CSCtq79432

O

CSCtq88900

O

CSCtr10877

O

CSCtr24502

O

CSCtr27068

O

CSCtr27150

O

CSCtr36554

O

CSCtr49389

O

CSCts88422

O

CSCty32238

O

O

CSCty85364

O

CSCua61044

O

Severity 3

CSCtd04154

O

R

CSCte70856

O

R

CSCtl53991

O

R

CSCtl58793

O

R

CSCtl97673

O

R

CSCtn26967

O

R

CSCtn29907

O

R

CSCtn48728

O

R

CSCtn66877

R

CSCtn93079

O

R

CSCtn95730

O

R

CSCto62199

O

R

CSCto88318

O

R

CSCtq01451

R

CSCtq35662

O

CSCtq40455

O

R

CSCtq42878

O

CSCtr04426

O

CSCtr29423

O

CSCtr42322

O

CSCtr44412

O

CSCtr50223

O

CSCtr55608

O

CSCty97827

O

O

CSCui62316

O

Severity 4

CSCtn68418

O

O

Resolved Caveats

  • CSCto68011

Symptom : The fcdomain service on both supervisor modules fails, which results in a reload of the device. An error message similar to the following message is displayed:

%SYSMGR-2-SERVICE_CRASHED: Service ''fcdomain'' (PID 4688) hasn't caught signal 11 (core will be saved)

This issue affects the following products when are they configured with SNMP:

Cisco MDS 9000 Series Multilayer Switches

Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series, running in FC Switching Mode (NPV mode is not affected).

The Cisco Unified Computing System documented in Cisco Bug ID CSCto77342.

The following products are confirmed not vulnerable:

Cisco Nexus 7000 series switches

Cisco Nexus 4000 series switches

Workaround : This issue is resolved.

  • CSCtf11784

Symptom : The zone process failed. The output of the show logging log command has the following error message:

%SYSMGR-2-SERVICE_CRASHED: Service "zone" (PID 17567) hasn't caught signal 11 (core will be saved)

Workaround : This issue is resolved.

  • CSCth10234

Symptom : An MDS 9000 Family switch does not send the following traps, which should be sent when a link goes up or down:

IETF-extended-linkDown

IETF-extended-linkUp

cisco-extended-linkDown

cisco-extended-linkUp

Workaround : This issue is resolved.

  • CSCth80324

Symptom : FCIP links flap due to maximum TCP retransmissions (“TCP conn. closed - retransmit failure”), or to extended pings to a peer FCIP switch that shows packet loss. This issue is due to a buffer leak that is caused when ICMP unreachables are generated in response to frames with an unreachable source address, such as 0.0.0.0.

This issue can be seen on all Ethernet ports on the MSM-18/4 module and the MDS 9222i switch, when either is running Cisco NX-OS Release 4.2(1) or later, or Cisco NX-OS Release 5.0(1) or later.

Workaround : This issue is resolved.

  • CSCti73204

Symptom : The show interface ethernet flowcontrol command entered on an MDS 9000 Family switch returned the message: “Internal error.”

Workaround : This issue is resolved.

  • CSCtj92295

Symptom : An MDS 9000 Family switch fails in the wwnmanager process. Use the s how logging log command and the show cores command to confirm the issue:

switch# 2010 Nov 8 06:38:28 sw-dc3-br1-51 %SYSMGR-2-SERVICE_CRASHED: Service

"wwn" (PID 2897) hasn't caught signal 6 (core will be saved).

switch# sh core

Module Instance Process-name PID Date(Year-Month-Day Time)

------ -------- --------------- -------- -------------------------

8 1 wwn 2897 2010-11-08 06:38:33

Workaround : This issue is resolved.

  • CSCtk47039

Symptom : An MDS 9000 Family switch does not respond to an FDISC from an NPV attached switch if the MDS 9000 switch is already processing an FDISC for the same PWWN. This issue occurs when the downstream device is running in NPV mode and the FDISC for the same PWWN must be in progress and no ABTS is sent to cancel the in-progress FDISC.

Workaround : This issue is resolved.

  • CSCtl86272

Symptom : Following a software upgrade on a MDS 9222i switch, traffic failures occurred between a newly configured flow, such as a regular zone flow, an FC-redirect flow, and an IVR flow. The ACL TCAM entry for the affected flow has no adjacency pointer and therefore no forwarding information for the flow, as can be seen by entering the following commands:

switch# attach mod x

switch# show process acltcam fwd-engine 0 input interface fcy/z

...

Loc cl vsan s_id d_id si up sof ipda dport prot sy fi fr en | pri mod ctl adj up vld cw stats ce

-------------------------------------------------------------------------------------------------------

...

6ef6 2 64 7d0109 7d0101 1 0 0 0 0 0 0 0 0 0 | 0 0 0 0 0 1 0 0 0

...

The following error can be seen in the error-history file for the acltcam process:

switch# att mod x

switch# show process acltcam internal errors

...

128) Event:E_DEBUG, length:91, at 553029 usecs after Fri Jan 21 20:41:27 2011

[107] acl_tcam_local_domain_list_init (3331):Unable to get local domains for existing vsans

...

Workaround : This issue is resolved.

  • CSCtn01631

Symptom : The Call Home process crashes and restarts when many RMON hc alerts are sent to Call Home.

Workaround : This issue is resolved.

  • CSCtn88331

Symptom : When you configure an FL port at any speed on a Generation 3 module, the speed is set by default to 2 Gbps. For example, if you configure the speed to be 8 Gbps, the actual speed on the hardware is set to 2 Gbps. This issue only occurs when an FL device is attached to a Generation 3 module.

Workaround : This issue is resolved.

  • CSCtq60165

Symptom : The IPS module fails and then reloads when FTA is enabled on the FCIP link for the Read Acceleration feature. This issue occurs when the software is in recovery mode and there appear to be packet drops on the FICON interfaces.

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. There is no interface defined or up in VSAN 1.

Workaround : This issue is resolved.

  • CSCte70856

Symptom : The Cisco Call Home feature stops sending Call Home alerts. In some situations, the Call Home feature might not be able to be configured or displayed. In addition, it might not be possible to save the configuration. The following syslog messages are logged:

%KERN-2-SYSTEM_MSG: mts_print_longest_queue_state: opcode counts for first and last 50 messages in pers_q of sap 66: - kernela

%KERN-2-SYSTEM_MSG: mts_print_msg_opcode_in_queue: opcode 4853 - 100 messages - kernel

%KERN-2-SYSTEM_MSG: mts_acquire_q_space() failing - no space in dst sap 66, uuid 63, src sap 28, opcode 4853 - kernel

This issue might be seen when the message level configured in Call Home is higher than that of the incoming alerts, such as from the RMON alerts from the port monitor feature.

Workaround : This issue is resolved.

  • CSCtl53991

Symptom : RMON alarms that check the percentage-utilization bandwidth threshold may sometimes fail to report accurate values. This issue might occur when an internal SNMP get of the interface utilization fails, which triggers a false-positive RMON alarm that indicates a bandwidth utilization on an interface that is incorrect.

Workaround : This issue is resolved.

  • CSCtl58793

Symptom : The Fabric Manager interface counters screen in the Protocol pull-down menu does not allow the use of the pencil eraser to clear the BBCreditTransitionFromZero counter.

Workaround : This issue is resolved.

  • CSCtl97673

Symptom : When the slow drain port-monitor policy is changed from its default configuration, there is no corresponding line added to the running configuration or the startup configuration. In addition, the slow drain policy activation configuration is lost after a switch reload; it is not lost upon a supervisor switchover.

Workaround : This issue is resolved.

  • CSCtn26967

Symptom : When an FCIP links starts dropping frames due to congestion control, there is no message given to the user. This issue occurs only in NX-OS Release 4.2 and later.

Workaround : This issue is resolved.

  • CSCtn29907

Symptom : When there is an IVR failure, a core file is produced, and a High Availability supervisor switchover occurs.

Workaround : This issue is resolved.

  • CSCtn48728

Symptom : Cisco devices running NX-OS software might send SNMP linkUp/linkDown trap information in an inconsistent order, which can create interoperability issues for third-party NMS applications.

Workaround : This issue is resolved.

  • CSCtn66877

Symptom : On the MDS 9124 switch, information about free memory is not consistent between CLI commands and SNMP.

Workaround : This issue is resolved.

  • CSCtn93079

Symptom : Call Home is not created for a standby supervisor failure. This issue was seen when the standby supervisor failed and was periodically being reset. When the switch was checked, the standby supervisor was in active state or powered on.

Workaround : This issue is resolved.

  • CSCtn95730

Symptom : An upgrade from SAN-OS Release 3.3(4) to Release 4.2(7a) on a Cisco MDS 9124e 24-port Fabric Switch for c-Class BladeSystem is disruptive. The install all command ended with the following messages before reload:

<date> unlock_local_module: Trying to unlock module 0

<date> unlock_local_module: failed to unlock module 0 (2)

Last reset......

Reason: Reset triggered due to HA policy of Reset

Service: fdmi hap reset

FC traffic interrupted

Workaround : This issue is resolved.

  • CSCto62199

Symptom : The Cisco 9222i switch spontaneously reboots itself, and the following stack trace can be seen in the output of the show system exception command:

STACK Call Trace:

[<f724ebf4>]str_isr_handle_cpm_one_intr_reg+0x94/0x310 [klm_str]

[<f724f4dc>]str_isr_cpm_0to3+0xf8/0x154 [klm_str]

[<f72510c0>]str_isr_bh+0x1bc/0x218 [klm_str]

[<c004cf50>]worker_thread+0x17c/0x228

[<c0052a8c>]kthread+0xec/0x128

[<c001bdf0>]original_kernel_thread+0x44/0x60

Workaround : This issue is resolved.

  • CSCto88318

Symptom : In certain rare circumstances, RADIUS authentication might stop working on a Cisco MDS 9000 Family switch. Use the show cores command to verify if the process failed.

switch# sh core

Module-num Instance-num Process-name PID Core-create-time

---------- ------------ ------------ --- ----------------

7 1 radius 2949 Apr 14 18:05

Workaround : This issue is resolved.

  • CSCtq01451

Symptom : The show ip interface command displays the error message “Internal error during command execution (11 8b)” on session termination.

The logging log file contains the message “%VSHD-2-VSHD_SYSLOG_EOL_ERR: EOL function ipconf_show_ip_if_all from library libipconfcli.so exited due to Signal 11.”

A VSH core file might also be generated.

Workaround : This issue is resolved.

  • CSCtq40455

Symptom : The interface VSAN membership configuration for a module that is powered off is missing after the configuration is saved. This issue can occur if you enter the copy running-configuration startup-configuration command while a module if powered off. It can also occur implicitly in some scenarios with FICON “active equals saved.”

Workaround : This issue is resolved.

  • CSCtq71703

Symptom : The interval for the default port-monitor policy is incorrect. The default is 60 seconds, but it should be 1 second.

Workaround : This issue is resolved.

Open Caveats

  • CSCtn72391

Symptom : Following a switch reload or a software upgrade, the startup configuration occasionally does not display feature fcip.

Workaround : Once the switch is completely up, copy the running configuration to the startup configuration by entering the copy running-config startup-config command.

  • CSCtq41235

Symptom : After you enter the shut command followed by the no shut command on a range of interfaces, STP convergence is slow. This issue might be seen because bringing up a large number of interfaces is delayed due to pacing of the interfaces.

Workaround : Enter the shut command followed by the no shut command on a smaller range of interfaces.

  • CSCtr10877

Symptom : Following an ISL flap that isolates some switches in the fabric (and the corresponding FCR peers) and then later merges them again, some FCR peers might get out of sync with the SSM switch FCR peer (that is, the FCR peer that owns a configuration) during the peer discovery phase. Consequently, some application flows might not come online, or might even get deleted.

Workaround : Enter the following supervisor commands on the problematic FCR peer, which will trigger this FCR peer to resync with the rest of the fabric, and force it to come out of the error state:

switch# test fc-redirect config sync-with-fabric

switch# test fc-redirect config sync-with-fabric all-peers

If more than one peer is affected by this issue, then do the following. If the application flows do not come online, then the application CLI commands s may need to be checked to verify that the flows did not get deleted. If they did, then the flows need to be recreated again through the application CLI command s or DCNM-SAN interface.

  • CSCtr24502

Symptom : Following a switch reload or a module reload, throughput drops with local switching enabled because the local switching configuration is lost after the reload.

Workaround : Enable local switching again after the switch reloads or the module reloads.

  • CSCtq76711

Symptom : The 8-port FCoE module (DS-X9708-K9) fails to boot up after it is power cycled. This issue might be seen if there are enough local routes to exhaust the hardware table space on the FCoE module.

Workaround : Remove enough local routes so that the remaining routes do not exhaust the hardware resources of the FCoE module and then reload the FCoE module.

  • CSCtq79432

Symptom : On the storage VDC of the switch, the default gateway and the IP address of the switch may not be reachable if they are configured using the setup script. This issue can occur when you use the setup script to configure the default gateway and IP address. The default gateway and IP address should be configured manually in the “default” VRF.

Workaround : Reconfigure the default-gateway and IP address in the “default” VRF

  • CSCtq88900

Symptom : In an SME or IOA deployment, if the number of H->T flows that are added exceeds 512, then subsequent disruptive platform events can leave an FCR unable to process interprocess (MTS) messages at a rate fast enough to support the scaled configuration. This situation can cause an MTS-buffers full condition in the FCR, which can result in unpredictable behavior. Some of the resulting errors may be unrecoverable, and may require a disruptive restart of the flows.

Workaround : Use CFS regions if a large number (greater than 512) of application flows need to be configured. CFS regions segment the FCR peer topology into manageable proportions.

  • CSCtr27068

Symptom : The port-group monitor feature is disabled on the 48-port 8-Gbps Advanced Fibre Channel switching module (DS-X9248-256K9).

Workaround : None.

  • CSCtr27150

Symptom : The port-group monitor feature is disabled on the 32-port 8-Gbps Advanced Fibre Channel switching module (DS-X9232-256K9).

Workaround : None.

  • CSCtr36554

Symptom : The feature manager causes high CPU usage on the standby supervisor. This issue occurs when the feature manager gets into a loop of sending messages to itself.

Workaround : Reload the standby supervisor.

  • CSCtr49389

Symptom : The system health serdes-loopback in t f c-port-range command that tests the health of a port using the serdes loopback on the 48-port 8-Gbps Advanced Fibre Channel switching module (DS-X9248-256K9) and the 32-port 8-Gbps Advanced Fibre Channel switching module (DS-X9232-256K9) fails if there is no SFP attached to the port. The following message is displayed:

Serdes loopback test on fcx/y failed. Failure reason: failed to initialize for testing.

Workaround : Attach an SFP to the port so that the test can pass and the port can come up.

  • CSCts88422

Symptom : A Cisco MDS 9000 switch sends a “Changed Switch Configuration” RSCN each time a management interface comes up, a management IP address is changed, or a switch name is changed. This notification is an RSCN Event Qualifier 4, and it is sent to all the devices that are logged in to the switch. However, some types of devices cannot properly handle RCSNs of this type which results in traffic disruption.

This symptom might be seen in switches running NX-OS Release 5.2(1), which is the release when the “Changed Switch Configuration” RSCN started being sent.

Workaround : None. Upgrade to NX-OS Release 5.2(2) or a later release. The issue is resolved in NX-OS Release 5.2(2) such that NX-OS software no longer sends the “Changed Switch Configuration" RSCNs.

  • CSCty32238

Symptom : On certain hardware, certain Cisco MDS 9000 Series features and applications do not work. These include IVR, IOA, DMM, SME, fcflow, and SPAN.

The following devices with hardware revision 1.5 are affected by this issue:

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

DS-X9248-48K9, 4/44-port host-optimized 8-Gbps Fibre Channel Switching Module

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

The following devices with hardware revision 1.0 are affected by this issue:

DS-X9304-18K9, 18/4-Port Multiservice Module (MSM-18/4)
For this module, the affected version is 73-14372-01A0 hardware version 1.0 (due to the new 73-number)

DS-C9222i-K9, Cisco MDS 9222i Multilayer Fabric Switch
For this switch, the affected version is 73-14373-01A0 hardware version 1.0 (due to the new 73-number)

For the DS-X9248-96K9, DS-X9248-48K9 and DS-X9224-96K9 modules, the output of the show module command indicates whether or not the device is affected.

switch# sh mod 2
Mod Ports Module-Type Model Status
--- ----- ----------------------------------- ------------------ ----------
2 24 1/2/4/8 Gbps FC Module DS-X9224-96K9 ok
 
Mod Sw Hw World-Wide-Name(s) (WWN)
--- -------------- ------ --------------------------------------------------
2 5.2(1) <B>1.0</B> 20:41:00:0d:ec:24:f4:c0 to
20:58:00:0d:ec:24:f4:c0
 

In the preceding output, the device is hardware revision 1.0 and therefore not affected.

For the DS-X9304-18K9 and the DS-C9222i-K9, the show module command might indicate hardware version 1.0 due to new part numbers; however the show sprom module command shows the affected parts.

switch# sh mod 9
Mod Ports Module-Type Model Status
--- ----- ----------------------------------- ------------------ ----------
9 22 4x1GE IPS, 18x1/2/4Gbps FC Module DS-X9304-18K9 ok
 
Mod Sw Hw World-Wide-Name(s) (WWN)
--- -------------- ------ --------------------------------------------------
9 5.2(1) 1.0 22:01:00:0d:ec:25:e9:80 to 22:12:00:0d:ec:25:e9:80
 
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
9 00-1a-e2-03-4c-5c to 00-1a-e2-03-4c-64 JAE1131SCBW
 
switch# sh sprom module 9 1 |egrep "Part|Serial"
Serial Number : JAE1131SCBW
Part Number : 73-10688-06 <-- Not 73-14372-01 so h/w ver 1.0 is OK
Part Revision : A0

 

Workaround : Upgrade to software release that has the fix for this issue.

After performing a software upgrade to a Cisco NX-OS release that contains a fix for this issue, it may be necessary to enter the shut command followed by the no shut command on the affected host ports to regain connectivity.

If you perform a nondisruptive upgrade or downgrade from a release that contains a fix to a release that does not contain the fix, you need to reload each module affected by this issue.

If you have a Cisco MDS 9222i swtich that is affected by this issue, and you perform a nondisruptive upgrade or downgrade from a release that contains a fix to a release that does not contain the fix, you need to reload the switch.

  • CSCty85364

Symptom : Devices on an NPV switch with a trunked uplink to the core NPIV switch lose connectivity to other devices after zone configuration changes.

Conditions : This issue occurs after a zone set activation and only when all of the following conditions are true:

The switch is running NX-OS Release 5.2(1), Release 5.2(2), or Release 5.2(2a)

The F-port on the NPIV switch is located on an MDS 9000 48 port 8-Gbps Advanced Fibre Channel module (DS-X9248-256K9) or on an MDS 9000 32 port 8-Gbps Advanced Fibre Channel module (DS-X9232-256K9).

The F-port carries multiple VSANs.

The zone set activation is for a VSAN that is trunked to the NPV switch.

Workaround : This issue is resolved in NX-OS Release 5.2(2d). However, upgrading to Release 5.2(2d) after you encounter this issue in an earlier 5.2(x) release does not completely resolve the issue; it only prevents the issue from reoccurring.

When you encounter this issue, the ACL TCAM programming is deleted. To recover from this situation, you must restore the communication between the devices by restoring the ACL TCAM programming.

Recovery Steps:

To restore the ACL TCAM programming, do one of the following:

Reload the DS-X9232-256K9 module or DS-X9248-256K9 module.

Enter the shut command followed by the no shut command on the host and target ports that have lost connection.

Reload the hosts that have lost the targets.


Note If you have already upgraded to NX-OS Release 5.2(2d) without completing the recovery steps in Release 5.2(1), 5.2(2), or 5.2(2a), you must complete the recovery steps because the ACL entries that were deleted are not reprogrammed during the ISSU.


Workaround Steps:

If upgrading to NX-OS Release 5.2(2d) is not an option, you can work around this issue by following these steps:

Attach multiple F-ports between the NPV and NPIV switches and allocate one VSAN to each F-port.

Move the F-port uplink to a module that is not a DS-X9248-256K module or a DS-X9232-256K module.

  • CSCua61044

Symptom : A device that is attached to a Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9248-256K9) or a Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9232-256K9) is not able to communicate with other devices.

This symptom occurs only when a port on the DS-X9248-256K9 or DS-X9232-256K9 module is zoned to more than 146 unique devices.

The following errors can be seen in the log of the DS-X9248-256K9 or DS-X9232-256K9 module:

swtich# show process acltcam internal errors
1) Event:E_DEBUG, length:84, at 359632 usecs after Tue Jun 19 23:34:44 2012
[109] Program rqst sync failed. Fwd-eng:0(IN) ifIndex: 0x1104000, status: 0x404e0005
2) Event:E_DEBUG, length:65, at 359603 usecs after Tue Jun 19 23:34:44 2012
[112] Failed: tcamwrapv2_tcam_ssram_write, 155 entries, errno: 28
 

Workaround : Reduce the number of devices that this port is zoned to to 146 devices or less, or connect the device that is attached to the Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching Module or the Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching Module to a different model module.

  • CSCtq35662

Symptom : Due to an ASIC issue, there are no credits reserved for high priority traffic on the 48-port 8-Gbps Advance Fibre Channel switching module. As a result, for a long-distance connection, port credits may go to zero, which can cause the fabric merge to fail. This issue might be seen when a fabric merge fails for a long-distance ISL.

Workaround : None.

  • CSCtq42878

Symptom : When you configure dynamic port VSAN membership (DPVM) using device alias and then remove the alias before clearing the DPVM configuration, the node NWWN configuration will not take effect for the device when you enter the activate force command. This issue might be seen when you configure a device in DPVM using device alias, and then remove the device alias mapping for that device. If you configure the same device in DPVM using NWWN and enter the activate force command, the device is not logged out and does not login again to the NWWN configured VSAN.

Workaround : To work around this issue, do one of the following:

1. Create a DPVM configuration by PWWN instead of NWWN.

2. Create an alias configuration for PWWN, delete the DPVM device alias configuration, and then delete the alias configuration.

3. Enter the shut command followed by the no shut command on the interface.

  • CSCtr04426

Symptom : On a Cisco MDS 9000 switch, the tech support CLI for some FCoE components, like VLAN_MGR and ASSOC_MGR, may appear as part of the show tech-support command output, even though the FCoE plugin is not loaded.

Workaround : None.

  • CSCtr29423

Symptom : Tape acceleration is not working with the Emulex CNA card. This issue can be seen because the Emulex CNA card uses the same OXID for all fast-path SCSI commands (read/write), which breaks tape acceleration logic for accelerating the read/write IOs.

Workaround : None.

  • CSCtr42322

Symptom : When you have IVR zone member with devices attached to the 8-port FCoE module (DS-X9708-K9) or the 48-port 8-Gbps Advanced Fibre Channel switching module (DSX9248-256K9) and you perform certain actions like module reload, VSAN suspend, device port flapping, the device does not get exported and the FC ID rewrite entries are missing. This issue might be seen when there are IVR zone member with devices attached to the 8-port FCoE module or the 48-port 8-Gbps Advanced Fibre Channel switching module and you do any of the following:

Flap the device port on the 8-port FCoE module or the 48-port 8-Gbps Advanced Fibre Channel switching

Reload the module with the device attached

Suspend or no suspend the VSAN where the device is a member

Workaround : Enter the ivr refresh command to help re-advertise this device and get the rewrite entries programmed.

  • CSCtr44412

Symptom : Configuring a static area FC ID with an area that was used for a single static FC ID configuration will fail. This issue impacts only the area where a single static entry is added and removed later, particularly if the area will still available for a single FC ID configuration.

Workaround : Instead of entering the no vsan command to remove the single static FC ID, convert the existing static single FC ID to a dynamic one, and then purge to clear the area. The area will still be available for a static area FC ID configuration.

  • CSCtr50223

Symptom : On the MDS 9513 switch, when an MSM-18/4 module boots up, it sends a request to the supervisor module to mount the modflash on the MSM-18/4 module. If there is a timeout or error in response, the following syslog message displays:

2011 Jul 14 01:18:13 sw-dc5-br2-12 %LC_MNT_MGR-SLOT3-2-LC_MNT_MGR_ERROR: SUP mount failed. MTS receive timedout

2011 Jul 14 01:19:06 sw-dc5-br2-12 %PROC_MGR-SLOT3-2-ERR_MSG: ERROR: PID 1144 (lc_mnt_mgr) exited abnormally, exit status (0xa)

2011 Jul 14 01:19:06 sw-dc5-br2-12 %MODULE-2-MOD_MINORSWFAIL: Module 3 (serial: JAE1141ZB43) reported a failure in service lc_mnt_mgr

This issue might be seen when the supervisor module is unusually busy and cannot process the mount request from the MSM-18/4 module, or the actual mount command on the supervisor takes a long time.

Workaround : Reload the MSM-18/4 module in the same slot/module where the modflash mount failed. A request will be sent to the supervisor to mount the modflash.

  • CSCtr55608

Symptom : Following the insertion of the 32-port 8-Gbps Advanced Fibre Channel switching module (DSX9232-256K9), the following syslog message is displayed:

2011 Jul 16 05:35:00 emc-9513-II %SYSMGR-STANDBY-3-UNACCEPTABLE_WAIT: Service "r

es_mgr", no response from System Manager after 10 seconds. Terminating.

This issue might be seen if you enter the no install feature-set fcoe command, then power down the 32-port 8-Gbps Advanced Fibre Channel switching module, and then insert the module again, which triggers the install feature-set fcoe command.

Workaround : None. This is a not an operationally impacting issue because it happens on the standby supervisor, and the standby supervisor can successfully come up in spite of the syslog message.

  • CSCty97827

Symptom : Host-to-target connectivity across multihop connected switches is lost. The fcping fails between devices through a port channel.

This issue is extremely rare. The conditions for it may be created after a nondisruptive upgrade to Cisco NX-OS Release 5.2(x). However service disruption might not appear immediately on the affected port channel. The next time one or more members of the port channel flap, traffic loss could occur.

To verify if you have the potential to experiene this issue, enter the commands shown in the following examples:

switch# show port-channel internal info interface port-channel 3
 
port-channel 3
channel : 3 <<< channel_id
bundle : 10 <<< normally, bundle_id = channel_id - 1
ifindex : 0x4000002
pcport mode : 67108866
admin mode : on
oper mode : on
[...]
 
switch # show system internal fcfwd pcmap
port-channel 3:
IfIndex is 0x04000002 <<< last 3 nibbles
Bundle-Index is 0x0000000a <<< last 3 nibbles are not equal
[...]
 

Regardless of the last three nibbles of the preceding indexes, this issue has been hit if the following output contains “pcm_reserv_bundle_id:Conflict,rsv a new one...”

switch# show port-channel internal event-history port-channel 1
29) Event: E_DEBUG at 487974 usecs after Thu Mar 22 19:44:26 2012
pcm_reserve_bundle_id:Conflict,rsv a new one.req_bundle=0x0,resp_bundle=0x1
 

Workaround : Flap the affected port channel by entering the shut command followed by the no shut command and confirm that the issue is no longer present. Note that bundle id is not going to change to channel_id-1, but the last 3 nibbles in IfIndex and Bundle-Index should match.

switch# show port-channel internal info interface port-channel 3
 
port-channel 3
channel : 3
bundle : 10
ifindex : 0x4000002
pcport mode : 67108866
[...]
 
switch# show system internal fcfwd pcmap
port-channel 3:
IfIndex is 0x0400000a
Bundle-Index is 0x0000000a
[...]
 
  • CSCui62316

Symptom : An event manager action is executed twice.

Condition: This issue only occurs when an event manager applet has the run script command as an action.

Workaround : None.

  • CSCtn68418

Symptom : When you try to save a configuration, you might see the following message:

switch# copy run start
[########################################] 100%
Configuration update aborted: request was aborted
%DAEMON-3-SYSTEM_MSG: ntp:can't open /mnt/pss/ntp.drift.TEMP: No space left on device - ntpd[xxxx]
%PLATFORM-2-MEMORY_ALERT: Memory Status Alert : MINOR
%PLATFORM-2-MEMORY_ALERT: Memory Status Alert : MINOR ALERT RECOVERED
 
`show system internal flash` output will display /isan as 100% full.
Mount-on 1K-blocks Used Available Use% Filesystem
/ 204800 54624 150176 27 /dev/root
/proc 0 0 0 0 proc
/isan 409600 409576 24 100 none

 

This symptom was seen because the Call Home feature had duplicate message throttling disabled and there were flapping interfaces that generated thousands of Call Home messages. These messages filled up the ISAN directory.

Workaround : To work around this issue, enable Call Home duplicate message throttling. If you find that the /isan directory is 100 percent full, open a TAC case to get assistance with deleting the files.

Related Documentation

The documentation set for NX-OS for the Cisco MDS 9000 Family includes the following documents. To find a document online, access the following web site:

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

The documentation set for Cisco Fabric Manager appears in the Cisco Fabric Manager Release Notes for Release 4.2(1) , which is available from the following website:

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

Release Notes

  • Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Releases
  • Cisco MDS 9000 Family Release Notes for MDS SAN-OS Releases
  • Cisco MDS 9000 Family Release Notes for Storage Services Interface Images
  • Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images

Regulatory Compliance and Safety Information

  • Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family

Compatibility Information

  • Cisco Data Center Interoperability Support Matrix
  • Cisco MDS 9000 NX-OS Hardware and Software Compatibility Information and Feature Lists
  • Cisco MDS NX-OS Release Compatibility Matrix for Storage Service Interface Images
  • Cisco MDS 9000 Family Switch-to-Switch Interoperability Configuration Guide
  • Cisco MDS NX-OS Release Compatibility Matrix for IBM SAN Volume Controller Software for Cisco MDS 9000
  • Cisco MDS SAN-OS Release Compatibility Matrix for VERITAS Storage Foundation for Networks Software

Hardware Installation

  • Cisco MDS 9500 Series Hardware Installation Guide
  • Cisco MDS 9500 Series Supervisor-2A Tech Note
  • Cisco MDS 9200 Series Hardware Installation Guide
  • Cisco MDS 9100 Series Hardware Installation Guide
  • Cisco MDS 9124 and Cisco MDS 9134 Multilayer Fabric Switch Quick Start Guide

Software Installation and Upgrade

  • Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide
  • Cisco MDS 9000 Family Storage Services Interface Image Install and Upgrade Guide
  • Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade Guide

Cisco NX-OS

  • Cisco MDS 9000 Family NX-OS Licensing Guide
  • Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide
  • Cisco MDS 9000 Family NX-OS System Management Configuration Guide
  • Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
  • Cisco MDS 9000 Family NX-OS Fabric Configuration Guide
  • Cisco MDS 9000 Family NX-OS Quality of Service Configuration Guide
  • Cisco MDS 9000 Family NX-OS Security Configuration Guide
  • Cisco MDS 9000 Family NX-OS IP Services Configuration Guide
  • Cisco MDS 9000 Family NX-OS Intelligent Storage Services Configuration Guide
  • Cisco MDS 9000 Family NX-OS High Availability and Redundancy Configuration Guide
  • Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide

Command-Line Interface

  • Cisco MDS 9000 Family Command Reference

Intelligent Storage Networking Services Configuration Guides

  • Cisco MDS 9000 I/O Acceleration Configuration Guide
  • Cisco MDS 9000 Family SANTap Deployment Guide
  • Cisco MDS 9000 Family Data Mobility Manager Configuration Guide
  • Cisco MDS 9000 Family Storage Media Encryption Configuration Guide
  • Cisco MDS 9000 Family Secure Erase Configuration Guide
  • Cisco MDS 9000 Family Cookbook for Cisco MDS SAN-OS

Troubleshooting and Reference

  • Cisco NX-OS System Messages Reference
  • Cisco MDS 9000 Family NX-OS Troubleshooting Guide
  • Cisco MDS 9000 Family NX-OS MIB Quick Reference
  • Cisco MDS 9000 Family NX-OS SMI-S Programming Reference

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.