 Feedback
|
Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS NX-OS Release 4.2(9)MDS 9000 Chassis and Module Support in Cisco MDS NX-OS 4.x
Migrating from Supervisor-1 Modules to Supervisor-2 Modules
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
FICON Supported Releases and Upgrade Paths
Upgrading an MDS 9222i Switch with SANTap or Invista is Provisioned on the SSM
Enabling Telnet Required After an Upgrade
Reconfiguring SSM Ports Before Upgrading to NX-OS Release 4.2(9)
Upgrading the SSI Image on Your SSM
Upgrading a Cisco MDS 9124 or Cisco MDS 9134 Switch
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Resetting SNMP Notifications Following an Upgrade
Converting Automatically Created PortChannels Before an Upgrade
Downgrading Your Cisco MDS SAN-OS Software Image
General Downgrading Guidelines
Downgrading the SSI Image on Your SSM
Downgrading an MDS 9500 Series Switch with an 8-Gbps Module Installed
New Features in Cisco MDS NX-OS Release 4.2(9)
Licensed Cisco NX-OS Software Packages
Storage Services Enabler Package
On-Demand Port Activation License
Storage Media Encryption Package
Generation 1 Module Limitation
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
PPRC Not Supported with FCIP Write Acceleration
Rule Changes Between SAN-OS Release 3.3(1c) and NX-OS Release 4.2(1a) Affect Role Behavior
RCS Not Supported in Cisco NX-OS Release 4.2(9)
A McData Switch Can Become Inaccessible After a Zone Set Deactivation
Configuring a Persistent FCID in an IVR Configuration with Brocade Switches
Incompatibility for the FC Redirect IVR Feature in Cisco NX-OS Release 4.2(9)
Internal Component Affects Certain Hardware Running Older Software
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 4.2(9)
Release Date: April 18, 2012
Part Number: OL-19964-13 D0
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.
Note
As of Cisco Fabric Manager Release 4.2(1a), Fabric Manager information will no longer appear in the Cisco MDS 9000 Family Release Notes for NX-OS releases. Cisco Fabric Manager Release Notes will include information that is exclusive to Fabric Manager as a management tool for Cisco MDS 9000 Family switches and Cisco Nexus 5000 Series switches. Refer to the following website for Release Notes for Cisco Fabric Manager:
http://www.cisco.com/en/US/products/ps10495/prod_release_notes_list.html
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
04/18/2012
Created release notes.
B0
04/20/2012
•
•
C0
05/18/2012
Added the "Converting Automatically Created PortChannels Before an Upgrade" section.
D0
06/25/2012
Revised the nondisruptive upgrade path to Cisco NX-OS Release 4.2(9) in Table 10.
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 in Cisco MDS NX-OS 4.x
Table 3 lists the MDS hardware chassis supported by Cisco MDS NX-OS 4.x.
Table 4 lists the MDS hardware modules supported by Cisco MDS NX-OS 4.x. For the list of MDS hardware modules supported by Cisco MDS SAN-OS 3.x, see Table 5.
Table 4 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
Yes
N/A
N/A
DS-X9530-SF1-K9
MDS 9500 Supervisor-1 Module
No
N/A
N/A
DS-X9224-96K9
24-port 8-Gbps Fibre Channel Switching Module
Yes1
No
No
DS-X9248-96K9
48-port 8-Gbps Fibre Channel Switching Module
Yes1
No
No
DS-X9248-48K9
4/44-port Host Optimized8-Gbps Fibre Channel Switching Module
Yes
Yes
Yes
DS-X9316-SSNK9
16-port Storage Services Node (SSN-16)
Yes
Yes
No
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 Requires DS-13SLT-FAB2 in the MDS 9513.
Table 5 lists the MDS hardware modules supported by Cisco MDS SAN-OS 3.x.
Migrating from Supervisor-1 Modules to Supervisor-2 Modules
As of Cisco MDS SAN-OS Release 3.0(1), the Cisco MDS 9509 and 9506 Directors support both Supervisor-1 and Supervisor-2 modules. Supervisor-1 and Supervisor-2 modules cannot be installed in the same switch, except during migration. Both the active and standby supervisor modules must be of the same type, either Supervisor-1 or Supervisor-2 modules. For Cisco MDS 9513 Directors, both supervisor modules must be Supervisor-2 modules.
Caution
Note
To migrate from a Supervisor-1 module to a Supervisor-2 module, refer to the step-by-step instructions in the Cisco MDS 9000 NX-OS Release 4.1(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide.
Supervisor-2A Module
The Cisco MDS 9500 Series Supervisor-2A module, DS-X9530-SF2A-K9, is a new supervisor module for the Cisco MDS 9500 Series. The Supervisor-2A module is functionally equivalent to the Supervisor-2 module, but has these distinguishing features:
•
•
For additional information about the Supervisor-2A module, see the Cisco MDS 9500 Series Supervisor-2A Tech Note.
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 the Fabric Manager, view the Switches tab in the Information pane, locate the switch using the IP address, logical name, or WWN, and check its version in the Release column.
Determining Software Version Compatibility
Table 6 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/public/sw-center
See the following sections in this release note for details on how you can nondisruptively upgrade your Cisco MDS 9000 switch. Issuing the install all command from the CLI, or using Fabric Manager to perform the downgrade, enables the compatibility check. The check indicates if the upgrade can happen nondisruptively or disruptively depending on the current configuration of your switch and the reason.
Compatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------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:1.3(x)_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 7.
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 8.
Selecting the Correct Software Image for an MDS 9500 Series Switch
The system and kickstart image that you use for an MDS 9500 Series switch depends on whether the switch is based on a Supervisor-1 module or a Supervisor-2 module, as shown in Table 9.
Table 9 Software Images for Supervisor Type
9513, 9509, and 9506
Supervisor-2 module
Filename begins with m9500-sf2ek9
Use the show module command to display the type of supervisor module in the switch. The following is sample output from the show module command on a Supervisor -2 module:
switch# show 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-standbyUpgrading 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 Fabric Manager, see the Cisco Fabric Manager Release Notes for Release 4.2(1a), which is available from the following website:
http://www.cisco.com/en/US/products/ps10495/prod_release_notes_list.html
General Upgrading Guidelines
Note
Use the following guidelines when upgrading to Cisco MDS NX-OS Release 4.2(9):
•
•
•
•
•
•
•
•
–
–
–
–
–
Note
Use Table 10 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 4.2(9), find the image release number you are currently using in the Current column of the table, and use the path recommended.
Note
FICON Supported Releases and Upgrade Paths
Cisco MDS NX-OS Release 4.2(9) is not a FICON-qualified release.
Table 11 lists additional SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes for FICON upgrade path information.
Use Table 12 to determine your FICON nondisruptive upgrade path to Cisco MDS NX-OS Release 4.2(1b). 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.
Upgrading an MDS 9222i Switch with SANTap or Invista is Provisioned on the SSM
On an MDS 9222i switch, if SANTap or Invista is provisioned on a Storage Services Module (SSM) in slot 2, then an In-Service Software Upgrade (ISSU) to NX-OS Release 4.2(1b) is not supported. The upgrade to NX-OS Release 4.2(1b) is supported if you set boot variables, save the configuration, and reload the switch. If the switch is running SAN-OS Release 3.3(1a) or earlier, first upgrade to SAN-OS Release 3.3(1c) and then upgrade to NX-OS Release 4.2(1b).
Enabling Telnet Required After an Upgrade
Following an upgrade from SAN-OS 3.x to NX-OS 4.x, you need to enable the Telnet server if you require a Telnet connection. As of MDS NX-OS Release 4.1(1b), the Telnet server is disabled by default on all switches in the Cisco MDS 9000 Family. In earlier releases, the Telnet server was enabled by default.
Upgrading Effect on VSAN 4079
If you are upgrading from a SAN-OS Release 3.x to NX-OS Release 4.2(1b), and you have not created VSAN 4079, the NX-OS software will automatically create VSAN 4079 and reserve it for EVFP use.
If VSAN 4079 is reserved for EVFP use, the switchport trunk allowed vsan command will filter out VSAN 4079 from the allowed list, as shown in the following example:
switch(config-if)# switchport trunk allowed vsan 1-40801-4078,4080switch(config-if)#
If you have created VSAN 4079, the upgrade to NX-OS Release 4.2(1b) will have no affect on VSAN 4079.
If you downgrade after NX-OS Release 4.2(1b) creates VSAN 4079 and reserves it for EVFP use, the VSAN will no longer be reserved.
Upgrading with IVR Enabled
An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive. Some possible scenarios include the following:
•
•
•
If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state because of a domain overlap.
This issue was resolved in Cisco SAN-OS Release 2.1(2b); you must upgrade to Release 2.1(2b) before upgrading to Release 3.3(1c). An upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) when IVR is enabled requires that you follow the procedure below. If you have VSANs in interop mode 2 or 3, you must issue an IVR refresh for those VSANs.
To upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) for all other VSANs with IVR enabled, follow these steps:
Step 1
Note
Step 2
Note
Step 3
2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED:%$VSAN 2005%$ Isolation of interfacePortChannel 52 (reason: unknown failure)2005 Aug 31 21:52:04 switch %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN 2005%$Isolation of interface PortChannel 51(reason: domain ID assignment failure)Step 4
switch(config)# vsan databaseswitch(config-vsan-db)# vsan vsan-id suspendswitch(config-vsan-db)# no vsan vsan-id suspendStep 5
Step 6
Step 7
Note
Reconfiguring SSM Ports Before Upgrading to NX-OS Release 4.2(9)
Starting with Cisco MDS SAN-OS Release 3.0(1), the SSM front panel ports can no longer be configured in auto mode, which is the default for releases prior to Release 3.0(1).
Note
For more information on upgrading SAN-OS software, see the "Upgrading Your Cisco MDS NX-OS Software Image" section.
If the configuration is not updated before the upgrade, the installation process for the new image will automatically convert all ports configured in auto mode to Fx mode. This change in mode might cause a disruption if the port is currently operating in E mode.
To upgrade the image on your SSM without any traffic disruption, follow these steps:
Step 1
switch# show interface fc 2/1 - 32fc2/1 is upHardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)Port WWN is 20:4b:00:0d:ec:09:3c:00Admin port mode is auto <-------- shows port is configured in auto modesnmp traps are enabledPort mode is F, FCID is 0xef0300 <-------- shows current port operational mode is FPort vsan is 1Speed is 2 GbpsTransmit B2B Credit is 3Step 2
a.
switch# config tswitch(config)# interface fc 2/1switch(config-if)# switchport mode fxb.
switch# config tswitch(config)# interface fc 2/5switch(config-if)# switchport mode eStep 3
a.
switch# config tswitch(config)# interface fc 2/2switch(config-if)# switchport mode fxb.
switch# config tswitch(config)# interface fc 2/2switch(config-if)# shutdownStep 4
switch# copy running-config startup-config
Upgrading the SSI Image on Your SSM
Use the following guidelines to nondisruptively upgrade the SSI image on your SSM:
•
•
–
–
–
–
–
Upgrading a Cisco MDS 9124 or Cisco MDS 9134 Switch
If you are upgrading from Cisco MDS SAN-OS Release 3.1(1) to Cisco NX-OS Release 4.2(9) on a Cisco MDS 9124 or MDS 9134 Switch, follow these guidelines:
•
•
•
•
•
•
Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch
Cisco MDS SAN-OS software upgrades are disruptive on the Cisco MDS 9216i switch, which has a single supervisor. If you are performing an upgrade on this switch, you should follow the nondisruptive upgrade path shown in Table 10, even though the upgrade is disruptive. Following the nondisruptive upgrade path ensures that the binary startup configuration remains intact.
If you do not follow the upgrade path, (for example, you upgrade directly from SAN-OS Release 2.1(2) or earlier version to NX-OS Release 4.2(x)), the binary startup configuration is deleted because it is not compatible with the new image, and the ASCII startup configuration file is applied when the switch comes up with the new upgraded image. When the ASCII startup configuration file is applied, there may be errors. Because of this, we recommend that you follow the nondisruptive upgrade path.
Note
Resetting SNMP Notifications Following an Upgrade
The SNMP notification configuration resets to the default settings when you upgrade to Cisco NX-OS Release 4.2(1b). Use the snmp-server enable traps command to reenable your required SNMP notifications.
Converting Automatically Created PortChannels Before an Upgrade
Before upgrading from NX-OS Release 4.1(x) or 4.2(x) to Release 5.x, ensure that you do not have any automatically created PortChannels present in the switch configuration. Use the port-channel persistent command to convert an automatically created PortChannel to a persistent PortChannel. Failure to convert automatically created PortChannels prior to the upgrade can result in traffic disruption because Autocreation of PortChannels is a deprecated feature as of NX-OS Release 4.1(1b).
Downgrading Your Cisco MDS SAN-OS Software Image
This section lists the guidelines recommended for downgrading your Cisco MDS SAN-OS software image and includes the following topics:
•
•
General Downgrading Guidelines
Use the following guidelines to nondisruptively downgrade from Cisco MDS NX-OS Release 4.2(9):
•
•
•
•
•
–
–
–
–
–
Note
1.
2.
If these conditions exist, remove the application configuration for these targets and hosts before proceeding with the downgrade.
Use Table 13 to determine the nondisruptive downgrade path from Cisco NX-OS Release 4.2(1b). Find the SAN-OS image you want to downgrade to in the To SAN-OS Release column of the table and use the path recommended.
Note
FICON Downgrade Paths
Table 14 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.
Downgrading the SSI Image on Your SSM
Use the following guidelines when downgrading your SSI image on your SSM:
•
•
•
•
–
–
–
Downgrading an MDS 9500 Series Switch with an 8-Gbps Module Installed
If you attempt to perform a nondisruptive software downgrade from NX-OS Release 4.x to SAN-OS Release 3.x on an MDS 9500 Series switch that has an 8-Gbps module installed, the switch should display a message that the module is unsupported and stop the downgrade. Instead, the switch displays a message that the module is unsupported and proceeds with a disruptive downgrade. The following table shows the actual and expected behavior of the switch for a software downgrade.
Table 15 Downgrade Behavior on an MDS 9500 Series Switch with 8-Gbps Module Installed
DB mode1
MDS 9513 with 8-Gbps module
4.2(9)
3.3(x)
Disruptive
Abort. Disruptive after powerdown of 8-Gbps module.
DB mode
MDS 9513 without 8-Gbps module
4.2(9)
3.3(x)
Disruptive
Disruptive.
BM mode2
MDS 9513 with 8-Gbps module
4.2(9)
3.3(x)
Abort
Abort. Nondisruptive after powerdown of 8-Gbps module.
BM mode
MDS 9513 without 8-Gbps module
4.2(9)
3.3(x)
Nondisruptive
Nondisruptive.
BM mode
MDS 9509 or 9506 with 8-Gbps module
4.2(9)
3.3(x)
Abort
Abort. Nondisruptive after powerdown of 8-Gbps module.
BM mode
MDS 9509 or 9506 without 8-Gbps module
4.2(9)
3.3(x)
Nondisruptive
Nondisruptive.
1 DB mode is the fabric mode that supports Generation 3 8-Gbps modules in an MDS 9513 switch chassis.
2 BM mode is the fabric mode that does not support Generation 3 8-Gbps modules in an MDS 9513 switch chassis.
New Features in Cisco MDS NX-OS Release 4.2(9)
Cisco MDS NX-OS Release 4.2(9) is a maintenance release that includes only bug fixes. There are no new features in this release.
Licensed Cisco NX-OS Software Packages
Most Cisco MDS 9000 family software features are included in the standard package. However, some features are logically grouped into add-on packages that must be licensed separately, such as the Cisco MDS 9000 Enterprise package, SAN Extension over IP package, Mainframe package, Fabric Manager Server (FMS) package, Storage Services Enabler (SSE) package, Storage Media Encryption package, and Data Mobility Manager package. On-demand ports activation licenses are also available for the Cisco MDS Blade Switch Series and 4-Gbps Cisco MDS 9100 Series Multilayer Fabric switches.
Enterprise Package
The standard software package that is bundled at no charge with the Cisco MDS 9000 Family switches includes the base set of features that Cisco believes are required by most customers for building a SAN. The Cisco MDS 9000 family also has a set of advanced features that are recommended for all enterprise SANs. These features are bundled together in the Cisco MDS 9000 Enterprise package. Refer to the Cisco MDS 9000 Enterprise package fact sheet for more information.
SAN Extension over IP Package
The Cisco MDS 9000 SAN Extension over IP package allows the customer to use FCIP to extend SANs over wide distances on IP networks using the Cisco MDS 9000 family IP storage services. Refer to the Cisco MDS 9000 SAN Extension over IP package fact sheet for more information.
Mainframe Package
The Cisco MDS 9000 Mainframe package uses the FICON protocol and allows control unit port management for in-band management from IBM S/390 and z/900 processors. FICON VSAN support is provided to help ensure true hardware-based separation of FICON and open systems. Switch cascading, fabric binding, and intermixing are also included in this package. Refer to the Cisco MDS 9000 Mainframe package fact sheet for more information.
Storage Services Enabler Package
The Cisco MDS 9000 SSE package allows network-based storage applications and services to run on the Cisco MDS 9000 family SSMs, Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4), and Cisco MDS 9222i. Intelligent fabric applications simplify complex IT storage environments and help organizations gain control of capital and operating costs by providing consistent and automated storage management. Refer to the Cisco MDS 9000 SSE package fact sheet for more information.
On-Demand Port Activation License
On-demand ports allow customers to benefit from Cisco NX-OS Software features while initially purchasing only a small number of activated ports on 4-Gbps Cisco MDS 9100 Series Multilayer Fabric switches. As needed, customers can expand switch connectivity by licensing additional ports.
Storage Media Encryption Package
The Cisco MDS 9000 Storage Media Encryption package enables encryption of data at rest on heterogeneous tape devices and virtual tape libraries as a transparent fabric service. Cisco SME is completely integrated with Cisco MDS 9000 Family switches and the Cisco Fabric Manager 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 Fabric Manager 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.
I/O Accelerator Package
The Cisco I/O Accelerator (IOA) package activates IOA on the Cisco MDS 9222i fabric switch, the Cisco MDS 9000 18/4 Multiservice Module (MSM-18/4), and on the SSN-16 module. The IOA package is licensed per service engine and is tied to the chassis. The number of licenses required is equal to the number of service engines on which the intelligent fabric application is used.The SSN-16 requires a separate license for each engine on which you want to run IOA. Each SSN-16 engine that you configure for IOA checks out a license from the pool managed at the chassis level. SSN-16 IOA licenses are available as single licenses.
XRC Acceleration License
The Cisco Extended Remote Copy (XRC) acceleration license activates FICON XRC acceleration on the Cisco MDS 9222i switch and on the MSM-18/4 in the Cisco MDS 9500 Series directors. One license per chassis is required. You must install the Mainframe Package and the SAN Extension over FCIP Package before you install the XRC acceleration license. The Mainframe Package enables the underlying FICON support, and the FCIP license or licenses enable the underlying FCIP support. XRC acceleration is not supported on the SSN-16.
Limitations and Restrictions
This section lists the limitations and restrictions for this release. The following limitations are described:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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:
•
•
Red Hat Enterprise Linux
The Linux kernel core dump is not supported in NX-OS Release 4.1(1b) and later versions and therefore the CLI command has been removed. A syntax error message will be displayed if you import configurations from SAN-OS Release 3.3(x) and earlier to NX-OS Release 4.1(1b) and later. These syntax errors do not affect the application of other commands in the configuration and can be safely ignored. To address this, remove the kernel core configuration from the ASCII configuration file before importing the configuration.
Generation 1 Module Limitation
When a Cisco or other vendor switch port is connected to a Generation 1 module port (ISL connection), the receive buffer-to-buffer credit of the port connected to a Generation 1 module port should not exceed 255.
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.2(9), follow these steps:
Step 1
Step 2
Step 3
Step 4
Proceed with the upgrade to NX-OS Release 4.2(9).
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
In NX-OS Release 4.2(9), IOA does not support the following NX-OS features:
•
•
•
•
Support for FCIP Compression Modes
In Cisco NX-OS Release 4.2(9), 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(9), 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.
PPRC Not Supported with FCIP Write Acceleration
IBM Peer to Peer Remote Copy (PPRC) is not supported with FCIP Write Acceleration.
Rule Changes Between SAN-OS Release 3.3(1c) and NX-OS Release 4.2(1a) Affect Role Behavior
The rules that can be configured for roles were modified between SAN-OS Release 3.3(1c) and NX-OS Release 4.2(1a). As a result, roles do not behave as expected following an upgrade from SAN-OS Release 3.3(1c) to NX-OS Release 4.2(1a). Manual configuration changes are required to restore the desired behavior.
Rule 4 and Rule 3: after the upgrade, exec and feature are removed. Change rule 4 and rule 3 as follows:
rule 4 permit exec feature debug
rule 4 permit debug
rule 3 permit exec feature clear
rule 3 permit clear
Rule 2: after the upgrade, exec feature license is obsolete.
rule 2 permit exec feature license
Not available in Release 4.2(1).
Rule 9, Rule 8, and Rule 7: after the upgrade, you need to have the feature enabled to configure it. In SAN-OS Release 3.3(1c), you could configure a feature without enabling it.
RCS Not Supported in Cisco NX-OS Release 4.2(9)
Cisco NX-OS Release 4.2(9) does not support the Reliable Commit Service (RCS) feature. Brocade Fabric OS (FOS) version 5.0.5f does support RCS. As a result, if you have an MDS switch that is running NX-OS Release 4.2(9) connected to a Brocade switch that is running FOS version 5.0.5f, and you attempt to activate the IVR zone set from the MDS switch, the active IVR zone set database will not be propagated to the Brocade switch. The host on the Brocade switch will not receive the RSCN when a regular zone set is activated or deactivated on the MDS switch, but the active and full zone set database will be propagated to the Brocade switch.
Cisco NX-OS Release 5.0(1a) and later releases support RCS.
A McData Switch Can Become Inaccessible After a Zone Set Deactivation
In a fabric with an MDS switch that is running Cisco NX-OS Release 4.2(9) and a McData switch where there is an active IVR zone set and an active regular zone set, deactivating the zone set on the McData switch will cause the McData switch to become inaccessible and unreachable by ping. If this situation occurs, do one of the following:
•
•
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.
Incompatibility for the FC Redirect IVR Feature in Cisco NX-OS Release 4.2(9)
A software incompatibility for the FC Redirect IVR feature exists between Cisco NX-OS Release 4.2(9) and Release 4.2(5). As a result, if you install Release 4.2(9) and configure IOA or SME and then downgrade to Release 4.2(5), you will not be able to upgrade to Release 4.2(9) because the FC Redirect IVR capability that is enabled in Release 4.2(5) is not supported in Release 4.2(9). To work around this issue, follow these steps:
1.
2.
3.
4.
5.
Internal Component Affects Certain Hardware Running Older Software
If you are running Cisco SAN-OS Release 3.3(x), the following Cisco MDS 9000 devices will not come up if they use a specific version of an internal component:
–
–
If you encounter this issue, upgrade to NX-OS Release 4.2(9), which is the minimum software release that has the fix for this issue.
For additional information, see CSCty32238.
Caveats
This section lists the open and resolved caveats for this release. Use Table 16 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 RSCN process might fail and cause a system reload. This symptom might be seen when many RSCNs are transmitted due to links changing state, but no responses are received from the destinations.
Workaround: This issue is resolved.
•
Symptom: The module manager process fails on a Cisco MDS 9000 switch that is running the special engineering NX-OS Release 4.2(7dE3), if the switch has a Generation 1 module installed. The failure occurs because the size of the image-compatibility matrix (srg) that is part of the module image increases. If the srg size is greater than 10KB during boot up, it causes memory corruption in module manager that results in the module manager fails. This issues does not occur on a switch that does not have a Generation 1 module.
Workaround: This issue is resolved.
•
Symptom: The initiator-side FCIP or IOA engine fails. This issue might be seen under certain rare conditions when FCP-2 error recovery procedures are invoked by the initiator to recover a SCSI read operation.
Workaround: This issue is resolved.
•
Symptom: In a very rare corner case, IVR fails when it gets a corrupted device update (DU) payload.
Workaround: This issue is resolved.
•
Symptom: The port-monitor feature incorrectly logs alerts that BB credit is not-available following an ISSU to Cisco NX-OS Release 4.2(7). This symptom might be seen when there are idle ports, or ports that not experiencing buffer credit loss, the port-monitor feature logs alerts for a BB credit not-available condition, even though the condition does not actively exist on the switch.
Workaround: This issue is resolved.
•
Symptom: In configuration where slow-drain timeout is configured, congestion-drop-timeout and preemptive-drop-timeout do not get applied.
Workaround: This issue is resolved.
•
Symptom: Cisco MDS 9000 fabric switches should include fc2 commands in the show tech command.
Workaround: This issue is resolved.
•
Symptom: A "BB credit not available" event is triggered by the Port Monitor before 100 msec, even though the configured value for the event to get trigger is 100 ms.
Workaround: This issue is resolved.
•
Symptom: A Fibre Channel port does not come up, but stays in init state. This symptom might be seen after a port link error recovery that is initiated by the module.
Workaround: This issue is resolved.
•
Symptom: If you use port-monitor policies with the portguard actions of "errdisable" or "flap" with the Absolute Threshold set, make sure that there are no old or stale counters for the port-monitor counter you are monitoring. If the counter has old or stale entries that are at or above the rising-threshold value, the interfaces specified in the Port Type field of the policy might go down once the policy is activated.
Workaround: This issue is resolved.
•
Symptom: If the number of mbufs in the compressed IO packet is 256, the IPS processor does not compact the IO packet.
Workaround: This issue is resolved.
•
Symptom: The Fabric-Device Management Interface (FDMI) cores are generated on a Cisco MDS 9500 switch. This symptom might be seen when FDMI is busy processing MTS messages, and it fails to send a heartbeat.
Workaround: This issue is resolved.
•
Symptom: An MDS 9000 Family switch does not respond to an FDISC from an NPV-attached switch if the MDS 9000 switch is already processing an FDISC for the same pWWN. This issue occurs when the downstream device is running in NPV mode and the FDISC for the same pWWN must be in progress and no ABTS is sent to cancel the in-progress FDISC.
Workaround: This issue is resolved.
•
Symptom: Under extremely rare circumstances, a Cisco MDS 9000 switch might fail and reload. After the reload, the output of the show system reset-reason command indicates that the trigger was an HA policy.
switch# show system reset-reason----- reset reason for Supervisor-module 8 (from Supervisor in slot 8) ---1) At 658542 usecs after Tue Nov 30 18:17:46 2010Reason: Reset triggered due to HA policy of ResetService: rib hap resetVersion: 4.2(3)This issue can happen only if an external event triggers a RIB update. Examples of these types of external events include module insertions or reloads, and the addition of new switches and VSANs to a fabric.
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: 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: Fabric Manager Server (FMS) sends multiple EMC E-mail Home e-mail messages when a module fails. This symptom might be seen when a Cisco MDS 9000 module fails and the MDS 9000 switch is running Cisco NX-OS Release 5.0(x) or Release 5.2(x).
Workaround: This issue is resolved.
•
Symptom: A Cisco MDS 9500 Series switch might reset due to an IVR failure. The reset is triggered by the HA reset policy. The show cores command displays the following output:
switch# show coresModule-num InstanceProcess PID Core-create-time---------- ------------ ------------ --- -----------8 1 ivr 3020 Aug 14 00:198 1 ivr 27476 Aug 14 00:197 1 ivr 3024 Aug 14 00:197 1 ivr 544 Aug 14 00:19This symptom might be seen on a Cisco MDS 9500 Series switch that is running NX-OS Release 4.2(7b).
Workaround: This issue is resolved.
•
Symptom: An SNMP MIB walk on CiscoFcFeMIB over 64 iterations detected ~400K memory leak.
Workaround: This issue is resolved.
•
Symptom: In very rare circumstances, the communication between 2 VSANs in an IVR NAT topology can get interrupted. In the path between the VSANs, one of the switches stops exporting the devices to the next hop VSAN, and the output of the show ivr internal pvm command on that switch shows that the RSCN_OFFLINE_SENT flag has been set for all affected devices.
Workaround: This issue is resolved.
•
Symptom: On certain hardware, IVR does not work. If IVR is not configured on the switch where the module is installed, then there is no impact from this issue.
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: The following message is seen in the output of the show logging log command:
%KERN-3-SYSTEM_MSG: Both SYN and FIN bits are set. Discard this packet - kernelThis symptom might be seen when an application is trying to establish a TCP connection to the mgmt port and both the SYN and FIN bits are set. As per the protocol, if both the SYN and FIN bits are set, then the packet is illegal and should be discarded.
Workaround: This issue is resolved.
•
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: In very rare circumstances, the SANTap process or the SME process might fail. If the failure occurs on the Cisco MDS9222i switch, it might cause a full switch reload. This symptom might be seen in NX-OS Release 4.1(x) software.
Workaround: This issue is resolved.
•
Symptom: The DMM CPP interface cpp1/1/1 does not come up unless there is an active port in VSAN 1. VSAN 1 is the DMM management VSAN.
Workaround: This issue is resolved.
•
Symptom: If QoS is enabled and you are running ZONE QOS and you globally disable it from Fabric Manager Server or a script that runs the CLI commands simultaneously across the fabric, you may not be able to activate the zone set after this event.
The output of the show logging log command shows the following message:
switch# 2010 Jun 2 18:47:47 switch %ZONE-2-ZS_CHANGE_ACA_FAILED: %$VSAN 1%$ ACA failed : domain 0x1 returns NO_REASON_CODEIf you try to activate the zone set from Fabric Manager Server, the following error message appears:
switch:zone: Qos needs to be enabled to perform this action
The problem is that QoS does gets disabled, however the QoS zone attribute parameters do not get cleaned up in the running configuration. This issue can occur in Basic and Enhanced Zoning Modes.
This symptom might be seen when you run ZONE QOS and disable QoS globally in the fabric.
Workaround: This issue is resolved.
•
Symptom: A SCSI flow that is configured for Fibre Channel write acceleration might disappear after a module reloads. This symptom can be seen under the following conditions:
–
–
Workaround: This issue is resolved.
•
Symptom: SFP tx power and current are not displayed correctly even though the interface is enabled.
This symptom might be seen when a port experiences the following sequence of events:
–
–
Workaround: This issue is resolved.
•
Symptom: The Cisco MDS 9222i failed with following reason:
switch# show system reset-reason----- reset reason for Supervisor-module 1 (from Supervisor in slot 1) ---1) At 436178 usecs after Thu Jul 15 09:39:32 2010Reason: Reset triggered due to HA policy of ResetService: Service "bootvar"Version: 3.3(4a)Workaround: This issue is resolved.
•
Symptom: The port-group-monitor feature does not generate alarms when the configured port-ASIC bandwidth threshold is crossed.
This symptom might be seen when the port-group-monitor feature is used on a Cisco MDS 9000 device that is running NX-OS Release 4.2(7). Alarms are not generated when the threshold is crossed, even when traffic is running that has crossed the threshold.
Workaround: This issue is resolved.
•
Symptom: A port on a Generation 3 module is disabled and set to hwFailure (hardware failure) state.
This symptom might be seen when a port MAC address experiences a double bit ECC error (type 87) as indicated in the output of the show logging onboard exceptionlog command:
"Error Description: IP_FCMAC_ERR Interrupt, port = x, src_bit = 87"Workaround: This issue is resolved.
•
Symptom: The Call Home service on a Cisco MDS 9500 series switch can fail and cause a supervisor switchover.
This symptom might be seen under normal working conditions. The following configuration sequence can lead to the failure:
destination-profile new_profile
destination-profile new_profile alert-group License
destination-profile new_profile alert-group Syslog-group-port
destination-profile new_profile message-level 5
Workaround: This issue is resolved.
•
Symptom: When creating a job, DMM intermittently reports:
DMM_JOB_INFRA_FC_REDIRECT_SETUP_ERRThis symptom might be seen when there are two or more paths to a host, multiple paths to existing storage, and multiple paths to the new storage.
Workaround: This issue is resolved.
•
Symptom The show fcdomain fcid command is not available to users with network-operator roles.
This symptom might be seen on Cisco MDS 9000 switches running NX-OS Release 4.2(x) and later releases.
Workaround: This issue is resolved.
•
Symptom: No Call Home email alert is generated specifically for Gigabit FCIP interfaces.
This symptom might be seen in NX-OS Release 4.1(x) and Release 4.2(x).
Workaround: This issue is resolved.
•
Symptom: The congestion-drop timer configuration should not allow a range be specified. One value should be specified.
Workaround: This issue is resolved.
•
Symptom: Call Home alerts are not sent for port or link down events. This symptom might be seen because Call Home messages are not generated after an upgrade to Cisco NX-OS Release 4.2(7a).
Workaround: This issue is resolved.
•
Symptom: The switch generates core files after a downgrade from NX-OS Release 4.2.7a to Release 4.1.3a.
Workaround: This issue is resolved.
•
Symptom: The port group monitor feature is enabled, and the log entry and trap are generated for "Rising Threshold > 100% of Port Group Bandwidth Used."
This symptom might be seen when the port group monitor feature is enabled in NX-OS Release 4.2(3).
Workaround: This issue is resolved.
•
Symptom: In certain conditions, when a server connected to a Cisco MDS 9000 Family switch is shut down, it appears to still be logged into the fabric. This issue might be seen in an IBM virtualized environment, with the VIOS connected to an NPV switch. When an LPAR that is running AIX is shut down, it remains logged into the fabric and its FC ID appears in the outputs of the show npv flogi-table command on the NPV switch and the show flogi database command on the core switch.
Workaround: This issue is resolved.
•
Symptom: The syslogd process fails in NX-OS
Workaround: This issue is resolved.
•
Symptom: The PMON counter command should be enabled only after monitoring is enabled.
Workaround: This issue is resolved.
•
Symptom: The SSM module reloads when the iSCSI process fails. This symptom might be seen when normal iSCSI operations are in progress.
Workaround: This issue is resolved.
•
Symptom: Output Discards may not appear in the output of the show interface fc slot/port command when the switch drops Class 3 Fibre Channel frames.
Workaround: This issue is resolved.
•
Symptom: The Fabric Configuration Server fails due to heartbeat failure when retrieving the switch port details from the port manager and updating its database.
Workaround: This issue is resolved.
•
Symptom: The port-group-monitor feature generates an alert that shows > 100% when the interface is changed to admin state up if the port-group-monitor policy is already active.
2010 Oct 19 12:40:00 switchname %PMON-SLOT6-2-PMON_RISING_THRESHOLD: PortGroup1 RX crossed rising threshold 50%, fc6/1=0%, fc6/2=891417%, fc6/3=0%, 891417%of port group bandwidth is used.2010 Oct 19 12:40:00 switchname %PMON-SLOT6-2-PMON_RISING_THRESHOLD: PortGroup1 TX crossed rising threshold 50%, fc6/1=0%, fc6/2=188287%, fc6/3=0%, 188287%of port group bandwidth is used.This symptom might be seen when using the port-group-monitor feature on Cisco MDS 9000 Series devices running NX-OS Release 4.2(3). Alarms are created erroneously if a port-group-monitor policy is active and a port in a port group is admin no shut.
Workaround: This issue is resolved.
•
Symptom: When upgrading from NX-OS Release 4.1(3a) to Release 5.0(1a), certain ports are brought down because of Diag failure. The following error messages appear:
2010 Jul 5 19:33:39 MDSSWITCH %IMAGE_DNLD-SLOT5-2-IMG_DNLD_STARTED:Module image download process. Please wait until completion...2010 Jul 5 19:33:57 MDSSWITCH %IMAGE_DNLD-SLOT5-2-IMG_DNLD_COMPLETE:Module image download process. Download successful.2010 Jul 5 19:35:00 MDSSWITCH %MODULE-5-LCM_MODULE_UPGRADE_END: Upgradeof module 5 ended2010 Jul 5 19:35:00 MDSSWITCH %PLATFORM-5-MOD_STATUS: Module 5current-status is MOD_STATUS_ONLINE/OK2010 Jul 5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE:%$VSAN 10%$ Interface fc5/37 is down (Diag failure)2010 Jul 5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE:%$VSAN 10%$ Interface fc5/38 is down (Diag failure)2010 Jul 5 19:35:00 MDSSWITCH %PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE:%$VSAN 10%$ Interface fc5/39 is down (Diag failure)The logs have the following error message:
5) Event:E_DEBUG, length:84, at 242335 usecs after Mon Jul 5 19:35:00 2010[103] 3170:ohms_lc_exception: ERROR: Exception from module 5PortBits 0xfff000000000This symptom might be seen when all interfaces that were brought down with "Diag failure" were listed in an exception that occurred before the upgrade was performed.
Workaround: This issue is resolved.
•
Symptom: The supervisor hangs and the mgmt0 interface does not respond. All data traffic through the system is lost.
This symptom might be seen only on the Cisco MDS 9222i switch. The watchdog does not recover the CPU automatically after the following type of exception occurs:
"Machine Check in kernel mode: Caused by (from MCSR=x): . Signal 7"
Workaround: This issue is resolved.
•
Symptom: After a change in IVR topology, such as after a new switch is added, there might be issues with establishing connectivity in new IVR zones. The scope of the problem is usually limited to certain switches and VSANs. On some of these switches, the show ivr internal vdri-fsm command shows that the virtual domain representing these switches' native VSANs in remote or transit VSANs is unexpectedly stuck in NOT_ADVERTISING state. The problem usually affects only new flows, that is, devices that have not been zoned or connected before the topology change. This symptom might be seen when IVR1 (non-NAT) is used.
Workaround: This issue is resolved.
•
Symptom: In rare circumstances, the FCS service on an Cisco MDS 9000 switch might fail. Messages similar to the following appear in the switch log:
2010 Nov 2 02:59:42 %SYSMGR-3-HEARTBEAT_FAILURE: Service "fcs" sent SIGABRT for not settingheartbeat for last 6 periods. Last heartbeat 31.42 secs ago.2010 Nov 2 02:59:43 %SYSMGR-2-SERVICE_CRASHED: Service "fcs" (PID 2913) hasn't caught signal 6(core will be saved).2010 Nov 2 02:59:43 %CALLHOME-2-EVENT: SW_CRASH fcs in slot 7 crashed with crash type : stateful crashWorkaround: This issue is resolved.
•
Symptom: RMON alarms that check the percentage-utilization bandwidth threshold may sometimes fail to report accurate values. This issue might occur when an internal SNMP get of the interface utilization fails, which triggers a false-positive RMON alarm that indicates a bandwidth utilization on an interface that is incorrect.
Workaround: This issue is resolved.
•
Symptom: An iSCSI configuration might not be completely restored following an unsuccessful upgrade and switchover.
Workaround: This issue is resolved.
•
Symptom: When an FCIP links starts dropping frames due to congestion control, there is no message given to the user. This issue occurs only in NX-OS Release 4.2 and later.
Workaround: This issue is resolved.
•
Symptom: Call Home is not created for a standby supervisor failure. This issue was seen when the standby supervisor failed and was periodically being reset. When the switch was checked, the standby supervisor was in active state or powered on.
Workaround: This issue is resolved.
•
Symptom: An upgrade from SAN-OS Release 3.3(4) to Release 4.2(7a) on a Cisco MDS 9124e 24-port Fabric Switch for c-Class BladeSystem is disruptive. The install all command ended with the following messages before reload:
switch#
> version 4.1(3)
> callhome
> email-contact abc@cisco.com <mailto:abc@cisco.com>
> phone-contact +14087994089
> streetaddress xyxxyxWorkaround: This issue is resolved.
•
Symptom: The Cisco 9222i switch spontaneously reboots itself, and the following stack trace can be seen in the output of the show system exception command:
> 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 allWorkaround: This issue is resolved.
•
Symptom: Following an interface flap, the interface goes into an error-disabled state because it reaches the port reinitialization limit. Either the interface is down (error disabled), or the vendor reports out-of-order PLOGIs. This symptom might be seen when Fibre Channel flows are configured. The issue is severe when many Fibre Channel flows are configured and if the device that flaps is in many zones with many zone members.
Workaround: This issue is resolved.
•
Symptom: An RSCN is not sent to zone members in an IVR remote VSAN when the physical interface goes down. This symptom might be seen when the devices are in an IVR zone. The RSCN is sent to the local IVR VSAN zone members, but not to the remote IVR VSAN zone members.
Workaround: This issue is resolved.
•
Symptom: Some SNMP ipAddrEntry requests do not return with Get-Next.
Workaround: This issue is resolved.
•
Symptom: The Cisco MDS IOA feature fails when IOA flows frequently flap due to logout and 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 SAN-OS Release 3.3(1c) to NX-OS Release 4.2(7d).
Workaround: This issue is resolved.
•
Symptom: The show interface fcipx command shows Path MTU 592 instead of the interface or other higher path MTU. This symptom might be seen after a reload or activation of the module that contains the Gigabit Ethernet interfaces used in FC IP.
Workaround: This issue is resolved.
•
Symptom: Lower than expected performance occurs when a Qlogic HBA is connected to a Cisco MDS 9000 switch and a port is configured in F mode.
Workaround: This issue is resolved.
•
Symptom: DMM is limited to five jobs per storage port.
Workaround: This issue is resolved.
•
Symptom: Attempt to add ITLs to tape-device in Cisco Fabric Manager results in the following message:
There was a problem adding tape path to tape device xxx. (Failed to create Path Tape Device: xxx Error: Failure response received from the switch: Previous config in progress. Please try again later.) Please try again.
Workaround: This issue is resolved.
•
Symptom: A Tivoli Storage Manager (TSM) that is in an IOA flow logs ANR8311E errno=16. This symptom might be seen when IOA sends a SCSI busy message to the TSM server.
Workaround: This issue is resolved.
•
Symptom: The standby supervisor remains in a powered-up state and not ha-standby even though a process is failing.
Workaround: This issue is resolved.
Open Caveats
•
Symptom: Packet errors are seen on an ASIC on the 18/4-Port Multiservice Module (MSM-18/4).
The issue might be seen on the 18/4-Port Multiservice Module (MSM-18/4) when one of the SPI interfaces from an ASIC is connected to the Octeon processor.
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(5), 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)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2012 Cisco Systems, Inc. All rights reserved.
