 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS NX-OS Release 5.2(6)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 Guidelines Specific to NX-OS Release 5.2(6)
FICON Supported Releases and Upgrade Paths
Downgrading Your Cisco MDS SAN-OS Software Image
Downgrading Guidelines Specific to NX-OS Release 5.2(6)
General Downgrading Guidelines
New Features in Cisco MDS NX-OS Release 5.2
New Features in Cisco MDS NX-OS Release 5.2(6)
Storage Media Encryption Features
New Features in Cisco MDS NX-OS Release 5.2(2d)
New Features in Cisco MDS NX-OS Release 5.2(2a)
New Features in Cisco MDS NX-OS Release 5.2(2)
New 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
OUI Mismatch for SME Tape Targets
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(6)
Release Date: August 09, 2012
Part Number: OL-27554-01 J0
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
August 09, 2012
Created the release notes.
B0
August 29, 2012
Added M91S2K9-5.2.6 for the MDS 9134 and the MDS 9124 switches to Table 2.
C0
September 11, 2012
Updated the guidelines for smart zoning in the "Smart Zoning" section.
D0
September 20, 2012
Added an explanation of a syntax error to the "Downgrading Guidelines Specific to NX-OS Release 5.2(6)" section.
E0
September 28, 2012
Updated the"Deprecated Features" section.
F0
October 08, 2012
Added open caveat CSCuc35483.
G0
November 8, 2012
Added the "NPE Software Images" section.
H0
February 13, 2013
Updated the "New Features in Cisco MDS NX-OS Release 5.2" section to include new features from earlier 5.2 releases.
I0
March 12, 2013
Added open caveat CSCuc84790.
J0
April 5, 2013
Added open caveat CSCuf31077.
Contents
This document includes the following:
•
MDS 9000 Chassis and Module Support
•
•
•
•
•
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-OS 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) and later releases, 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 Optimized 8-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 Guidelines Specific to NX-OS Release 5.2(6)
Follow these guidelines when upgrading to Cisco MDS NX-OS Release 5.2(6):
•
•
•
•
•
•
–
–
–
–
–
–
–
–
–
–
•
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(6). 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
FICON Supported Releases and Upgrade Paths
Cisco MDS NX-OS Release 5.2(6) 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.
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(6)
The following guidelines applies to a downgrade from Cisco MDS NX-OS Release 5.2(6):
•
Syntax error while parsing 'switchport fill-pattern IDLE speed 8000'The syntax error message is harmless and can be ignored.
•
If you do not install Generation 4 hardware or perform a full switch reload following the installation of NX-OS Release 5.2(6) 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(6). 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 "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(6), then you cannot nondisruptively download from NX-OS Release 5.2(6) to NX-OS 5.0(x).
3 A downgrade from NX-OS Release 5.2(6) to a release other than Release 5.2(1), 5.2(2), 5.2(2a), or 5.2(2d) 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:
•
•
•
•
•
•
Product information about Cisco MDS 9000 NX-OS software is available at this link:
http://www.cisco.com/en/US/products/ps5989/index.html
New Features in Cisco MDS NX-OS Release 5.2(6)
Cisco MDS NX-OS Release 5.2(6) includes the new features described in the following sections:
•
Smart Zoning
Cisco smart zoning simplifies zoning to reduce the burden on administrators and enable automation of SAN provisioning without affecting SAN hardware resource consumption. When the smart zoning feature is enabled, Cisco MDS 9000 Family fabrics provision the hardware access control entries specified by the zone set more efficiently. Administrators can define zones as one-to-many, or many-to-many without incurring a penalty in switch resource consumption. As a result, zones can be defined to correspond to entities that are meaningful in their data center operations. For example, they can define a zone for an application, or for an application cluster, or for a hypervisor cluster without compromising internal resource utilization.
Follow these guidelines for smart zoning:
•
•
•
•
Note
For additional information on how to implement and configure Smart Zoning, see the Cisco MDS 9000 Fabric Configuration Guide.
Storage Media Encryption Features
Cisco NX-OS Release 5.2(6) includes the following enhancements to Cisco Storage Media Encryption (SME) Disk:
–
–
–
–
These enhancements require Cisco NX-OS Release 5.2(6) and Cisco DCNM Release 6.1(1a). For more information on these feature enhancements, see the Cisco MDS 9000 Family NX-OS Storage Media Encryption Configuration Guide.
New Features in Cisco MDS NX-OS Release 5.2(2d)
Cisco MDS NX-OS Release 5.2(2d) is a maintenance release that includes bug fixes. It does not include any new features.
New Features in Cisco MDS NX-OS Release 5.2(2a)
Cisco MDS NX-OS Release 5.2(2a) is a maintenance release that includes bug fixes and the following feature enhancement:
•
Port monitoring has been enhanced with several ASIC counters that monitor and report internal packet drops.
Additional information about this feature enhancement is available in the Cisco MDS 9000 Series Interfaces Configuration Guide.
New 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 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.
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.
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(6)" section for instructions on how to migrate to IVR NAT mode before upgrading to Cisco NX-OS Release 5.2(6).
Limitations and Restrictions
This section lists the limitations and restrictions. The following limitations are described:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
SME Quorum
You cannot change the quorum or the SME master node during a master key rekey. If a change occurs during the smart card portion of the operation, the master key rekey operation will fail and must be repeated from the beginning.
OUI Mismatch for SME Tape Targets
If Cisco DCNM does not discover all expected tape targets, check the sme.log to identify an OUI mismatch. Look for a message like the following:
2012.04.09 21:15:50 WARN [SME] skipped target 50:06:0b:00:00:b8:e4:b0 due to explicit type mismatch. Expect: 240 found: 228. If this is an error update your OUI definitionsTo correct this issue, manually add the OUI definitions to the server.properties file. The format is as follows:
# 0xhhhhhh vendor_name devicetypes h(host)|d(disk)|t(tape)|s(switch)|g(gateway)|m(cisco mds)# for example: newOUIs=0x00E069 JNI h|d; 0x000ded Cisco m;\# 0x006069 Brocade s;newOUIs=FCIP Performance Drop
FCIP performance can drop in a topology where the round-trip time (RTT) delay is configured at 80 ms, IPSec is enabled, and write acceleration (WA) is not used.
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 an RSA version 1 key for SSH, then you will not be able to log in through SSH following the upgrade.
If you have an 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 port channels 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 packet 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 FLOGI process might fail repeatedly, which leads to a system reload if a module reboots during an ISSU or DSSU. This issue can occur only if a module reloads (for any reason) during ISSU or DSSU. This is not a normal event and this issue is not likely to occur.
Workaround: This issue is resolved.
•
Symptom: An IOA tape read acceleration problem occurs when sending Accept (ACC) to the Read Exchange Concise (REC) Extended Link Service with data_xfer_count = 0, and when a few data packets have been sent. Once the REC ACC is sent, the host sends a Sequence Retransmission Request (SRR) FCP FC-4 Link Service Request to claim the rest of the data. The target sends a REJECT, which causes the host to end the exchange. This symptom might be seen when IOA retransmissions occur from target to host.
Workaround: This issue is resolved.
•
Symptom: A tape target is unresponsive and a permanent error is sent to the host. The host side and target side IOA traces show multiple Read Exchange Concise and Sequence Retransmission Request events followed by ABTS for the read exchanges.
Workaround: This issue is resolved.
•
Symptom: A process fails in /isan/bin/xbm when the CPU is mostly occupied by two or three processes and snmpd is one of them.
This symptom occurs on Cisco MDS 9000 switches running Cisco NX-OS Release 5.0(4d). When there is frequent interaction between snmpd and other processes such as zone, the priority of these processes is promoted. As the result, these two processes and a few others occupy most of the CPU, and other processes do not get to run which causes them to fail, typically due to a heartbeat failure.
Workaround: This issue is resolved.
•
Symptom: After upgrading Fabric Manager Server and the Cisco Key Management Centers (KMC) from Cisco NX-OS Release 4.2(3) to Release 5.0(4d) to Release 5.2(1), the old tape key replication relationships are lost. However, you are able to create new tape key replication relationships for the newly created tape-backup groups.
This symptom occurs following an upgrade of the KMC to Cisco NX-OS Release 5.2(1).
Workaround: This issue is resolved.
•
Symptom: After releasing the local zone lock through Cisco Fabric Manager, the fabric lock still exists and the IVR commit does not happen.
Workaround: This issue is resolved.
•
Symptom: During an ISSU from Cisco NX-OS Release 4.2(3) to Release 5.0(7), the standby supervisor failed to boot to the new version, but the boot variables were modified to the new release, which is not the expected behavior.
Workaround: This issue is resolved.
•
Symptom: An EPLD upgrade failed because an incorrect fabric controller was detected.
Workaround: This issue is resolved.
•
Symptom: The ethport process failed on the active supervisor and then on the standby supervisor after a switchover that was triggered by hap-reset, which caused a switch reload.
switch# show system reset-reason----- reset reason for Supervisor-module 5 (from Supervisor in slot 5) ---1) At 645162 usecs after Wed May 2 11:56:56 2012Reason: Reset triggered due to HA policy of ResetService: ethport hap resetVersion: 5.2(2a)----- reset reason for Supervisor-module 6 (from Supervisor in slot 6) ---1) At 685033 usecs after Wed May 2 12:01:03 2012Reason: Reset triggered due to HA policy of ResetService: ethport hap resetVersion: 5.2(2a)Four core files were created, two for each supervisor module.
switch# show coresModule Instance Process-name PID Date(Year-Month-Day Time)------ -------- --------------- -------- -------------------------5 1 ethport 3445 2012-05-02 12:02:365 1 ethport 11344 2012-05-02 12:02:386 1 ethport 30298 2012-05-02 12:06:476 1 ethport 3491 2012-05-02 12:06:49This symptom might occur when a PortChannel is created over Gigabit Ethernet ports.
user=admin:cmd=configure terminal ; interface port-channel 1 ; channel mode active (SUCCESS)user=admin:cmd=configure terminal ; interface port-channel 1 ; shutdown (SUCCESS)user=admin:cmd=Interface port-channel 1 state updated to upuser=IPS config:cmd=Write conditional config:: ips: 1, iscsi: 0, fcip: 1 iscsi-intf-vsan: 0, ips_lc: 1Workaround: This issue is resolved.
•
Symptom: The following exceptions are logged in the module exception log of Cisco MDS 9000 Generation 4 modules:
1. TBIRD_FWD_IAF_ACL_PIORD_LSB_ECC_ERR2. TBIRD_FWD_IAF_ACL_BANK0_LSB_ECC_ERR3. TBIRD_FWD_IAF_ACL_BANK1_LSB_ECC_ERR4. TBIRD_FWD_IAF_FIB_PIORD_LSB_ECC_ERR5. TBIRD_FWD_IAF_FIB_BANK0_LSB_ECC_ERR6. TBIRD_FWD_IAF_FIB_BANK1_LSB_ECC_ERR7. TBIRD_FWD_ETI_SPANS_PIORD_LSB_ECC_ERR8. TBIRD_FWD_ETI_SPANS_BANK0_LSB_ECC_ERR9. TBIRD_FWD_ETI_SPANS_BANK1_LSB_ECC_ERRThe count of relevant errors per module (from the last time counters were cleared) can be seen by the following command:
switch# show hardware internal errors all | inc "LSB_ECC| in module"If TACACS accounting is enabled, the following messages will be in the syslog:
%TACACS-3-TACACS_ERROR_MESSAGE: All servers failed to respond%AAA-1-AAA_SESSION_LIMIT_REJECT: aaa request rejected as maximum aaa sessions are in progressThis symptom occurs only on the Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9232-256K9) and the Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9248-256K9).
The main cause of the issue is the exceptions generated on the module. These exceptions do not impact operations. However, the unthrottled notification exceptions are not desirable, and might cause switch resources to be overwhelmed. These notifications should be disabled until it is possible to upgrade to software where this issue is fixed.
Workaround: This issue is resolved.
•
Symptom: An HDS AMS Truecopy path failure occurs in a topology with an HDS AMS initiator and target, and a Cisco MDS 9509 switch with a MSM-18/4 module and a Cisco MDS 9222i switch. IVR NAT is enabled with both devices in an IVR zone. The path between the initiator and target is active after the IVR zone set is enabled, but after the FCIP link goes down and then up, the Truecopy path stays offline unless a manual recovery is initiated. This problem does not occur without IVR.
Workaround: This issue is resolved.
•
Symptom: On an Cisco MDS 9513 switch, SCSI traffic sent from a LUN to a device configured for IVR or FC Redirect gets dropped.
This symptom occurs when the LUN numbers end with 0x2x, 0x22, or 0x81.
Workaround: This issue is resolved.
•
Symptom: A FICON tape acceleration (FTA) control message that was received out of sequence caused the MSM-18/4 module to fail. This symptom occurred when FTA was enabled for read acceleration.
Workaround: This issue is resolved.
•
Symptom: Following an IVR zone set activation, a Cisco MDS 9148 switch loses connectivity within a VSAN.
Workaround: This issue is resolved.
•
Symptom: When FTA is disabled, a module reloads due to a null device entry.
Workaround: This issue is resolved.
•
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:
switch# 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: This issue is resolved.
•
Symptom: An RSCN is not sent to zone members in the IVR remote VSAN when the physical interface goes down.
This symptom occurs when the devices are in an IVR zone. An RSCN is sent to local IVR VSAN zone members, but not to remote IVR VSAN zone members.
Workaround: This issue is resolved.
•
Symptom: An ISSU might fail with the following message:
%MODULE-2-LCM_UPGRADE_READY_GENERAL_FAIL:Upgrade ready message fails SAP Zone serverThis symptom occurs when suspended VSANs trigger it.
Workaround: This issue is resolved.
•
Symptom: A replaced smart card configuration is not persistent following a switch reload.
Workaround: This issue is resolved.
•
Symptom: A Cisco MDS 9124 switch incorrectly indicates that the TCAM is full when it is not. The symptom occurs when a Cisco MDS 9124 switch is in NPV mode and an NPIV switch is connected to it with PortChannels. If the NPIV mode switch reloads, the TCAM member table counter is not decreased.
Workaround: This issue is resolved.
•
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, power down the 32-port 8-Gbps Advanced Fibre Channel switching module, and then insert the module again, which causes the install feature-set fcoe command to execute.
Workaround: This issue is resolved.
•
Symptom: The Cisco MDS IOA feature fails when IOA flows frequently flap due to logout and to tape sessions that are cleaned up on the host and target IOA nodes.
Workaround: This issue is resolved.
•
Symptom: An SME cluster with a single node goes offline after an upgrade from Cisco SAN-OS Release 3.3(1c) to Cisco NX-OS Release 4.2(7d).
Workaround: This issue is resolved.
•
Symptom: SANTap PLOGI ELS_Capture ACL is not programmed for SANTap VT/VI
This symptom might occur when the AVT zone is large (over 50 members). The PLOGI LS_ACC can be dropped and not sent back to the EMC Recover Point Appliance (RPA).
By programming in this new ACL entry, the LS_ACC will be captured by the supervisor module and delayed until the ACL programming is complete.
The following drop counters will increment when this occurs:
switch# show hardware internal fwd-ingress 0 error-statistics* -----------------------------------------------------------------------------* Global Error Statistics for device Tuscany-fwd* dev inst: 0, port(s): 1-22*ADDRESS STAT COUNT__________ ________ __________________0x00002d5c AD_ADJ_PKT_DROP_FCNT 0xxxMapping for adj mem stats:...0x40 - acl_default_no_match_drop...------- ----- ------Address Bytes Frames------- ----- ------...0040 00000000000016ac 0000000000000029Workaround: This issue is resolved.
•
Symptom: An AAA authentication error occurs.
switch(config)# aaa group server ldap ldap-groupswitch(config)# aaa authentication login default group ldap-grouptoo big pss key or value size could not update aaa configurationswitch(config)#This symptom might be seen on a switch that is running Cisco NX-OS Release 5.x software or a later release, and a downgrade from Cisco NX-OS Release 5.1(x) or a later release occurs.
Workaround: This issue is resolved.
•
Symptom: The startup configuration does not sync up with the running configuration even after executing a copy running-config startup-config command. Additional interfaces appear in the startup configuration, even when the module does not have those ports present. For instance, for a module with 12 ports, such as the Cisco MDS 9000 12-port 4-Gbps Fibre Channel Switching Module (DS-X9112), the startup configuration shows that interfaces 13 through 24 also are present.
Workaround: This issue is resolved.
•
Symptom: An interface fails with "Hardware Failure" and the exception log contains the error "RXF NP fifo overflow."
switch# show int fc12/7fc12/7 is down (Hardware failure)switch# show logging log%MODULE-2-MOD_SOMEPORTS_FAILED: Module x (serial: JAFxxxxxxx) reported failureon ports x/8-x/8 (Fibre Channel) due to FC MAC Experienced an error in device118 (error 0xc760020a)switch# show module internal exceptionlog********* Exception info for module x ********exception information --- exception instance 1 ----Module Slot Number: xDevice Id : 118Device Name : AakashDevice Errorcode : 0xc760020aDevice ID : 118 (0x76)Device Instance : 00 (0x00)Dev Type (HW/SW) : 02 (0x02)ErrNum (devInfo) : 10 (0x0a)System Errorcode : 0x40420010 FC MAC Experienced an errorError Type : Minor errorPhyPortLayer : Fibre ChannelPort(s) Affected : 8Error Description : RXF NP fifo overflow, ref port 7DSAP : 0 (0x0)UUID : 543 (0x21f)This symptom occurs only on the following Generation 3 modules:
–
–
–
Workaround: This issue is resolved.
•
Symptom: The following truncated syslog message is printed when a 48-port 8-Gbps Advanced Fibre Channel module (DS-X9248-256K9) is inserted into a Cisco MDS 9000 switch chassis with a fabric 2 module.
2011 Oct 31 10:28:22 MDS-FABRIC-B %XBAR-2-INCOMPATIBLE_CONFIG: Linecard in slot 3 is not supported with current switch fabric mode. Please upgrade to either DS-13SLT-FAB2 or DS-13SLT-FAB3 switch fabricmodules in the case of 9513 chassis to supportthe linecard and reload the switch. In the case of9506/9509 please reWorkaround: This issue is resolved.
•
Symptom: When the configuration was copied using SNMP, the file transfer indicated it was complete but it was not. Subsequent attempts using SNMP to execute the copy running-config startup config command or to transfer the startup configuration using TFTP failed with the following message:
"snmpd: another copy is in progress: Only one operation allowed at any one instance."This symptom occurs when you attempt to save the running-configuration to the startup-configuration through SNMP using Device Manager or Cisco Fabric Manager.
Workaround: This issue is resolved.
•
Symptom: When a device alias is renamed and committed, the renamed entry appears in the device alias database and propagates to the active zone set, however, it does not propagate to the full zone set. If the running configuration is copied to the startup configuration, the old name still exists in the startup configuration.
This symptom occurs regardless of basic or enhanced zoning, IVR, or non-IVR fabrics.
Workaround: This issue is resolved.
•
Symptom: The TSM application that runs through the Storage Media Encryption (SME) feature on a Cisco MDS 9000 switch reports the following error message:
ANR8311E An I/O error occurred while accessing drive DRIVEx (/dev/rmtx) for READoperation, errno = 78This error is a result of the Cisco MDS 9000 switch dropping a small number of SCSI data frames at the very end of a large read exchange. This symptom might be seen when the TSM server HBA is connected to the Cisco MDS 9000 switch at a speed of 2 Gbps.
Workaround: This issue is resolved.
•
Symptom: Device Manager does not show the power supply information correctly. Even if you make a change in redundant or combined mode, Device Manager shows the lowest value under capacity when you have two different power supplies.
Workaround: This issue is resolved.
•
Symptom: When a switch is upgraded from a lower software version to a higher version and PMON policies are configured, if there are counter differences in these software versions, the PMON policy cannot be removed from the higher version.
This symptom occurs only when PMON policies are configured before the upgrade and extra counters are present in the upgraded version.
Workaround: This issue is resolved.
•
Symptom: Entering the clear ntp session command causes NTP to fail.
This symptom occurs when there is a NTP CFS lock held by the switch.
Workaround: This issue is resolved.
•
Symptom: The standby supervisor remains in a powered-up state and not in HA standby even though a process is failing.
Workaround: This issue is resolved.
•
Symptom: Cisco MDS Storage Media Encryption (SME) will not function with an RSA key length of less than 1024 in Cisco NX-OS Release 5.2(1) and later releases.
Workaround: This issue is resolved.
•
Symptom: IVR per VSAN state information is missing local VSAN information.
Workaround: This issue is resolved.
•
Symptom: The fabric name that is configured in Cisco MDS SME does not match the fabric name in Cisco DCNM-SAN and there is no meaningful message about the mismatch.
Workaround: This issue is resolved.
•
Symptom: The management interface on a Cisco MDS 9148 switch is 10/half after the switch reloads.
Workaround: This issue is resolved.
•
Symptom: When a local node leaves a Cisco IOA cluster, a message needs to be displayed that provides the reason the node left.
Workaround: This issue is resolved.
•
Symptom: Host-to-target connectivity across multihop-connected switches is lost. The fc ping fails between devices through a PortChannel.
This issue is extremely rare. The conditions for this issue 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 PortChannel. The next time one or more members of the PortChannel flap, traffic loss could occur.
To verify if you have the potential to experience 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: This issue is resolved.
•
Symptom: Cisco IOA issues the following messages:
%LIBBASE_SVC-5-IT_NEXUS_FAILURE: IT-NEXUS (iwwn, twwn). IT-NEXUS on ioa4/1vi-vt (viwwn, vtwwn) bind failure. Reason: : 0x46%LIBBASE_SVC-5-IT_NEXUS_FAILURE: IT-NEXUS (iwwn, twwn). IT-NEXUS on ioa2/1vi-vt (viwwn, vtwwn) bind failure. Reason: : 0x26The reason text is not provided and the reason codes of 0x46 and 0x26 are not defined.
Workaround: This issue is resolved.
•
Symptom: The size of the bootflash on a Cisco MDS 9222i switch might be smaller than expected. The bootflash should be around 650 MB, but on some Cisco MDS 9222i switches the bootflash size is 325 MB.
Workaround: This issue is resolved.
•
Symptom: An ISSU upgrade fails with a core file for an FC Redirect process.
switch# show coresModule-num Instance-num Process-name PID Core-create-time---------- ------------ ------------ --- ----------------8 1 fc-redirect 3097 Apr 4 12:59This symptom occurred on a Cisco MDS 9513 switch with Cisco NX-OS Release 4.2(7a) that was upgrading to Cisco NX-OS Release 5.0(4d).
Workaround: This issue is resolved.
•
Symptom: Following an upgrade from Cisco NX-OS Release 3.3(x) to Release 4.2(x), IVR over FCIP caused an ENTERPRISE_PKG license to be checked out. Before the upgrade, IVR was using the SAN_EXTN_OVER_IP_IPS2 license. The ENTERPRISE_PKG license should not have been checked out as the SAN_EXTN_OVER_IP_IPS2 was still present.
Workaround: This issue is resolved.
•
Symptom: Some onboard logging statistics are not updated as frequently as required. These statistics are used only for debugging limited types of problems.
This symptom might be seen only on the 32-port 8-Gbps Advanced Fibre Channel module (DS-X9232-256K9) and the 48-port 8-Gbps Advanced Fibre Channel module (DS-X9248-256K9).
Workaround: This issue is resolved.
•
Symptom: A username cannot be deleted.
Workaround: This issue is resolved.
•
Symptom: A Fibre Channel interface is down. It is error-disabled because the port reinitialization limit has been reached.
This symptom occurs when the module rootfs (/dev/root) is full, and the module FIB VmSize is larger than 15000 KB.
First trigger is the module rootfs (/dev/root) is full.
switch# attach module xmodule-4# show system internal flashFilesystem 1K-blocks Used Available Use% Mounted onrootfs 95195 95195 0 100% //dev/root 95195 95195 0 100% /switch# attach module xmodule-4# show process memusage |include "VmSize|fib"Name |PID | VmSize | VmData | VmStk | VmExe | VmLib |fib | 1647 | 10192 k| 2548 k| 84 k| 288 k| 4808 k|The number in the VmSize column should not exceed 15000 KB.
Workaround: This issue is resolved.
•
Symptom: A Cisco Fabric Services (CFS) process fails when a CFS application deregisters itself and a timeout occurs. The following messages are displayed:
%FSCM-2-FABRIC_START_CFG_MGR_PROGRAM_EXIT: Fabric Start Cfg Mgr daemon exiting: could not registerwith CFS%SYSMGR-3-SERVICE_TERMINATED: Service "fscm" (PID 3704) has finished with error codeSYSMGR_EXITCODE_SYSERR (1).%SYSMGR-STANDBY-5-CFGWRITE_STARTED: Configuration copy started (PID 2589).%RADIUS-3-RADIUS_ERROR_MESSAGE: could not register with cfs: 0x80b3003e%SYSMGR-2-SERVICE_CRASHED: Service "cfs" (PID 2883) hasn't caught signal 11 (core will be saved).Workaround: This issue is resolved.
•
Symptom: An F port interface goes down and will not come back up. The following error message is displayed:
Link failure Link Reset failed nonempty recv queueThis issue only affects interfaces on the Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9248-256K9) or the Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9232-256K9). It is triggered by shutting the last member (or the interface itself) of a downstream next-hop PortChannel while high rates of traffic are flowing from the edge port into the PortChannel.
This issue cannot be cleared by shutting and not shutting the affected interface. It can be identified for an affected interface fc x/y with the following command:
switch# attach module {x}module-x# show hardware internal credit-info port {y}Buffers are all used. (Configued-0x20, used = 0x26)module-x# exitThe number of buffers used is greater than those configured.
Workaround: This issue is resolved.
•
Symptom: The FSCM process exits without deregistering from Cisco Fabric Services (CFS). As a result, the following CFS events occur:
Wed May 2 15:44:41 2012 :MTS send failed, retval -1, errno 32 [Broken pipe]Dest sap 139, opcode 8465This symptom occurs after the FSCM process exits or fails or both four times and is not restarted due to a sysmgr policy.
Workaround: This issue is resolved.
•
Symptom: Hosts that are zoned by a device alias cannot see storage.
This symptom occurs in an active zone set, and there is no FCID next to the device alias; however, the FCID is in the FCNS database.
switch# show zoneset activezone name myserver_hba0-mystorage_8D0 vsan 10* fcid 0x363d00 [device-alias myserver_hba0]device-alias mystorage_8D0switch# show fcns databaseVSAN 10:--------------------------------------------------------------------------FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE--------------------------------------------------------------------------0x110000 N 50:00:11:22:33:44:55:66 scsi-fcp:target[mystorage_8D0]There are duplicate pPWWNs.
switch# show zone internal ddas-tableDevice Alias Database State: 1Device Alias Mode: enhanced------------------------------------------------------------------------------Device Alias Name PWWN------------------------------------------------------------------------------mystorage_8DA 50:00:11:22:33:44:55:66mystorage_8D0 50:00:11:22:33:44:55:66Workaround: This issue is resolved.
•
Symptom: The Cisco MDS 9513 multilayer switch that is running Cisco NX-OS Release 5.0(1a) includes a version of OpenSSL that is affected by the vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs:
CVE-2012-0814
This bug was opened to address the potential impact on this product.
This symptom occurs on a device with a default configuration.
Additional details about the vulnerabilities listed above can be found at http://cve.mitre.org/cve/cve.html
Workaround: This issue is resolved.
•
Symptom: The show tech-support command does not work properly for users with a role other than network-admin. Sections of the command that require access to modules will time out and be missing from the output.
The symptom occurs because non-network-admin users are not being permitted to attach to a module. The following error messages are displayed when such a user enters this command:
switch# attach module 1This command can only be run by the network adminIf a role is created and permit attach is added to the role, the command will fail with the following error message:
switch# attach module 1% Permission denied for the roleThis issue affects any user with a role other than network-admin.
Workaround: This issue is resolved.
•
Symptom: The IKE service might fail and produce a core dump on a Cisco MDS 9509 switch that is configured for IPsec with IKE. The failure occurs during a IKE rekey operation.
This symptom occurs on a Cisco MDS 9509 that is running Cisco NX-OS Release 4.2(1b).
Workaround: This issue is resolved.
•
Symptom: When hosts are added to the FE VSAN, the MSM-18/4 module (DS-X9304-18K9) that is running SANTap might experience a ps_stap core.
This symptom occurs when hidden LUNs are installed and the number of LUNs per host exceeds the maximum limit. The following messages might be seen before the core:
2012 Jul 12 10:31:56 MDS03 %SANTAP-SLOT3-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning:ApproachingMAX_LUNS_PER_HOST(256) limit for Host 1:2:3:4:5:6:7:8, DVT1:2:3:4:5:6:7:8. Existing num luns 2302012 Jul 12 10:31:56 MDS03 %SANTAP-SLOT3-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning:ApproachingMAX_LUNS_PER_HOST(256) limit for Host 1:2:3:4:5:6:7:8, DVT1:2:3:4:5:6:7:8. Existing num luns 2302012 Jul 12 10:31:57 MDS03 %SANTAP-SLOT3-4-ST_NEAR_MAX_LUNS_PER_HOST: Warning:Approaching2012 Jul 12 10:31:59 MDS03 %SANTAP-SLOT3-2-ST_MAX_LUNS_PER_HOST_REACHED:MAX_LUNS_PER_HOST(256) limit reached for Host 1:2:3:4:5:6:7:8, DVT1:2:3:4:5:6:7:8. Cannot Install Lun 0xyyyy2012 Jul 12 10:32:00 MDS03 %PROC_MGR-SLOT3-2-ERR_MSG: ERROR: PID xxxx (ps_stap)killedwith signal (11)Workaround: This issue is resolved.
•
Symptom: Following an ISSU or ISSD, DMM is not configured on a a module where IPFC and DMM were previously configured.
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: 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: 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: After replacing a smart card that reached the maximum number of shares (16), the new smart card gets stuck in the initializing state.
Workaround: None.
•
Symptom: Periodic FCIP port flaps might occur when Tape Acceleration and IP compression are enabled and the MTU is configured at 9000. This situation might lead to a failure of an IPS core.
This symptom might be seen when the following configuration is applied to an FCIP tunnel:
–
–
–
–
Workaround:
This issue does not occur if TA is not configured and other parameters remain the same.
This issue does not occur if the MTU size of up to 2500 is configured and other parameters remain the same.
•
Symptom: On a Windows XP system, master key rekey cannot detect a smart card and displays the following message:
Exception reading smartcard:CKR_OPERATION_NOT_INITIALIZEDWorkaround: None.
•
Symptom: On a Windows 7 32-bit system, there is an issue with the Java version detect plugin. In addition, the pkcs11wrapper.dll file is not copied over correctly.
Workaround: None.
•
Symptom: An ISSU from Cisco MDS Release 4.2(7dE5) to Release 5.2(6) fails when the number of IOA tape acceleration flows exceeds 511.
This issue might be seen on an Cisco MDS 9000 Series switch with the MDS 9000 18/4-port Multiservice (MSM-18/4) module.
Workaround: None.
•
Symptom: Activation of a zone set in a VSAN in interop mode 1, fails with the following error messages:
%ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN_DOM: %$VSAN <vsan>%$ Activation failed: reason Invalid zonset format domain <dom>%ZONE-2-ZS_CHANGE_SFC_FAILED: %$VSAN <vsan>%$ SFC failed : domain <dom> returnsINVALID_ZSET_FORMATThe failure occurs only if the following conditions exist:
–
–
–
–
Workaround:
There are two methods for working around this issue:
–
–
•
Symptom: Following an upgrade to NX-OS Release 5.2(6) or Release 5.2(6a), FCIP interfaces are down and the following message appears:
fcip1 is down (Tunnel port src interface unbound)The licenses for all SAN_EXTN_OVER_IP packages in the grace period might be unnecessarily checked out.The inter-VSAN routing (IVR) process is using those licenses.
switch# show ivrLicense status-----------------IVR is running based on the following license(s)SAN_EXTN_OVER_IPSAN_EXTN_OVER_IP_IPS2SAN_EXTN_OVER_IP_IPS4SAN_EXTN_OVER_IP_9216iSAN_EXTN_OVER_IP_18_4SAN_EXTN_OVER_IP_SSN16Conditions: This symptom might be seen when IVR is running over FCIP.
Workaround: To work aorund this issue, follow these steps:
1.
switch# show license usage SAN_EXTN_OVER_IP_18_4Application----------------------------------------------------------------------------IVR_FCIP----------------------------------------------------------------------------2.
3.
switch# no feature fcipswitch# no feature IVR4.
switch# copy licenses bootflash:lic-backup.tarswitch# copy bootflash:lic-backup.tar tftp://xxx.xxx.xxx.xxx5.
6.
7.
8.
•
Symptom: Ports on the 24-port, 48-port, or 4/44-port 8-Gbps Fibre Channel switching modules go into a suspended state and packets cannot egress or ingress on the port. This issue can occur on Cisco MDS 9500 Series Directors and Cisco MDS 92221 switches when any of the following modules are installed:
–
–
–
Conditions: This issue occurs after a nondisruptive upgrade to Cisco NX-OS Release 5.2(6x) or Release 5.2(8), and a link flap occurs on the ports.
Workaround: To work around this issue, do one of the following:
1.
2.
3.
Further Problem Description: The main indications of a port exhibiting this issue are the following:
–
–
•
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: 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: The label for a smart card is not detected correctly.
Workaround: None.
•
Symptom: After creating an SME cluster, adding disks to a disk group, changing some disk states, and starting master key rekey, the key creation date is invalid.
Workaround: None.
•
Symptom: After creating an SME cluster in advanced mode, adding 500 disks to the disk group, exporting the keys, and importing the keys again, there is no scroll option in the import manage key window.
Workaround: None.
•
Symptom: On a Cisco MDS 9000 switch with the MSM-18/4 module that is running FC Redirect, host ports and destination ports become error-disabled after flapping. The logs show the following errors:
switch(config-if)# sh int fc1/17 br-------------------------------------------------------------------------------Interface Vsan Admin Admin Status SFP Oper Oper PortMode Trunk Mode Speed ChannelMode (Gbps)-------------------------------------------------------------------------------fc1/17 1 FL -- errDisabled swl -- --switch(config-if)#switch(config)# ivr aam pre-deregister-checkswitch(config)# show ivr aam pre-deregister-checkAAM pre-deregister check status--------------------------FAILUREThere are merged entries or AAM has not been enabled with the following switches:switch swwn 20:00:00:0d:ec:3e:f4:c0Workaround : Disable IVR and AAM support on FCR and flap the ports:
switch (config)# no fc-redirect ivr-support enableswitch (config)# no ivr aam registerAAM is currently disabled. No change will be made.switch (config)#switch (config)# ivr commitdistribution not enabledswitch (config)# int fc1/17switch (config-if)# shutswitch (config-if)# no shutswitch (config-if)# sh int fc1/17 br-------------------------------------------------------------------------------Interface Vsan Admin Admin Status SFP Oper Oper PortMode Trunk Mode Speed ChannelMode (Gbps)-------------------------------------------------------------------------------fc1/17 1 FL -- up swl FL 2 --switch (config-if)#•
In Generation 4 modules, the following errors might be observed. They are not a cause for concern to the normal operation of the hardware. These errors are logged in the onboard persistent log and can be viewed by entering the show logging onboard exception-log command after attaching to the module.
TBIRD_FWD_EBM_0_SER_PARITY_XXX : InformationalTBIRD_FWD_EBM_0_PACK0_EPR_DROP : InformationalTBIRD_FWD_EBM_1_PACK3_MISS_SOF : InformationalTBIRD_FWD_EBM_1_PACK0_MISS_EOP : InformationalTBIRD_FWD_EBM_1_PACK0_SF_TOO_SMALL : InformationalThese errors are reported when there are internal correctable conditions encountered during operation, and the corrective action is taken. They do not necessarily indicated a problem with the switch or module.
The following error can occur in cases of corrupted frames in the ingress path (due to a bad cable or SFP). It does not necessarily indicated a problem with the switch hardware.
THB_IPA_IPA0_INTR_FLD_ERR_FROM_MEM : WarningWorkaround: None.
•
Symptom: After the primary KMC fails over to the secondary, KMC performance suffers. The system attempts to reacquire connectivity to the primary KMC for each operation, and the system waits for that attempt to time out before using the secondary KMC. Waiting for the timeout creates a significant delay for failed over operations, particularly when scaled.
This symptom occurs when the primary KMC fails (because of loss of connectivity).
Workaround: Restore connectivity to the primary KMC.
•
Symptom: When a trunk link fails, the 1.3.6.1.4.1.9.9.289.1.3 trap has an incorrect link failure reason of "gracefully down."
This symptom might be seen only when a link failure occurs on a E, TE, or TF port.
Workaround: Ignore the link down reason because the link down trap is valid.
•
Symptom: A "VSAN down" trap is sent for VSAN 4094 when a trunk port goes down because the VSAN is not configured on the trunk.
This symptom might be seen only when a link down occurs on a E, TE, or TF port.
Workaround: Ignore the trap.
•
Symptom: Communication errors that occur during master key rekey are not handled gracefully.
Workaround: None.
•
Symptom: When creating a cluster, key management servers are not listed in the drop-down list.
Workaround: Manually enter the IP address of the server.
•
Symptom: For a failed master key rekey, the master key shares were generated and updated in the CKMC.
Workaround: None.
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.
