 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS NX-OS Release 5.2(2)MDS 9000 Chassis and Module Support
Determining the Software Version
Determining Software Version Compatibility
Selecting the Correct Software Image for an MDS 9100 Series Switch
Selecting the Correct Software Image for an MDS 9200 Series Switch
Selecting the Correct Software Image for an MDS 9500 Series Switch
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(2)
FICON Supported Releases and Upgrade Paths
Downgrading Your Cisco MDS SAN-OS Software Image
Downgrading Guidelines Specific to NX-OS Release 5.2(2)
General Downgrading Guidelines
New Features in Cisco MDS NX-OS Release 5.2
New Software Features in Cisco MDS NX-OS Release 5.2(2)
New Software Features in Cisco MDS NX-OS Release 5.2(1)
New Hardware in Cisco MDS NX-OS Release 5.2(1)
Licensed Cisco NX-OS Software Packages
Storage Media Encryption Package
Storage Services Enabler Package
On-Demand Port Activation License
Maximum Number of Zones Supported in Interop Mode 4
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
Regulatory Compliance and Safety Information
Software Installation and Upgrade
Intelligent Storage Networking Services Configuration Guides
Obtaining Documentation and Submitting a Service Request
Cisco MDS 9000 Family Release Notes
for Cisco MDS NX-OS Release 5.2(2)
Release Date: January 23, 2012
Part Number: OL-25090-02 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
A0
January 23, 2012
Created the Cisco MDS NX-OS Release 5.2(2) release notes.
B0
January 25, 2012
Removed IVR from the "Features Not Supported on the Cisco MDS 9148 Switch" section.
Added resolved caveat CSCtx32991.
C0
January 26, 2012
Updated the "XRC Acceleration License" section.
D0
February 3, 2012
Added Resolved Caveat CSCts21095.
E0
February, 8, 2012
Updated the "New Software Features in Cisco MDS NX-OS Release 5.2(2)" section: removed FIPS certification for SME and added IOA with NPV.
F0
March 8, 2012
Updated the upgrade path in Table 11.
G0
April 2, 2012
Updated Table 11.
H0
April 30, 2012
•
Added the "Upgrading to Cisco NX-OS Release 5.2 from Release 5.0(8)" section.
•
•
•
I0
May 7, 2012
Added open caveat CSCty97827.
J0
May 24, 2012
Added open caveat CSCty85364.
K0
June 20, 2012
Added resolved caveat CSCts88422.
L0
June 25, 2012
Added open caveat CSCua61044.
M0
August 29, 2012
Added M91S2K9-5.2.2 for the MDS 9134 and MDS 9124 switches to Table 2.
N0
September 15, 2012
Added resolved caveat CSCts40563.
Updated the "Deprecated Features" section.
O0
November 8, 2012
Added the "NPE Software Images" section.
P0
February 13, 2013
Updated the "New Features in Cisco MDS NX-OS Release 5.2" section to include the features in the earlier 5.2 releases
Contents
This document includes the following:
•
•
•
•
•
•
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
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
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
Yes1
Cisco MDS 4-Gbps Fabric Switch for HP c-Class BladeSystem
Yes1
Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter
Yes1
1 This switch supports Cisco MDS NX-OS Release 5.2(2), but does not support Release 5.2(1).
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
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
No
No
No
DS-X9232-256K9
32-port 8-Gbps Advanced Fibre Channel Switching Module
Yes1
No
No
No
DS-X9248-256K9
48-port 8-Gbps Advanced Fibre Channel Switching Module
Yes1
No
No
No
DS-X9224-96K9
24-port 8-Gbps Fibre Channel Switching Module
Yes1
Yes3
No
No
DS-X9248-96K9
48-port 8-Gbps Fibre Channel Switching Module
Yes1
Yes3
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
1 Requires DS-13SLT-FAB3 or DS-13SLT-FAB2 in the MDS 9513.
2 Requires the Supervisor-2A module.
3 Requires DS-13SLT-FAB2 in the MDS 9513.
Table 5 Module Support Matrix for Cisco MDS NX-OS 4.x
DS-X9530-SF2-K9
MDS 9500 Supervisor-2 Module
Yes
N/A
N/A
DS-X9530-SF2A-K9
MDS 9500 Supervisor-2A Module
Yes1
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
Yes2
No
No
DS-X9248-96K9
48-port 8-Gbps Fibre Channel Switching Module
Yes2
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
1 In software releases earlier than Cisco NX-OS Release 4.2(7a), the Supervisor-2A module appears as unsupported hardware in Device Manager, but the Supervisor-2A module does work with Cisco NX-OS release 4.x software.
2 Requires DS-13SLT-FAB2 in the MDS 9513.
Table 6 lists the MDS hardware modules supported by Cisco MDS SAN-OS 3.x.
Table 6 Module Support Matrix for Cisco MDS SAN-OS 3.x
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
Yes1
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)2
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
1 In software releases earlier than Cisco NX-OS Release 3.3(5a), the Supervisor-2A module appears as unsupported hardware in Device Manager, but the Supervisor-2A module does work with Cisco NX-OS release 3.x software.
2 Cisco SAN-OS Release 3.2(1) and later support the 18/4-Port Multiservice Module (MSM-18/4).
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.
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/cisco/software/navigator.html?a=a&i=rpm
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 rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive resetAt a minimum, you need to disable the default device alias distribution feature using the no device-alias distribute command in global configuration mode. The show incompatibility system bootflash:system image filename command determines which additional features need to be disabled.
Note
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.
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
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.
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 moduleMod 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-standbyNPE 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:
•
•
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
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:
•
•
•
•
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(2)
Follow these guidelines when upgrading to Cisco MDS NX-OS Release 5.2(2):
•
•
•
•
•
–
–
–
–
–
–
–
–
–
–
•
Note
To migrate to IVR-NAT mode, follow these steps:
1.
–
–
2.
3.
4.
5.
The network can now run in IVR-NAT mode.
General Upgrading Guidelines
Follow these general guidelines before performing a software upgrade:
•
•
•
•
–
–
–
Note
Nondisruptive Upgrade Paths
Use Table 11 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 5.2(2). 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
Note
Caution
For supported upgrade paths in a FICON environment, see the "FICON Supported Releases and Upgrade Paths" section.
Table 11 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 5.2(2)
NX-OS:
Release 5.2(1)
Upgrade directly to NX-OS Release 5.2(2)1 .
All 5.0(x) releases
Upgrade directly to NX-OS Release 5.2(2).
All 4.2(x) releases
1.
2.
All 4.1(x) releases
1.
2.
SAN-OS:
Release 3.3(1c), 3.3(2), 3.3(3), 3.3(4x), and 3.3(5x).
1.
2.
3.
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.
2.
3.
4.
Release 2.1(2), 2.1(1b), 2.1(1a), and
2.0(x)1.
2.
3.
4.
5.
Release 1.x
1.
2.
3.
4.
5.
6.
1 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.
2 Cisco NX-OS Release 4.2(7b) supports a direct upgrade to Release 5.2(2). Release 4.2(7b) is the only 4.2(x) release that supports a direct upgade to Release 5.2(2). This direct upgrade path is available if you are using the open NX-OS Release 4.2(7b) software or the FICON-certified NX-OS Release 4.2(7b) software.
FICON Supported Releases and Upgrade Paths
Cisco MDS NX-OS Release 5.2(2) is 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.
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.
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(2)
The following guideline applies to a downgrade from Cisco MDS NX-OS Release 5.2(2):
•
If you do not install Generation 4 hardware or perform a full switch reload following the installation of NX-OS Release 5.2(2) on an MDS 9509 or MDS 9506 switch, then you can nondisruptively downgrade to NX-OS Release 5.0(x).
•
To gather information about SPAN sessions and delete them, use the following commands in this order:
–
–
–
–
–
–
–
–
–
–
General Downgrading Guidelines
Follow these general guidelines before you perform a a software downgrade:
•
•
•
•
–
–
–
–
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.
Use Table 15 to determine the nondisruptive downgrade path from Cisco NX-OS Release 5.2(2). Find the NX-OS or SAN-OS image that 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
1 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.
2 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(2), then you cannot nondisruptively download from NX-OS Release 5.2(2) to NX-OS 5.0(x).
3 A downgrade from NX-OS Release 5.2(2) to a release other than 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.
New Features in Cisco MDS NX-OS Release 5.2
This section lists the new software and hardware features in Cisco MDS NX-OS Release 5.2. It includes the following topics:
•
•
•
New Software Features in Cisco MDS NX-OS Release 5.2(2)
Cisco MDS NX-OS Release 5.2(2) is a FICON-certified version of Cisco MDS NX-OS Release 5.2(1), that also includes new features and bug fixes. In addition to these features, Cisco MDS NX-OS Release 5.2(2) supports all the new software features and new hardware that were introduced in Cisco MDS NX-OS Release 5.2(1).
Cisco MDS NX-OS Release 5.2(2) supports the following software features:
•
Cisco MDS NX-OS Release 5.2(2) is a FICON-certified release that supports these features:
–
–
–
–
•
Cisco MDS NX-OS Release 5.2(2) supports the following switches (which are not supported by Cisco MDS NX-OS Release 5.2(1)):
–
–
–
–
•
Port group monitoring and SNMP are available on the Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching module and the Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching module.
•
Cisco MDS NX-OS Release 5.2(2) supports Inter-VSAN Routing (IVR) on the Cisco MS 9148 multilayer fabric switch.
•
Cisco MDS NX-OS Release 5.2(2) supports configuring IOA with NPV.
New Software Features in Cisco MDS NX-OS Release 5.2(1)
Cisco MDS NX-OS Release 5.2(1) supports the following software features:
•
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.
•
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.
•
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 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), Cisco DCNM for SAN introduces server-based licenses that allow you to purchase a pool of Cisco DCNM for SAN licenses instead of a switch-based Fabric Manager Server (FMS) license. The installed base of existing FMS licenses are grandfathered into Cisco DCNM for SAN, which means that you do not have to purchase a new license to use Cisco DCNM for SAN if you have an existing FMS license.
There are many new features in Cisco DCNM for SAN, including:
–
–
–
–
–
Detailed information about Cisco DCNM features is available in the Cisco DCNM Release Notes, Release 5.2, and in the feature configuration guides for Cisco DCNM for SAN.
For additional information about Cisco MDS NX-OS Release 5.2(1), see the Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1).
New Hardware in Cisco MDS NX-OS Release 5.2(1)
Cisco MDS NX-OS Release 5.2(1) supports the following new Generation 4 hardware devices:
•
•
•
•
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.
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:
•
•
•
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(2)" section for instructions on how to migrate to IVR NAT mode before upgrading to Cisco NX-OS Release 5.2(2).
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
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.
Limitations and Restrictions
This section lists the limitations and restrictions. The following limitations are described:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
FCoE Module
•
•
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:
•
•
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
Step 2
Step 3
Step 4
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
Step 2
Step 3
Step 4
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:
•
•
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> commitWhen 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.comTo 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:
•
•
Trunking F ports, trunking F port channels and regular F port channels are not supported on the following MDS 9000 components:
•
•
•
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:
•
•
The following VSAN IDs are assigned in the Fibre Channel Framing and Signaling (FC-FS) interface standard:
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:
•
•
•
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:
•
•
•
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:
•
•
•
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:
•
•
•
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:
•
•
•
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:
•
•
•
•
In addition, the following features have these limits:
•
•
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:
•
•
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.
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.
.
Resolved Caveats
•
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: This issue is resolved.
•
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: This issue is resolved.
•
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: This issue is resolved.
•
Symptom: The port-group monitor feature is disabled on the Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel switching module (DS-X9248-256K9).
Workaround: This issue is resolved.
•
Symptom: The port-group monitor feature is disabled on the 32-port 8-Gbps Advanced Fibre Channel switching module (DS-X9232-256K9).
Workaround: This issue is resolved.
•
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: This issue is resolved.
•
Symptom: On a Cisco MDS 9000 switch running NX-OS Release 5.2(1), one or more process logs like the following are displayed:
2012 May 7 10:04:32 switch_SW00 %SYSMGR-SLOT5-2-SERVICE_CRASHED: Service "PMon" (PID 1200) hasn't caught signal 11 (core will be saved).2012 May 7 07:05:49 switch_SW00 %CALLHOME-2-EVENT: SW_CRASH PMon in slot 5 crashed with crash type : stateful crash2012 May 9 11:03:23 switch_SW00 %SYSMGR-SLOT4-2-SERVICE_CRASHED: Service "PMon" (PID 1200) hasn't caught signal 11 (core will be saved).2012 May 9 08:04:37 switch_SW00 %CALLHOME-2-EVENT: SW_CRASH PMon in slot 4 crashed with crash type : stateful crashA core dump for the process event is saved.
This symptom might be seen when there are no port-monitor groups configured. Only the default policy is present in the switch.
Workaround: This issue is resolved.
•
Symptom: When configuring user-defined commands for alert-groups, the "too big pss key" error message or the "value size" error message appears. In addition, the CFS Call Home commit fails.
This symptom might be seen when a switch is downgraded from Cisco NX-OS Release 5.1(x) or Release 5.2(1) to NX-OS Release 4.2(x), and there is no Call Home configuration in the startup configuration.
Workaround: This issue is resolved.
•
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: This issue is resolved.
•
Symptom: The feature manager is not responsive and goes into a loop. As a result, interfaces cannot be allocated to the storage VDC on a switch that is running the NPE image.
Workaround: This issue is resolved.
•
Symptom: A Cisco MDS 9000 switch that is configured for FICON Tape Acceleration (FTA) might not correctly clear an existing FICON exchange if the proper sequence of Fibre Channel frames that are needed to close the exchange are not seen. This situation can lead to a collision for a scheduled slot and can cause the MSM-18/4 module to reload unexpectedly.
This symptom might be seen when a host or control unit does not properly close out an exchange because of some error condition.
Workaround: This issue is resolved.
•
Symptom: Following a software upgrade on a switch with a single supervisor, active Port Monitor policies disappear. This symptom occurs only on a single-supervisor switch.
Workaround: This issue is resolved.
•
Symptom: A Cisco MDS 9000 switch that is configured for FICON Tape Acceleration (FTA) might not account correctly for an acknowledged exchange that was previously accelerated. This situation can cause the MSM-18/4 module to reload unexpectedly.
This symptom might be seen during times when the host is busy and it stacks the status from the tape drive (control unit) until later when it requests status with a "request-status" message.
Workaround: This issue is resolved.
•
Symptom: Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4), DS-X9304-18K9, might fail and have the following logs in the syslog:
2012 Jan 12 11:54:22 rmdsrdc4-sl-01 %IPS_SB_MGR-SLOT5-2-PORT_SOFTWARE_FAILURE: Port softwarefailure, module 5 port 22012 Jan 12 11:54:22 rmdsrdc4-sl-01 %IPS_SB_MGR-SLOT5-2-PORT_SOFTWARE_FAILURE: Port softwarefailure, module 5 port 32012 Jan 12 11:54:22 rmdsrdc4-sl-01 %IPS_SB_MGR-SLOT5-2-PORT_SOFTWARE_FAILURE: Port softwarefailure, module 5 port 42012 Jan 12 11:54:22 rmdsrdc4-sl-01 %MODULE-4-MOD_WARNING: Module 5 (serial: JAE124605F2)reported warning on ports 5/19-5/34 (Fibre Channel Virtual) due to Skyline ni moduleexperienced an error in device 60 (device error 0xc3c0067b)The failure also generates core dumps :
switch#show coresModule-num Instance-num Process-name PID Core-create-time---------- ------------ ------------ --- ----------------5 2 sb_part.0.0.0 12350000 Jan 12 11:545 2 sb_part.0.0.1 12350100 Jan 12 11:545 2 sb_part.0.0.2 12350200 Jan 12 11:54This symptom might be seen because after packet decompression of a corrupted packet, the source of the packet is unknown and FCIP is unable to retrieve the FCIP header, SOF, or EOF. FCIP returns SYNC LOSS, which flaps the FCIP link.
Workaround: This issue is resolved.
•
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: This issue is resolved.
•
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 log in again to the NWWN configured VSAN.
Workaround: This issue is resolved.
•
Symptom: On a Cisco MDS 9000 switch, the tech support CLI for some FCoE components, such as 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: This issue is resolved.
•
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 such as a module reload, VSAN suspend, or 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 members 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:
–
–
–
Workaround: This issue is resolved.
•
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 be available for a single FC ID configuration.
Workaround: This issue is resolved.
•
Symptom: On the 48-port 8-Gbps Advanced Fibre Channel switching module (DSX9248-256K9), port monitoring and alarms for Tx and Rx traffic can get disabled under some conditions for ports that have their speed set as "switchport speed auto."
Workaround: This issue is resolved.
•
Symptom: Lower than expected performance occurred when a Qlogic HBA was connected to a Cisco MDS 9000 switch and a port was configured in F-mode. The switch responded to a Get Port Speed Capabilities (GPSC) request with incorrect values for both Port Speed Capabilities and Port Operating Speed:
–
–
–
–
–
–
Workaround: This issue is resolved.
•
Symptom: A temperature sensor alarm might occur with sensor 1 or sensor 2 on the 32-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9232-256K9). The following error appears:
%PLATFORM-4-MOD_TEMPFAIL:The output of the show environment temperature command shows that the sensor status is failure.
--------------------------------------------------------------------Module Sensor MajorThresh MinorThres CurTemp Status(Celsius) (Celsius) (Celsius)--------------------------------------------------------------------1 Outlet1 n/a n/a n/a Failure1 Outlet2 n/a n/a n/a Failure...Workaround: This issue is resolved.
•
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 noneThis 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: This issue is resolved.
Open Caveats
•
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.
•
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.
•
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-fabricswitch#test fc-redirect config sync-with-fabric all-peersIf more than one peer is affected by this issue, then additional steps are needed. If the application flows do not come online, then the application CLI commands 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 Cisco DCNM-SAN interface.
•
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 errors1) 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: 0x404e00052) 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: 28Workaround: 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.
•
Symptom: Occasionally, a 10-G ISL between a 32-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9232-256K9) or a 48-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9248-256K9) and an older generation Cisco MDS 9000 module can take a long time to come up. The link can go into an error-disabled state.
Workaround: None.
•
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:
–
–
–
The following devices with hardware revision 1.0 are affected by this issue:
–
For this module, the affected version is 73-14372-01A0 hardware version 1.0 (due to the new 73-number)–
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 2Mod Ports Module-Type Model Status--- ----- ----------------------------------- ------------------ ----------2 24 1/2/4/8 Gbps FC Module DS-X9224-96K9 okMod Sw Hw World-Wide-Name(s) (WWN)--- -------------- ------ --------------------------------------------------2 5.2(1) <B>1.0</B> 20:41:00:0d:ec:24:f4:c0 to20:58:00:0d:ec:24:f4:c0In 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 9Mod Ports Module-Type Model Status--- ----- ----------------------------------- ------------------ ----------9 22 4x1GE IPS, 18x1/2/4Gbps FC Module DS-X9304-18K9 okMod 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:80Mod MAC-Address(es) Serial-Num--- -------------------------------------- ----------9 00-1a-e2-03-4c-5c to 00-1a-e2-03-4c-64 JAE1131SCBWswitch# sh sprom module 9 1 |egrep "Part|Serial"Serial Number : JAE1131SCBWPart Number : 73-10688-06 <-- Not 73-14372-01 so h/w ver 1.0 is OKPart Revision : A0Workaround: Upgrade to software release that has the fix for this issue.
–
–
–
•
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:
–
–
–
–
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:
–
–
–
Note
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:
–
–
•
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.
•
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.
•
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 timedout2011 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_mgrThis 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.
•
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 "res_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.
•
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 3port-channel 3channel : 3 <<< channel_idbundle : 10 <<< normally, bundle_id = channel_id - 1ifindex : 0x4000002pcport mode : 67108866admin mode : onoper mode : on[...]switch # show system internal fcfwd pcmapport-channel 3:IfIndex is 0x04000002 <<< last 3 nibblesBundle-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 129) Event: E_DEBUG at 487974 usecs after Thu Mar 22 19:44:26 2012pcm_reserve_bundle_id:Conflict,rsv a new one.req_bundle=0x0,resp_bundle=0x1Workaround: 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 3port-channel 3channel : 3bundle : 10ifindex : 0x4000002pcport mode : 67108866[...]switch# show system internal fcfwd pcmapport-channel 3:IfIndex is 0x0400000aBundle-Index is 0x0000000a[...]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
•
•
•
•
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
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2012 Cisco Systems, Inc. All rights reserved.
