 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS NX-OS Release 5.2(2d)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(2d)
FICON Supported Releases and Upgrade Paths
Downgrading Your Cisco MDS SAN-OS Software Image
Downgrading Guidelines Specific to NX-OS Release 5.2(2d)
General Downgrading Guidelines
New Features in Cisco MDS NX-OS Release 5.2
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
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(2d)
Release Date: April 25, 2012
Part Number: OL-25090-04 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
April 25, 2012
Created the release notes.
B0
May 2, 2012
•
Changed the status of caveat CSCtz09636 from Open to Resolved.
•
C0
May 7, 2012
Revised the description of caveat CSCty85364.
D0
May 24, 2012
Revised the description of caveat CSCty85364.
E0
June 25, 2012
Added open caveat CSCua61044.
F0
August 8, 2012
Removed the "Upgrading to Cisco NX-OS Release 5.2 from Release 5.0(8)" section.
G0
August 29, 2012
Added M91S2K9-5.2.2d for the MDS 9134 and MDS 9124 switches to Table 2.
H0
September 28, 2012
Updated the "Deprecated Features" section.
I0
November 8, 2012
Added the "NPE Software Images" section.
J0
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.
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) 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 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 Guidelines Specific to NX-OS Release 5.2(2d)
Follow these guidelines when upgrading to Cisco MDS NX-OS Release 5.2(2d):
•
•
•
•
•
–
–
–
–
–
–
–
–
–
–
•
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(2d). 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
Table 11 Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 5.2(2d)
NX-OS:
Release 5.2(1) and 5.2(2), and 5.2(2a)
Upgrade directly to NX-OS Release 5.2(2d).
All 5.0(x) releases
Upgrade directly to NX-OS Release 5.2(2d).
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 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 upgrade 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(2d) 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(2d)
The following guideline applies to a downgrade from Cisco MDS NX-OS Release 5.2(2d):
•
If you do not install Generation 4 hardware or perform a full switch reload following the installation of NX-OS Release 5.2(2d) 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(2d). 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(2d), then you cannot nondisruptively download from NX-OS Release 5.2(2d) to NX-OS 5.0(x).
3 A downgrade from NX-OS Release 5.2(2d) to a release other than Release 5.2(1), 5.2(2), or 5.2(2a) 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(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(2d)" section for instructions on how to migrate to IVR NAT mode before upgrading to Cisco NX-OS Release 5.2(2d).
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: A SANTap DPP may cause CRC errors in a multiple FE/BE VSAN setup with heavy I/O load.
This symptom might be seen when SANTap is running on a Cisco MDS 9000 MSM-18/4 module or Cisco MDS 9222i base module with multiple a FE/BE VSAN configuration. There is a heavy I/O load on both VSANs
Workaround: This issue is resolved.
•
Symptom: A DPP failure causes the MSM to reload. The show cores command shows the following output:
switch# show coresModule-num Instance-num Process-name PID Core-create-time---------- ------------ ------------ --- ----------------4 1 sb_part.0.0.0 12350000 Jul 11 14:454 1 ps_stap 1458 Jul 11 14:464 1 sb_part.0.0.1 12350100 Jul 11 14:464 1 sb_part.0.0.2 12350200 Jul 11 14:46Signatures in the bt#1 0x103a2360 in ssram_malloc () at../platform/storage/las/linecard/dpp/isapi/octeon/sys/mem_xse.c:47Workaround: This issue is resolved.
•
Symptom: An FCIP engine fails and all FCIP links that are attached to that engine are brought down and up.
This issue is rare and has only been seen in one FICON environment with a triangular topology and both compression and FICON Tape Acceleration are enabled.
Workaround: This issue is resolved.
•
Symptom: The FSPF route flaps every two seconds. The output of the show system internal rib sync command shows the following:
1 0000c702 update add 130 cb0000 ff0000 Sun Jan 15 17:10:14 20122 0000c703 update delete 130 cb0000 ff0000 Sun Jan 15 17:10:16 20123 0000c704 update add 130 cb0000 ff0000 Sun Jan 15 17:10:18 20124 0000c705 update delete 130 cb0000 ff0000 Sun Jan 15 17:10:19 20125 0000c706 update add 130 cb0000 ff0000 Sun Jan 15 17:10:21 20126 0000c707 update delete 130 cb0000 ff0000 Sun Jan 15 17:10:23 2012Switch1:FSPF Link State Database for VSAN 130 Domain 0xcb(203)LSR Type = 1Advertising domain ID = 0x0d(13)External LSR advertised by local switchLSR Age = 0LSR Incarnation number = 0x80003e9dLSR Checksum = 0xfb1aNumber of links = 1NbrDomainId IfIndex NbrIfIndex Link Type Cost-----------------------------------------------------------------------------0x0d(13) 0x0010cb0d 0x00100dcb 1 30001Switch2:FSPF Link State Database for VSAN 130 Domain 0xcb(203)LSR Type = 1Advertising domain ID = 0x23(35)External LSR advertised by local switchLSR Age = 0LSR Incarnation number = 0x80003f2cLSR Checksum = 0x3785Number of links = 3NbrDomainId IfIndex NbrIfIndex Link Type Cost-----------------------------------------------------------------------------0x21(33) 0x0010cb21 0x001021cb 1 300010x0f(15) 0x0010cb0f 0x00100fcb 1 300010x23(35) 0x0010cb23 0x001023cb 1 30001This symptom might be seen when you disable IVR and there is an E link down or the switch reloads at the same time. A stale FSPF route is left in the FSPF database, which causes virtual domain flaps.
Workaround: This issue is resolved.
•
Symptom: Cisco MDS Storage Media Encryption (SME) tape keys are incorrectly purged, which causes the tapes to be unreadable because the keys are no longer in the database.
This symptom might be seen following a DPP failure that is shown as a port software failure:
%IPS_SB_MGR-SLOT12-2-PORT_SOFTWARE_FAILURE: Port software failure, module 12port 1%IPS_SB_MGR-SLOT12-2-PORT_SOFTWARE_FAILURE: Port software failure, module 12port 2%IPS_SB_MGR-SLOT12-2-PORT_SOFTWARE_FAILURE: Port software failure, module 12 port 3%IPS_SB_MGR-SLOT12-2-PORT_SOFTWARE_FAILURE: Port software failure, module 12port 4Workaround: This issue is resolved.
•
Symptom: FCIP interfaces go down and stay down. The output of the show logging log command shows the following output:
switch# show logging log%IPS-SLOT2-3-RED_PACKET_DROPS: Congestion detected on GigabitEthernet port (buffer pool size: ...)%PORT-5-IF_PORT_QUIESCE_FAILED: Interfacefcip51 port quiesce failed due to failure reason: Force Abort Due to LinkFailure (0xa2)This symptom might be seen in NX-OS Release 4.2(1) through Release 5.2(2a) when IPSec is enabled and configured for FCIP.
Workaround: This issue is resolved.
•
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: This issue is resolved.
•
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 very rare circumstances in IVR NAT configurations, it is possible that devices from two or more VSANs stop communicating. The root cause is there are stale device entries in IVR vdri-fsm, which cause IVR DEP and PVM to get stuck, which prevents the name server from registering the devices.
There is a stale device entry in vdri-fsm device list:
switch4# sh ivr internal vdri-fsm vsan 130 domain 203VDRI FSM: A=1:V=130:D=0xcb(203)Native VSAN/AFID = 111/1 Cur State: LSR_OWNERNumber of Devices Advertised: 1FCID: 0xcb7f98 WWN=10:00:00:00:c9:7a:06:4c PV Pending: Add=No Del=No <---offline device, pwwn not in ivr zoneset and fcns databasePNATswitch1# sh ivr internal pnat vdom-info vsan 130IVR2 PNAT: Virtual domain info for 1:130:203 is_owner=false, owner_dom=13, local_dom=15ID: VDOM-1:130:203switch2# sh ivr internal pnat vdom-info vsan 130IVR2 PNAT: Virtual domain info for 1:130:203 is_owner=false, owner_dom=13, local_dom=35ID: VDOM-1:130:203switch3# sh ivr internal pnat vdom-info vsan 130IVR2 PNAT: Virtual domain info for 1:130:203 is_owner=false, owner_dom=13, local_dom=33ID: VDOM-1:130:203switch4# sh ivr internal pnat vdom-info vsan 130NONEThere should be outputs like the following:
is_owner=true, owner_dom=13, local_dom=13Therefore, at switch2 and switch3, the system keeps trying with switch4, but cannot get an OXID. The counter below shows the retry count.
switch2# show ivr internal dep vsan 130Internal information for DEP FSM--------------------------------vsan domain nh status sync_status req i/f130 0xcb(203) 111 NONE FCID_RW 9955 <--------Missing OXID hereNumber of DEP entries : 1switch1# show ivr internal dep vsan 130Internal information for DEP FSM--------------------------------vsan domain nh status sync_status req i/f130 0xcb(203) 111 NONE FCID_RW 10034<--------Missing OXID hereThe output should be like the following:
12 0x23(35) 211 ALL_DONE OXID|FCID_RW 0 [ fc5/1 fc9/2 fc4/2 fc1/8 fc6/1 fc5/2 fc2/8 fc6/2 fc3/8 fc1/10 fc4/8 fc2/10 fc4/10 fc3/10 ]switch2# show ivr internal pvm dom 203 vsan 130AFID:1 Vsan:130 Virtual domain:203Domains:13,15,33,35Domains added to route LSR:13,15 <----- should have full list 13,15,33,35Flags:0x3 (ROUTE_ADDED )Device ListPort WWN:10:00:00:00:xx:yy:zz:aaDomains with rewrite completed:13,15,33,35Domains with registered NS info:13,15 <----- should have full list 13,15,33,35Flags:0x3 (INITIAL_SYNC RSCN_ONLINE_SENT )Stale domain entry: on the LSR_owner switch that has the stale device in vdri, the zone database may also have an inconsistent domain while the peer switch does not.
switch# show zone internal vsan 130203(0xcb)rib has both fspf and ivr entryfspf 130 cb0000 ff0000 00 00 D P A 1 63 F normal frmivr 13:203 Domain 0xcb(203)ivr 130 cbffff ffffff 00 00 R P A 1 0 F normal frmsup-fc0This symptom might be seen under the following conditions:
–
–
–
Workaround: This issue is resolved.
•
Symptom: The copy running-config startup-config command should display an error if a VDC global configuration change is pending.
Workaround: This issue is resolved.
•
Symptom: DMM is limited to five jobs per storage port.
Workaround: This issue is resolved.
•
Symptom: The TSM application that runs through 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 READ operation, errno = 78.This error results when the switch drops a small number of SCSI data frames at the very end of a large read exchange.
This symptom might be seen when the HBA for the TSM server is connected at 2-Gbps to the MDS 9000 switch.
Workaround: This issue is resolved.
•
Symptom: New syslog messages do not get added to the log file on the supervisor and do not appear in the output of the show logging log command.
This symptom might be seen when the log has 0 bytes free, which can be seen with the dir log: command. In addition, the contents of log:startupdebug is updated about every 2 to 5 minutes or with every SNMP poll from an SNMP application like Cisco Fabric Manager or DCNM-SAN.
Workaround: This issue is resolved..
•
Symptom: FICON Tape Acceleration VTD-to-RTD recalls fail.
Workaround: This issue is resolved.
•
Symptom: Excessive bit errors on MDS generation 4 ports do not trigger the port to be shut down by the default bit error monitoring process.
This issue occurs only on ports on the 32-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9232-256K9) or on the 48-port 8-Gbps Advanced Fibre Channel Switching Module (DS-X9248-256K9).)
Workaround: This issue is resolved.
•
Symptom: A Cisco MDS 9000 switch does not issue the following SFP warning and failure messages on Generation 4 modules:
%PORT-4-IF_SFP_WARNING: Interface fcx/y%PORT-3-IF_SFP_ALARM: Interface fcx/yThis symptom might be seen only on the following modules:
–
–
Workaround: This issue is resolved.
•
Symptom: Following an upgrade to NX-OS Release 5.2.(1), four ports went into error disabled state due to a failed validation. The tranceiver was a non FC transceiver, and it failed FC compliance.
The output of the show interface command shows the following
switch# show interfacefc1/47 is down (Error Disabled - The transceiver has failed FC compliance)Port description <removed>Hardware is Fibre Channel, SFP is CWDM-1550fc2/47 is down (Error Disabled - The transceiver has failed FC compliance)Port description <removed>Hardware is Fibre Channel, SFP is CWDM-1570This symptom might be seen following an upgrade from SAN-OS Release 3.3(x) to Release NX-OS 4.2(x) and then to NX-OS 5.2(x).
After upgrade, the CWDM links using SFPs DS-CWDM-1550= or DS-CWDM-1570= were down. The links using SFPs DS-CWDM-1590= or DS-CWDM-1610= were still up.
Workaround: This issue is resolved.
•
Symptom: The traps 1.3.6.1.4.1.9.9.276 and 1.3.6.1.6.3.1.1.5.3 send an incorrect "ifAdminStatus down" state.
This symptom might be seen only in the case of a link failure on an E, TE, or TF port.
Workaround: This issue is resolved.
•
Symptom: When any previously configured LUN cannot be discoverd, the IT nexus stays offline without informing the user about the discovery failure for the LUN.
This symptom might be seen when a report LUN failure on the target side causes the LUN discovery to fail.
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: 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 failue 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: 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.
CSCtq88900
Symptom: In an SME or IOA deployment, if the number of H->T flows that are added exceeds 512, then subsequent disruptive platform events can leave an FCR unable to process interprocess (MTS) messages at a rate fast enough to support the scaled configuration. This situation can cause an MTS-buffers full condition in the FCR, which can result in unpredictable behavior. Some of the resulting errors may be unrecoverable, and may require a disruptive restart of the flows.
Workaround: Use CFS regions if a large number (greater than 512) of application flows need to be configured. CFS regions segment the FCR peer topology into manageable proportions.
•
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: The management interface on a Cisco MDS 9148 switch is 10/half after the switch reloads.
Workaround: Enter the shut command followed by the no shut command on the switch.
•
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 0x04000<B>00a</B>Bundle-Index is 0x00000<B>00a</B>[...]•
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: None.
•
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 correctible 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: 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.
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.
