Table of Contents
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 “Obtaining Documentation and Submitting a Service Request” 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 online change history for this document.
- Components Supported
- MDS 9000 Chassis and Module Support
- Software Download Process
- Upgrading Your Cisco MDS NX-OS Software Image
- Downgrading Your Cisco MDS SAN-OS Software Image
- New Software Features in Cisco NX-OS Release 6.2(7)
- Licensed Cisco NX-OS Software Packages
- Limitations and Restrictions
- Obtaining Documentation and Submitting a Service Request
The Cisco MDS 9000 Family of Multilayer Directors and Fabric Switches provides industry-leading availability, scalability, security, and management, allowing you to deploy high performance storage-area networks with lowest total cost of ownership. Layering a rich set of intelligent features onto a high performance, protocol agnostic switch fabric, the Cisco MDS 9000 Family addresses the stringent requirements of large data center storage environments: uncompromising high availability, security, scalability, ease of management, and seamless integration of new technologies.
Cisco MDS 9000 NX-OS software powers the award-winning Cisco MDS 9000 Series Multilayer Switches. It is designed to create a strategic SAN platform with superior reliability, performance, scalability, and features. Formerly known as Cisco SAN-OS, Cisco MDS 9000 NX-OS software is fully interoperable with earlier Cisco SAN-OS versions and enhances hardware platform and module support.
Table 2 lists the NX-OS software part numbers and hardware components supported by the Cisco MDS 9000 Family.
Note For the latest information about supported transceivers, see the Cisco MDS 9000 Family Pluggable Transceivers data sheet.
Table 3 lists the part numbers and optical components supported by the Cisco MDS 9000 Family.
Table 4 lists the MDS hardware chassis supported by Cisco MDS NX-OS Release 6.2 7.
Table 5 lists the MDS hardware chassis supported by Cisco MDS NX-OS Release 5.x.
Table 6 lists the MDS hardware modules supported Cisco MDS NX-OS Release 6.2 Table 7 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 8 . For the list of MDS hardware modules supported by Cisco MDS SAN-OS 3.x, see Table 9 .
9.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.
Table 9 lists the MDS hardware modules supported by Cisco MDS SAN-OS 3.x.
18/4-Port Multiservice Module (MSM-18/4)12
11.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.
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
- Determining Software Version Compatibility
- Downloading Software
- Selecting the Software Image for an MDS 9148 Switch
- Selecting the Software Image for an MDS 9222i Switch
- Selecting the Software Image for an MDS 9500 Series Switch
- Selecting the Software Image for an MDS 9710 Switch
- NPE Software Images
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.
Table 10 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.
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.
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.
The system and kickstart image that you use for an MDS 9148 switch is shown in Table 11 .
The system and kickstart image that you use for an MDS 9222i switch is shown in Table 12 .
The system and kickstart image that you use for an MDS 9250i switch is shown in Table 13 .
The system and kickstart image that you use for an MDS 9500 Series switch with a Supervisor-2 or Supervisor-2A module is shown in Table 14 . Cisco NX-OS Release 6.x, Release 5.x, and Release 4.x do not support the Supervisor-1 module.
The system and kickstart image that you use for an MDS 9710 switch is shown in Table 15 .
No payload encryption (NPE) images are available with Cisco MDS NX-OS Release 6.2(7) software. The NPE images are intended for countries who have import restrictions on products that encrypt payload data.
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.
Note Before you begin the upgrade process, review the list of chassis and modules that Cisco MDS NX-OS Release 6.2(7) supports. See the “MDS 9000 Chassis and Module Support” section.
An ISSU or ISSD involves a supervisor switchover, so it is very important that you determine if this issue is present before a supervisor switchover occurs. If this issue is detected before the supervisor switchover, the affected interfaces can be restored easily by entering the shutdown and no shutdown command sequence.
If you see that an interface has a Max flogi key greater than 65535 before a system switchover, ISSU, or ISSD, you must disable the interface and then reenable it by using the shutdown command followed by the no shutdown command. This process disrupts the devices on the interface that is being shut down. After the devices relogin, the Max flogi key is reset to 1 and you can avoid this issue.
If an install and/or ISSU, or supervisor switchover has occurred, compare the number of devices fabric login (FLOGI) with the number of devices in the Fibre Channel Name Server (FCNS) local database. Enter the show flogi database and the show fcns database local commands and use the CLI outputs for comparison. If the FLOGI database has fewer entries than the FCNS local database, the issue has occurred.%FLOGI-1-MSG_FLOGI_REJECT_FCID_ERROR: %$VSAN xxx%$ [VSAN xxx, Interface fc4/19: mode[F]] FLOGI rejected - FCID allocation failed with error 0x401b0000.
Note If the Max flogi key value is a large number and is incrementing, it indicates that a device is repeatedly logging in. This situation might be a separate problem that needs further investigation. For assistance, contact the Cisco TAC.
- Review the nondisruptive upgrade path to Release 6.2(7) in Table 16 .
- Install and configure dual supervisor modules before the upgrade.
- Issue the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive.
- Be aware that some features impact whether an upgrade is disruptive or nondisruptive:
– Fibre Channel Ports : Fibre Channel ports can be nondisruptively upgraded without affecting traffic on the ports. See Table 16 for the nondisruptive upgrade path for all NX-OS and SAN-OS releases.
– Gigabit Ethernet Ports : Traffic on Gigabit Ethernet ports is disrupted during an upgrade or downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MSM-18/4 module and the MDS 9222i and MDS 9250i switch. Those nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the upgrade is in progress.
– FICON : If you have FICON enabled, the upgrade path is different. See the “FICON Supported Releases and Upgrade Paths” section.
Note In addition to these guidelines, you may want to review the information in the “Limitations and Restrictions” section prior to a software upgrade to determine if a feature may possibly behave differently following the upgrade.
Use Table 16 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 6.2(7). 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 The software upgrade information in Table 16 applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and intelligent services traffic.
Table 17 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 18 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.
- Issue the system no acl-adjacency-sharing execute command to disable ACL adjacency usage on Generation 2 modules. If this command fails, reduce the number of zones, IVR zones, TE ports, or a combination of these in the system and issue the command again.
- Disable all features not supported by the downgrade release. Use the show incompatibility system downgrade-image command to determine what you need to disable.
- Use the show install all impact downgrade-image command to determine if your downgrade will be nondisruptive.
- Be aware that some features impact whether a downgrade is disruptive or nondisruptive:
– Fibre Channel Ports : Fibre Channel ports can be nondisruptively downgraded without affecting traffic on the ports. See Table 19 for the nondisruptive downgrade path for all SAN-OS releases.
– Gigabit Ethernet Ports : Traffic on Gigabit Ethernet ports is disrupted during a downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MSM-18/4 module, and the MDS 9222i switch. Those nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the downgrade is in progress.
– FICON : If you have FICON enabled, the downgrade path is different. See the “FICON Downgrade Paths” section.
Use Table 19 to determine the nondisruptive downgrade path from Cisco NX-OS Release 6.2(7). 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 The software downgrade information in Table 19 applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP and intelligent services traffic.
Note Downgrading from Cisco MDS NX-OS Release 6.2(7) to Cisco MDS NX-OS Release 6.2(5a), 6.2(5), 6.2(3), or 6.2(1) on a Cisco MDS 9710 Director with 48-port 10-Gigabit FCoE module or VSAN configurations require additional steps that must be performed before downgrading. For more information, see Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide, Release 6.2(x).
Table 20 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.
This section briefly describes the new hardware introduced in Cisco NX-OS Release 6.2(7). For detailed information about the new hardware, see the Cisco MDS 9250i Hardware Installation Guide that is available from this URL:
The Cisco MDS 48-Port 10-Gigabit Fibre Channel over Ethernet Module (DS-X9848-480K9) is designed for the Cisco MDS 9710 Directors. The Cisco MDS 9710 Director supports up to eight 10 Gigabit Ethernet modules. These modules are hot-swappable and they support 10-Gigabit Ethernet ports in SFP+ form factor.
The Cisco MDS 48-Port 10-Gigabit Ethernet module delivers integrated Fibre Channel over Ethernet (FCoE), simplifies the network infrastructure and helps reduce costs. The FCoE module allows you to extend the existing Fibre Channel SANs by using FCoE. The Cisco MDS 48-Port 10-Gigabit Ethernet module supports connectivity to FCoE switching platforms and to FCoE devices. This module also supports connectivity to FCoE initiators and targets that only send FCoE traffic.
- Enhanced the scalability for zones, maximum devices in the fabric and maximum devices in the switch.
- Forward Error Correction (FEC) for 16-Gbps ISL connections
- Enhanced scalability for simultaneous FLOGIs for Cisco MDS 9500 Series switches
- Restriction of the number of NPIV logins to not exceed the configuration limits in for Cisco MDS 9500 Series switches
- Command-line interface (CLI) command changes, including the following:
This section briefly describes the new hardware introduced in Cisco NX-OS Release 6.2(5). For detailed information about the new hardware, see the Cisco MDS 9250i Hardware Installation Guide that is available from this URL:
The Cisco MDS 9250i Multiservice Fabric Switch (DS-C9250I-K9) is an optimized platform for deploying high-performance SAN extension solutions, distributed intelligent fabric services, and cost-effective multiprotocol connectivity for both open systems and mainframe environments.
The Cisco MDS 9250i switch offers 40 autosensing 2-, 4-, 8-, and 16-Gbps line-rate Fibre Channel ports, eight 10-Gigabit Ethernet Fibre Channel over Ethernet (FCoE) ports, and two 10-Gigabit Ethernet IP storage services ports in a fixed two-rack-unit (2RU) form factor.
- DMM support for Cisco MDS 9250i switch
- FCIP support for Cisco MDS 9250i switch
- FCR support for Cisco MDS 9250i switch
- IOA support for Cisco MDS 9250i switch
- Path Trace
- Command-line interface (CLI) command changes, including the following:
- Cisco MDS Data Mobility Manager (DMM) supports logical unit numbers (LUN) sizes that are larger than 2 terabyte. The supported number of sessions per DMM job is more than 255. For more information, see the Cisco MDS 9000 Family Data Mobility Manager Configuration Guide.
- FC-Redirect (FCR) support for Cisco MDS 9710 Director. For more information on IOA, see the Cisco MDS 9000 Family I/O Accelerator Configuration Guide. For more information on SME, see the Cisco MDS 9000 Family Storage Media Encryption Configuration Guide.
- Command-line interface (CLI) command changes, including the following:
Starting with Cisco NX-OS Release 6.2(1), the Cisco MDS 9000 Family supports the generic online diagnostics (GOLD) feature. With online diagnostics, you can test and verify the hardware functionality of a device while the device is connected to a live network. In particular, the online diagnostics help you verify that hardware and internal data paths are operating as designed so that you can rapidly isolate faults.
- Enhancement to map LDAP/AD users to Cisco NX-OS roles and allow both local and remote users to use SSH or Telnet.
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, and Data Mobility Manager package. On-demand ports activation licenses are also available for the Cisco MDS 9250i Multiservice Fabric Switch, Cisco MDS 9148 48-Port Multilayer Fabric Switch, and the Cisco MDS 8-Gb Fabric Switch for HP c-Class Blade System.
Note A license is not required to use the Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) module (DS-X9708-K9) and the Cisco MDS 48-Port 10- Gigabit Fibre Channel over Ethernet Module (DS-X9848-480K9).
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.
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.
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.
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.
On-demand ports allow customers to benefit from Cisco NX-OS Software features while initially purchasing only a small number of activated ports on the Cisco MDS 9250i Multiservice Fabric Switch, MDS 9148 48-Port Multilayer Fabric Switch, and the Cisco MDS 8-Gb Fabric Switch for HP c-Class Blade System. As needed, customers can expand switch connectivity by licensing additional ports.
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.
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.
- Cisco MDS 9250i Multiservice Fabric Switch
- Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) Module
- Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching Module
- Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching Module
- Cisco MDS 9000 48-port 16-Gbps Fibre Channel Switching Module
You cannot bring up these modules if these features are already configured. You should completely remove all configurations that include these features before you attempt to bring up these modules. In addition, you cannot configure these features after you bring up these modules.
- Fibre Channel Security Protocol (FC-SP) is currently not supported on the Cisco MDS 9710 Director and on Cisco MDS 9250i Multiservice Fabric Switch.
- Local switching is not supported on the Cisco MDS 9710 Director, but continues to be supported on the Cisco MDS 9500 Series.
- Online Health Management System (OHMS)—The Generic Online Diagnostics (GOLD) system provides diagnostics for the Cisco MDS 9710 Director instead of the OHMS. In Cisco NX-OS Release 6.2(5), the GOLD system does not provide any support for automation of corrective actions, such as rebooting modules based on error thresholds.
- ASCII File Can Be Copied to the Startup Configuration
- Fibre Channel Security Protocol (FC-SP) Not Supported
- Install Module Command Changes
- Fabric Binding Error Message
- IOA Scaling Support on Supervisor-2 Module
The install module module-number bios command is not supported on the Cisco MDS 9710 switch in Cisco NX-OS Release 6.2(1) and later releases. Use the install all command to upgrade the BIOS during a software upgrade.
When fabric binding is enabled, an error message appears whenever the Mainframe Package license is not installed, and also when the grace period is disabled. There is a functional impact associated with the error message, and the feature is enabled correctly.
This section lists the open and resolved caveats for this release. Use Table 21 to determine the status of a particular caveat. In the table, “O” indicates an open caveat and “R” indicates a resolved caveat.
Condition: This situation occurs if the Cisco Nexus 5000 switch in N_port virtualization (NPV) mode is connected to the Cisco MDS 9250i switch and the host and or target is connected to the Cisco Nexus 5000 switch.
Condition: When there are three or more E-port ISLs connected between two switches and if the zone merge has failed, the recovery action of Zone import fails. The symptom occurs only if there are three or more ISLs.[Wed Mar 21 15:50:40 IST 2012]:Thread[thread applet-com.cisco.dcbu.web.client.sme.applet.SmartcardApplet-1,4,https://172.16.1.1/sme/jsp/-threadGroup]:Initializing...[Wed Mar 21 15:50:42 IST 2012]:Thread[thread applet-com.cisco.dcbu.web.client.sme.applet.SmartcardApplet-1,4,https://172.16.1.1/sme/jsp/-threadGroup]:Module isModule Name: gclib.dll [Wed Mar 21 15:50:42 IST 2012]:Thread[Thread-11,4,https://172.16.1.1/sme/jsp/-threadGroup]:[Wed Mar 21 15:50:42 IST 2012]:Thread[Thread-11,4,https://172.16.1.1/sme/jsp/-threadGroup]:Looking for smartcard reader...[Wed Mar 21 15:50:51 IST 2012]:Thread[Thread-11,4,https://172.16.1.1/sme/jsp/-threadGroup]:Exception reading smartcard:CKR_OPERATION_NOT_INITIALIZED[Wed Mar 21 15:50:51 IST 2012]:Thread[Thread-11,4,https://172.16.1.1/sme/jsp/-threadGroup]:<fieldset class="cuesStatusBoxError"
Condition: This issue occurs if you create an SME cluster for recovery option as 2 of 3 by using Mozilla Firefox, version 11.0 or Microsoft Internet Explorer, version 8, on the Microsoft XP operating system, and then rekey the master key.
Symptom : When an In-Service Software Upgrade (ISSU) is performed from Cisco NX-OS Release 5.2(6b) to Release 6.2(1), LLDP command-line interface (CLI) commands are not available. In this situation, LLDP is running and traffic is flowing normally even after the ISSU, but the CLI commands are not available.
This symptom might be seen when feature-set fcoe was enabled on the original image, and feature lldps commands were working in the original image. Following the ISSU to Cisco NX-OS Release 6.2.1 image, the commands are not available.
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 appears:
sw-dc5-br2-12 %PROC_MGR-SLOT3-2-ERR_MSG: ERROR: PID 1144 (lc_mnt_mgr) exited abnormally, exit status (0xa)
sw-dc5-br2-12 %MODULE-2-MOD_MINORSWFAIL: Module 3 (serial: JAE1141ZB43) reported a failure in service lc_mnt_mgr
Symptom: Several control protocols are impacted because of the FCoE data traffic congestion in the traffic flows passing through, or originating, or terminating on a Cisco MDS 9250i switch that runs the default 7e network-qos policy.
Condition: This is a known limitation with 7e policy. With the 7e template, all control and data FCoE traffic is sent to a single queue. When congestion in the network is present, in addition to data packets, control packets also are impacted, which results in timeouts and drops for several control protocols. Control protocols might display errors.
Symptom: Inserting and removing an SFP in quick succession might cause the read operation to fail before completion with NACK errors, and the searching for supported speeds fails. This situation might prevent a port from coming up and the following error appears:
Symptom: The In-Service Software Upgrade (ISSU) or In-Service Software Downgrade (ISSD) of more than one Cisco MDS 9250i switch that are connected to one another might cause the VE/E links between them to go down.2013 Oct 10 14:09:07 sw234-9250i %ACLTCAM-2-ACL_TCAM_PHY_TCAM_WRITE_FAILED: Value write to hardware TCAM failed(ASIC: 1, Input TCAM, Address: 775, Num Entries: 1, Error: Broken pipe).2013 Oct 10 14:09:07 sw234-9250i %ACLTCAM-2-ACL_TCAM_PHY_TCAM_WRITE_FAILED: Value write to hardware TCAM failed(ASIC: 2, Input TCAM, Address: 609, Num Entries: 1, Error: Broken pipe).%ETH-QOS-2-QOSMGR_DCBXP_PFC_CMP_FAIL_MSG: Ethernet1/37 - qos config 'Priority-flow-control' not compatible with the peer
Workaround: If there are multiple fabric modules in the chassis, reload each fabric module one after the other. For example, reload the fabric module 1, wait for the module to complete the reload process, wait for 2 to 3 minutes and then reload the next fabric module. You must not reload all fabric modules at the same time. After reloading all fabric modules, clear the diagnostic result using the diagnostic clear result module command.
Condition: This situation occurs when Ethernet SPAN is configured on a Fibre Channel node of an MDS 9000 Series switch and the corresponding FCoE node is receiving traffic from the Fibre Channel node.
Condition: If the congestion timeout value is set to 100 ms for edge ports on the Cisco MDS 9710 Director with the Cisco MDS 48-Port 10-Gigabit Fibre Channel over Ethernet module, it causes the FCoE ISL to flap continuously.
Further Problem Description: Copying an image to bootflash causes more IDE interrupts, and the CPU processes the interrupts and does not give control to other USDs to communicate with the watchdog, and this issue causes the USD to crash.
Condition: This situation occurs if at least one of the switches in the fabric has the FCNS bulk notification feature enabled or if the DMM-specific Initiator or Target are moved to a switch that has the FCNS bulk notification feature enabled.
Symptom: After a switch upgrade to NX-OS 6.2(1) or later, a previously working AAA authenticated user who is configured for non network-operator privileges (such as network-admin) only receives network-operator privileges. This user is no longer able to configure the switch via CLI or SNMP.
Assign this policy conditionally on the requesting RADIUS client IP address (that is, a Cisco MDS switch mgmt0 IP address). Continue to use the original policy with the old format for RADIUS authentication requests from switches running NX-OS earlier than 6.2(1).
If the RADIUS server does not support conditional assignment of policies by RADIUS client IP address then an alternate method is possible. Create a local user on the switch with local role assignment which will override the remotely supplied role using the following commands:
Workaround: Use the fcs start-discovery command and then use the show topology and show fcs ie command to display the topology details including the switch name, management interface address, and vendor name.
Symptom: After an In Service Software Upgrade (ISSU), In Service Software Downgrade (ISSD), or supervisor switchover, devices fail to FLOGI into the switch, and the following error is logged in the syslog:
1. The Max flogi key is greater than 65535. The key can get this high if there are repeated FLOGIs on an interface. After the key exceeds 65535, this issue occurs. However, this situation does not impact end devices.
2. If a supervisor switchover, such as ISSU, ISSD, or system switchover occurs when the key is greater than 65535, Fibre Channel Identifiers (FC IDs) can be dropped from the FLOGI table. The end devices continue to function normally until they are logged out and then attempt to relogin.
If the Max flogi key value is greater than 65535 before any supervisor switchover, ISSU, or ISSD, use the shutdown and then no shutdown command on the interface. Consequently, the Max flogi key value must be checked before any supervisor switchover. However, if the supervisor switchover has already occurred and logging in are failing, you must follow either of these steps:
More Information: For detailed information about this issue, see the General Upgrading Guidelines.
%PORT-5-IF_DOWN_LINK_FAILURE: %$VSAN 1%$ Interface fc1/1 is down (Link failure Link Reset failed nonempty recv queue) port-channel11.
Also applies to earlier NX-OS 6.2 releases if there was an In Service Software Downgrade from NX-OS 6.2(7) to that earlier release. In that case, credit monitoring will remain disabled until the device re-logs in.%DIAG_PORT_LB-2-INT_PORT_LOOPBACK_TEST_FAIL: Module:1 Test:Internal PortLoopback failed 10 consecutive times. Faulty module: affected ports:affected ports:30 Error:Loopback test failed. Packets lost on the SUP in the transmit direction
- Cisco MDS 9710 Director Hardware Installation Guide
- Cisco MDS 9500 Series Hardware Installation Guide
- Cisco MDS 9500 Series Supervisor-2A Tech Note
- Cisco MDS 9250i Multiservice Switch Installation Guide
- Cisco MDS 9200 Series Hardware Installation Guide
- Cisco MDS 9100 Series Hardware Installation Guide
- Cisco MDS 9000 Family NX-OS Licensing Guide
- Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide
- Cisco MDS 9000 Family NX-OS System Management Configuration Guide
- Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
- Cisco MDS 9000 Family NX-OS Fabric Configuration Guide
- Cisco MDS 9000 Family NX-OS Quality of Service Configuration Guide
- Cisco MDS 9000 Family NX-OS Security Configuration Guide
- Cisco MDS 9000 Family NX-OS IP Services Configuration Guide
- Cisco MDS 9000 Family NX-OS Intelligent Storage Services Configuration Guide
- Cisco MDS 9000 Family NX-OS High Availability and Redundancy Configuration Guide
- Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide
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:
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 “Obtaining Documentation and Submitting a Service Request” 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)