Cisco MDS 9000 Series Release Notes for Cisco MDS NX-OS Release 6.2( 9a)
MDS 9000 Chassis and Module Support
Determining the Software Version
Determining Software Version Compatibility
Selecting the Software Image for an MDS 9148 Switch
Selecting the Software Image for an MDS 9148S Switch
Selecting the Software Image for an MDS 9222i Switch
Selecting the Software Image for an MDS 9250i Switch
Selecting the Software Image for an MDS 9500 Series Switch
Selecting the Software Image for an MDS 9700 Series Switch
Upgrading Your Cisco MDS NX-OS Software Image
FICON Supported Releases and Upgrade Paths
Downgrading Your Cisco MDS SAN-OS Software Image
General Downgrading Guidelines
New Hardware in Cisco MDS NX-OS Release 6.2(9a)
New Software Features in Cisco NX-OS Release 6.2(9a)
New Hardware in Cisco MDS NX-OS Release 6.2(9)
Cisco MDS 9148S Multilayer Fabric Switch
New Software Features in Cisco NX-OS Release 6.2(9)
New Hardware in Cisco MDS NX-OS Release 6.2(7)
Cisco MDS 48-Port 10-Gigabit Fibre Channel over Ethernet Module Ethernet Module
New Software Features in Cisco NX-OS Release 6.2(7)
New Hardware in Cisco MDS NX-OS Release 6.2(5)
Cisco MDS 9250i Multiservice Fabric Switch
New Software Features in Cisco NX-OS Release 6.2(5)
New Software Features in Cisco NX-OS Release 6.2(3)
New Hardware in Cisco MDS NX-OS Release 6.2(1)
Cisco MDS 9000 48-Port, 16-Gbps Fibre Channel Switching Module
New Software Features in Cisco NX-OS Release 6.2(1)
Licensed Cisco NX-OS Software Packages
On-Demand Port Activation License
Deprecated and Changed Features
ASCII File Can Be Copied to the Startup Configuration
Fibre Channel Security Protocol (FC-SP) Support
Install Module Command Changes
IOA Scaling Support on Supervisor-2 Module
Regulatory Compliance and Safety Information
Software Installation and Upgrade
Cisco NX-OS Configuration Guides
Intelligent Storage Networking Services Configuration Guides
Obtaining Documentation and Submitting a Service Request
Release Date: October 15, 2014
This document describes the caveats and limitations for switches in the Cisco MDS 9000 Series. 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 Series 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.
Added open caveat CSCvs57660. |
||
Added open caveat CSCuv76123. |
This document includes the following:
The Cisco MDS 9000 Series 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 Series 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 Series.
Table 3 lists the part numbers and optical components supported by the Cisco MDS 9000 Series.
Note For the latest information about supported transceivers (SFPs), see the Cisco MDS 9000 Family Pluggable Transceivers data sheet.
Table 4 lists the MDS hardware chassis supported by Cisco MDS NX-OS Release 6.2 9a.
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.
Yes4 |
||||
Yes5 |
||||
4/44-port Host Optimized 8-Gbps Fibre Channel Switching Module |
||||
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:
To determine the version of Cisco MDS NX-OS or SAN-OS software currently running on a Cisco MDS 9000 Series 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 Series 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 8 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 Series 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 9700 Directors, Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules.
To download the latest Cisco MDS NX-OS software, access the Software Center at this URL:
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm
See the following sections in this release notes for details on how you can nondisruptively upgrade your Cisco MDS 9000 switch. Using 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 show incompatibility system bootflash:system image filename command determines which additional features need to be disabled.
Note If you would like to request a copy of the source code under the terms of either GPL or LGPL, please send an e-mail to mds-software-disclosure@cisco.com.
The system and kickstart image that you use for an MDS 9148 switch is shown in Table 9 .
The system and kickstart image that you use for an MDS 9148S switch is shown in Table 9 .
The system and kickstart image that you use for an MDS 9222i switch is shown in Table 11 .
The system and kickstart image that you use for an MDS 9250i switch is shown in Table 12 .
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 13 . Cisco NX-OS Release 6.x, Release 5.x, and Release 4.x do not support the Supervisor-1 module.
Use the show module command to display the type of supervisor module in the switch. The following is sample output from the show module command on a Supervisor-2 module:
The system and kickstart image that you use for an MDS 9700 Series switch is shown in Table 14 .
No payload encryption (NPE) images are available with Cisco MDS NX-OS Release 6.2(9a) software. The NPE images are intended for countries who have import restrictions on products that encrypt payload data.
To differentiate an NPE image from the standard software image, the letters npe are included in the image name as follows:
When downloading software, ensure that you select the correct software images for you Cisco MDS 9000 Series switch. Nondisruptive software upgrades or downgrades between NPE images and non-NPE images are not supported.
This section lists the guidelines recommended for upgrading your Cisco MDS NX-OS software image and includes the following topics:
Note Before you begin the upgrade process, review the list of chassis and modules that Cisco MDS NX-OS Release 6.2(9a) supports. See the “MDS 9000 Chassis and Module Support” section.
For detailed instructions for performing a software upgrade using Cisco DCNM, see the Cisco DCNM Release Notes, Release 6.2, which is available from the following website:
http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-data-center-network-manager/products-release-notes-list.html
Follow these general guidelines before performing a software upgrade:
– Fibre Channel Ports : Fibre Channel ports can be nondisruptively upgraded without affecting traffic on the ports. See Table 15 for the nondisruptive upgrade path for all NX-OS and SAN-OS releases.
– Gigabit Ethernet/IPStorage Ports : Traffic on Gigabit Ethernet/IPStorage ports is disrupted during an upgrade or downgrade. This includes the Gigabit Ethernet/IPStorage ports on the MSM-18/4 module, SSN-16 module, 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/IPStorage 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.
– FCoE Ports: Upgrading to Cisco MDS NX-OS Release 6.2(9a) on a Cisco MDS 9700 Series Director with 48-port 10-Gigabit FCoE module or VSAN configurations require additional steps that must be performed before upgrading. For more information, see the Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide, Release 6.2(x).
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 15 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 6.2(9a). 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 15 applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and intelligent services traffic.
Cisco MDS NX-OS Release 6.2(9a) is not a FICON-certified release.
Table 16 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 17 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.
This section lists the guidelines recommended for downgrading your Cisco MDS SAN-OS software image and includes the following topics:
Follow these general guidelines before you perform a software downgrade:
– Fibre Channel Ports : Fibre Channel ports can be nondisruptively downgraded without affecting traffic on the ports. See Table 18 for the nondisruptive downgrade path for all SAN-OS releases.
– Gigabit Ethernet/ IPStorage Ports : Traffic on Gigabit Ethernet/IPStorage ports is disrupted during a downgrade. This includes the Gigabit Ethernet/IPStorage ports on the MSM-18/4 module, the MDS 9222i switch, and the MDS 9000 16-Port Storage Services Node (SSN-16). 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/IPStorage 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.
– FCoE Ports: Downgrading from Cisco MDS NX-OS Release 6.2(9a) on a Cisco MDS 9700 Series Director with 48-port 10-Gigabit FCoE module or VSAN configurations require additional steps that must be performed before downgrading. For more information, see the Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide, Release 6.2(x).
Use Table 18 to determine the nondisruptive downgrade path from Cisco NX-OS Release 6.2(9a). 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 18 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(9a) to Cisco MDS NX-OS Release 6.2(5a), 6.2(5), 6.2(3), or 6.2(1) on a Cisco MDS 9700 Series Director with 48-port 10-Gigabit FCoE module or VSAN configurations require additional steps that must be performed before downgrading. For more information, see the Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide, Release 6.2(x).
Table 19 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.
There is no new hardware introduced in Cisco NX-OS Release 6.2(9a).
Cisco MDS NX-OS Release 6.2(9a) is a maintenance release that includes bug fixes. It does not include new features.
This section briefly describes the new hardware introduced in Cisco NX-OS Release 6.2(9).
The Cisco MDS 9706 (DS-C9706) supports up to 192 ports in a 6-slot modular chassis, with up to 768 ports in a single rack. You can configure ports as Fibre Channel (2/4/8-Gbps, 4/8/16-Gbps, or 10-Gbps), FCoE (10-Gbps), or a mix of both Fibre Channel and FCoE. The Cisco MDS 9706 supports the same Fibre Channel and FCoE switching modules as the Cisco MDS 9710 director for a high degree of system commonality.
For detailed information about the Cisco MDS 9706 Director, see the Cisco MDS 9700 Series Hardware Installation Guide: http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-software/products-installation-guides-list.html
The Cisco MDS 9148S Multilayer Fabric Switch (DS-C9148S48PK9) is the next generation of the highly reliable and flexible Cisco MDS 9100 Series switches. It combines high performance with exceptional flexibility and cost-effectiveness. A powerful compact one rack-unit (1RU) form factor can scale from 12 to 48 line-rate 16 Gbps Fibre Channel ports.
For detailed information about the Cisco MDS 9148S Multilayer Fabric Switch, see the Cisco MDS 9148S Hardware Installation Guide: http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-software/products-installation-guides-list.html
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(9).
– device-alias confirm-commit (new)
– fc-management database vsan (new)
– priority-flow-control long-distance (changed) (new)
– show fc-management database (new)
– show process creditmon credit-loss-events (changed) (new)
– show process creditmon slowport-monitor-events (new)
– show tech-support fc-management (new)
– system timeout slowport-monitor mode E/F (new)
– show logging onboard slowport-monitor-events (new)
– system timeout no-credit-drop (changed) (new)
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: http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-software/products-installation-guides-list.html
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.
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(7).
– switchport max-npiv-limit (new)
– switchport trunk-max-npiv-limit (new)
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:
http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-software/products-installation-guides-list.html
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 is an ideal solution for local office and remote branch-office SANs and also in large-scale SANs operating the Cisco MDS 9700 and 9500 Series Multilayer director platforms.
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.
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(5).
– Changed the CLI output for the show ioa cluster flows command.
– Introduced the ioa-ping command.
– Introduced the ability to display IOA engine utilization.
– Introduced the ability to display hosts and targets by device alias in IOA.
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(3).
– Changed the CLI output for the show fcdomain vsan command.
– Deprecated the show interface counters performance command.
This section briefly describes the new hardware introduced in Cisco NX-OS Release 6.2(1). For detailed information about the new hardware, see the Cisco MDS 9710 Hardware Installation Guide that is available from this URL:
http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-software/products-installation-guides-list.html
This section includes the following topics:
The Cisco MDS 9710 Director is a high-performance SAN switch that is designed to meet the requirements of enterprise data center storage environments. The Cisco MDS 9710 Director has a ten-slot chassis that supports up to eight 48-port, 16-Gbps switching modules, two supervisor modules, up to six fabric modules, three fan trays, and up to eight power supplies. Airflow is front-to-back in the Cisco MDS 9710 chassis.
Up to eight Cisco MDS 9000 48-Port 16-Gbps Fibre Channel switching modules can be used in the Cisco MDS 9710 Director. These modules are hot-swappable and compatible with 2-, 4-, 8-, 16- and 10-Gbps interfaces, and they support hot-swappable Enhanced Small Form-Factor Pluggable (SFP+) transceivers.
The Fibre Channel switching module has 12 4-port port groups. Each port group is capable of a speed of 64-Gbps in each direction simultaneously. Ports on this switching module support expansion port (E port), fabric port (F port), fabric loop port (FL port), SPAN destination port (SD port), and (TE port) port mode.
– Individual ports can be configured with Cisco 16-Gbps,8-Gbps or 10-Gbps shortwave or longwave SFP+ transceivers. Each port supports 500 buffer credits with no additional licensing required. With the Cisco Enterprise Package, up to 4095 buffer credits can be allocated to an individual port.
This section briefly describes the new software features introduced in Cisco NX-OS Release 6.2(1).
Starting with Cisco NX-OS Release 6.2(1), the Cisco MDS 9000 Series 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.
For more information about this feature, see the Cisco MDS 9000 System Management Configuration Guide at this URL:
http://www.cisco.com/en/US/products/ps5989/products_installation_and_configuration_guides_list.html
For more information about this feature, see the Cisco MDS 9000 Security Configuration Guide, at this URL:
http://www.cisco.com/en/US/products/ps5989/products_installation_and_configuration_guides_list.html
– Enhance the clear snmp counters command.
– Display ISL related information.
– Display a warning messages for a shared port interface when you bring down the port.
– Display throughput information for all ports on a line card or ISL or on a switch or chassis.
– Provide an estimated time for DMM job completion.
– Shorten the show dmm job job-id 50571379 session session_id (1-20) command to show dmm job-id 50571379 session_id 1
– hardware ejector enable (new)
Information about the modified CLI commands can be found in the Cisco MDS 9000 Command Reference at this URL:
http://www.cisco.com/en/US/products/ps5989/prod_command_reference_list.html
Most Cisco MDS 9000 Series 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, Cisco MDS 9148S 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).
Additional information about licensed Cisco NX-OS software packages is available at this URL:
http://www.cisco.com/c/en/us/products/storage-networking/mds-9000-software-licensing/datasheet-listing.html
The standard software package that is bundled at no charge with the Cisco MDS 9000 Series switches includes the base set of features that Cisco believes are required by most customers for building a SAN. The Cisco MDS 9000 Series 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 Series 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 Series 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 9148S 48-Port Multilayer 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.
LUN zoning, read-only zones, and broadcast zones are no longer supported. These features affect the following hardware:
You cannot bring up these modules if these features are already configured. You should completely remove all configurations that include these features before you attempt to bring up these modules. In addition, you cannot configure these features after you bring up these modules.
In addition, the following software features are not supported or are changed in Cisco MDS NX-OS Release 6.2(9a):
Note OHMS is supported on Cisco MDS 9500 Series directors, Cisco MDS 9250i Multiservice Fabric Switch, Cisco MDS 9148S Multilayer Fabric Switch, and Cisco MDS 9148 Multilayer Fabric Switch.
Cisco NX-OS Release 6.2 does not support the following hardware:
This section lists the limitations and restrictions. The following limitations are described:
The copy bootflash:runnig-config.ascii startup-config command that was deprecated in an earlier Cisco NX-OS release is enabled from Cisco NX-OS Release 6.2(1).
From Cisco NX-OS Release 6.2(9) onwards, the FC-SP feature is supported on Cisco MDS 9700 Series.
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.
The install module module-number bios command continues to be supported in Cisco NX-OS Release 6.2(1) on Cisco MDS 9500 Series switches.
This section lists the open and resolved caveats for this release. Use Table 20 to determine the status of a particular caveat. In the table, “O” indicates an open caveat and “R” indicates a resolved caveat.
Symptom : The following Cisco products:
MDS 8 Gbps Fabric Switch for HP c-Class Blade System
MDS 4 Gbps Fabric Switch for HP c-Class BladeSystem
MDS 4 Gbps Fabric Switch for IBM BladeCenter
include a version of bash that is affected by the vulnerabilities identified by the Common Vulnerability and Exposures (CVE) IDs:
This bug has been opened to address the potential impact on this product.
Condition : Exposure is configuration dependent based on the following configuration commands:
This vulnerability may only be exploited by authenticated users.
Workaround : This issue is resolved.
Symptom: Creditmon crashes while collecting show tech-support on the Cisco MDS 9250i Multiservice switch. The following message is logged in the syslog:
Condition: This situation occurs after an In-Service Software Upgrade (ISSU) from 6.2.5 or 6.2.7 to 6.2.9.
Workaround: This issue is resolved.
Symptom : The Cisco MDS 9250i Multiservice switch does not generate the full core dump for IPS module crash.
Condition: The switch is running 6.2(9) after an In-Service Software Upgrade (ISSU) from 6.2(7).
Workaround : This issue is resolved.
Symptom: User cannot get the stack trace from the cores generated from FCIP processor on the Cisco MDS 9250i Multiservice switch.
Condition: The core daemon detects a false FCIP engine crash and starts collecting the core dump.
Workaround: This issue is resolved.
Symptom: FCIP flaps due to keep alive timeout error message. The following message is logged in the syslog:
Condition: If there is no traffic for 60 secs in the TCP session, TCP sends one probe every second. If 8 probes are not responded from the peer switch, the FCIP tunnel flaps because of the keep alive timer expiry.
Workaround: This issue is resolved.
Symptom : The RSCN or ZONE service crashes with the following syslog message:
A Cisco MDS 9700 switch can incur a switchover, however in most cases, the crash occurs again before the standby is available and the dual supervisor switch will reload.
Condition : This issue occurs only when "port" format RSCNs are configured and an RSCN is sent on the relevant VSAN. RSCNs are sent, for example, after activating zoneset changes or a link changing state. Further, only the following platforms are affected:
This issue does not occur when RSCNs are sent with "fabric" format.
Workaround : Use the default RSCN address format by removing the following lines from the switch configuration:
no zone rscn address-format port vsan
Note that some end devices may not support receiving RSCNs in this format.
Further Problem Description: This wrong data is constructed by the zone server. It can corrupt its own heap while creating the payload to put into MTS.
The crash can be either in the zone server or RSCN. It is just which module runs into the issue first. The fix that went in is to prevent both.
Symptom: An operational FCIP tunnel resets randomly. The following types of messages are logged in the syslog:
Condition: This situation occurs on Cisco MDS 9250i only when IP compression is enabled on an FCIP tunnel and data is transmitted from the port. This impacts all the IP compression modes.
Workaround: This issue is resolved.
Symptom: The FCNS process aborts.
Condition: When an internal message sending fails for any reason, FCNS process crashes.
Symptom : In case of multiple ISL connected to the switch having the host and in the same transit VSAN, after deactivating the IVR zoneset the entires are removed from the host interface. However, the entires are removed only from one ISL connected between the two switches. This creates stale entries for the transit VSAN on the switch.
Condition: This issue occurs when all the following conditions are met:
1. Switch is either Cisco MDS 9250i Multiservice switch, MDS 9148s switch or MDS 9148 switch on which the host is connected.
2. Switch has multiple ISL or port channel connected to it and they all belong to the same VSAN.
Workaround : Group multiple VSAN ISL links together in a single port channel link. Do not have any combination of ISL or port channel in same VSAN connected to the switch on which the host is connected.
Symptom: The Storage Media Encryption (SME) cluster creation fails and the following error message appears:
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.
Workaround : Following the ISSU, enter the feature lldp command on the switch to make the LLDP commands available on the switch.
Symptom: The Address Resolution Protocol (ARP) process fails for IP over Fibre Channel (IPFC).
Condition: This issue occurs when the Cisco MDS 9000 switches are connected through virtual Fibre Channel (vFC) interfaces.
Symptom The Cisco MDS 9710 Director does not allow a copy running saving configuration and a switch reload operation.
Condition: If active Fibre Channel Redirect (FC-Redirect) configurations are present in Cisco MDS 9710 Director.
Workaround : Remove the Cisco MDS 9710 Director from the fabric.
Symptom: The Cisco MDS 9250i switch incorrectly displays that the Ternary Content Addressable Memory (TCAM) is full even if enough memory is available.
Condition: This situation occurs if the IOA flows go into the security region and some TCAM entries are deleted or added.
Symptom: Traffic between two Cisco MDS 9250i switches might stop when the write acceleration feature is enabled during traffic flow.
Condition: This situation occurs if there are more than 11 tunnels.
Workaround: Disable the write acceleration feature on all of the tunnels or move all tunnels to a PortChannel.
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.
Workaround: Use the 6e template throughout the fabric so that the control and data traffic are placed in different queues and do not impact each other.
Symptom: Tape acceleration cannot be enabled on the Cisco MDS 9250i switch if the Transmission Control Protocol (TCP) connections are set to 5.
Condition: The tcp-connections command is used to set the TCP connection to 5.
Workaround: Set TCP connections to 2.
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:
Condition: This situation occurs with specific SFPs during removal and reinsertion.
Workaround: Avoid quickly removing and inserting an SFP. After removing an SFP, wait for few seconds before reinserting it.
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 go down.
Condition: This situation occurs if an ISSU or ISSD is simultaneously performed on Cisco MDS 9250i switches that are interconnected.
Workaround: Perform an ISSU or ISSD in a progressive method. For example, after the upgrade or downgrade completes on one switch, move on to another.
Symptom: When an In-Service Software Upgrade (ISSU) is performed on a Cisco MDS 9250i switch with approximately 200 IOA Disk flows, the following syslog is displayed:
Condition: This situation occurs is an ISSU was performed on a Cisco MDS 9250i switch with more than 180 I/O Accelerator (IOA) disk flows.
Workaround: On the Cisco MDS 9250i switch, limit the number of IOA disk flows to 180 during an ISSU.
More information: The Cisco MDS 9250i switch supports up to 180 disk flows.
Symptom: If both the Fibre Channel and Fibre Channel over Ethernet (FCoE) links with the same equal-cost multipath (ECMP) entries) between two switches, traffic does not flow.
Workaround: VLAN-VSAN mapping should be numerically identical when ECMPs exist with a mix of FC and FCoE paths. For example, map VSAN 10 to VLAN 10, VSAN 11 to VLAN 11, and so on.
Symptom: fctrace does not work on the Cisco MDS 48-Port 10-Gigabit Fibre Channel over Ethernet (FCoE)
Workaround: Use Path Trace to trace the path between two domains or a domain and an end device.
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.
Symptom: FC-SP ESP configurations cannot be applied if a PortChannel is created on a link-level encrypted ISL by using either the DCNM PortChannel wizard or CLI.
Workaround: Reconfigure FC-SP ESP on the PortChannel interface manually. Apply FC-SP ESP configurations on a PortChannel only after creating the PortChannel successfully.
More Information: If the PortChannel is created using the DCNM PortChannel wizard, you can use the FC-SP ESP wizard for the reconfiguration.
Symptom: The link-level encrypted ISL on a Cisco MDS 9500 switch fails to come online if the PortChannel creation using either DCNM or CLI fails.
Condition: The PortChannel creation fails because the compatibility check fails due to unavailability of resource.
Workaround: Apply the FC-SP ESP configurations on a PortChannel only after creating the PortChannel successfully.
Symptom: If a device-alias commit fails because of the validation failure of an application such as IVR, zone, dpvm, psm, the show device-alias session status command displays the following error:
Condition: This situation occurs if one of the following conditions is met:
– Application validation failure is seen when the time taken by the application to validate the device-alias pending changes with the database of the application exceeds the validation timeout.
– Application validation failure occurs when the device-alias pending-diff is huge and/or when the application database size is larger.
Workaround: Reduce the set of device-alias commands entered within a device-alias session, if the device-alias commit has failed because a validation failure.
Symptom: Specifying an fcanalyzer display-flter while writing a trace file is now not supported. The following message appears:
Condition: Occurs whenever attempting to use the fcanalyzer to capture Fibre Channel traffic.
Symptom: Host cannot access storage across an fcip link.
Condition: Under very rare circumstances and system default switchport mode f is configured and the fcip interface is left in the default switchport mode auto.
Workaround: Configure the fcip interface as
If the fcip interfaces will be placed in a port-channel, then also configure the port-channel as:
Symptom: A Cisco MDS 9250i switch may spontaneously reload.
Condition: The trigger is not known since the issue does not leave any information in the persistent logs.
Further Problem Description: This issue has been reported by a very small number of customers.
Please refer to CSCun24379 if these symptoms occur on an MDS 9250i switch running an NX-OS release before NX-OS 6.2(9).
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
Condition: This issue might occur when the supervisor module is unusually busy and cannot process the mount request from the MSM-18/4 module, or the actual mount command on the supervisor takes a long time.
Workaround : Reload the MSM-18/4 module in the same slot/module where the modflash mount failed. A request will be sent to the supervisor to mount the modflash.
Symptom: On Cisco MDS 9250i and MDS 9148S, the slow port statistics do not show oper delay value properly.
Condition: When the R_RDY delay in the traffic tester port is configured to a value that causes timeout drops in the switch port and the slow port monitor timeout feature is configured in the switch.
Symptom: Two end devices cannot communicate with a device it is zoned with. The situation issue occurs intermittently.
Condition: This issue occurs in all Cisco MDS NX-OS releases on MDS 9222i, 9506, 9509, 9513 and 9710 switches only. This issue also applies only on an F_port when the port mode is configured or defaulted to auto.
Because the default port mode on the Cisco MDS 2-, 4-, 8-, 10-, and 16-Gbps Advanced FC Module DS-X9448-768K9 is auto, this problem may be seen more frequently on the MDS 9710 platform with this switching module.
Workaround: Configure the port mode as fx instead of auto and shut and no shut the port by using the following commands:
Symptom: On a Cisco MDS 9710 Director, DS-X9448-768K9 ports might fail a loopback test and put the ports in that port group into a hwfailure state. The error message is logged in the syslog:
Condition: This situation might occur during a normal operation.
Workaround: You must reload the affected DS-X9448-768K9 module to recover the failed ports.
Symptom: An IVR VSAN topology must be configured to manual mode to avoid any traffic loss when multiple switches VSANs are involved during the ISSU and ISSD operations.
Condition: When the VSANs that are a part of the IVR zone on a Cisco MDS 9250i or MDS 9148S.
Workaround: Convert the IVR VSAN topology auto mode to manual mode by using the following commands:
– ivr copy auto-topology user-configured-topology
Symptom: If you connect one NPV switch to another NPV switch, the ports do not come online and you cannot see the logins on the lower NPV switch.
Condition: This situation occurs when an NPV switch is connected to another NPV switch.
Symptom: Configuring RSPAN for the sup-fc0 traffic with the Cisco MDS 9700 Series as the source results in packets looping.
Condition: This issue occurs only on the Cisco MDS 9700 Series if sup-fc0 is configured as an RSPAN source.
Workaround: Use the local span for checking sup-fc0 frames.
Symptom: On Cisco MDS 9250i switch, an active DMM server base method 2 job goes to the RESET state instead of the FAILED state.
Condition: The issue occurs when the host port flaps.
Workaround: Disable the bulk notification feature on all the switches by using the fcns no-bulk-notify command. To check the status of the bulk notification feature, use the show fcns internal info global command.
More information: In Cisco MDS NX-OS Release 6.2(9a), the bulk notification feature is enabled by default.
Symptom: On Cisco MDS 9000 switches, on mgmt0 interface, certain TCP ports from 600 to 1000 are open.
Workaround: To close the open ports, configure an IP access list as shown in the following example:
Symptom: On Cisco MDS 9000 switches, on mgmt0 interface, TCP port 2002 is open.
Condition: This issue affects Cisco MDS 9500 Series, 9200 Series, and 9100 Series only.
Workaround: To close the open TCP port, configure an IP access list as shown in the example:
Symptom: On Cisco MDS 9000 switches, on mgmt0 interface, TCP ports 32768 and 32769 might be open.
Condition: This issue affects Cisco MDS 9500 Series, 9200 Series, and 9100 Series only.
Workaround: To close the open TCP port, configure an IP access list as shown in the example:
Symptom: When using the fcanalyzer with the write option, it displays all trace data being written to file to the console or session. This causes the fcanalyzer to take a very long time to capture any meaningful data.
Condition: This situation occurs in Cisco MDS NX-OS 6.2(7) when using fcanalyzer to write out a pcap trace file.
Symptom: On a Cisco MDS 9000 switch, certain TCP ports from 600 to 1000 are open on the mgmt0 interface.
Condition: This situation occurs during normal operation.
Workaround: If these ports need to be closed, configure an IP access list. The following example shows how to configure an IP access list:
Symptom: The DCBX local information shows LLS DCBX registration when the port is in the shut state as:
Note All the other DCBX features are usually preregistered on a down port and not seen in the DCBX output. LLS is not deregistered on a shut port, and keeps appearing in the output.
Condition: This situation occurs when the port is in the shut state.
Symptom: On Cisco MDS 9700 48-Port 16-Gbps Fibre Channel Switching module (DS-X9448-768K9), after a switchover, the port number 48 flaps and then comes online.
Condition: The last port group, from port 41 to 48 was configured as 10-G port.
Workaround: Avoid configuring 10-G speed on ports from 41 to 48 on the 48-Port 16-Gbps Fibre Channel Switching module.
Symptom: A user with the priv-14 role does not inherit rules from the priv-0 through priv-13 roles.
Condition: This situation occurs during a normal operation.
Workaround: Create users with roles from priv-0 to priv-13 and log in, or log in to the switch using AAA authentication where users with certain user levels are identified.
Symptom: While configuring the SNMP server, if you configure a host name instead of an IP address, the following error appears:
Condition: If the domain name and the name server IP are configured, and if you provide the SNMP host name.
Workaround: Instead of the host name, add the IP address of the host in the SNMP configuration.
Symptom: In rare circumstances, the temperature sensor on a 18+4 module returns -1s. This can also lead to exceptions being recorded, similar to the following example:
Symptom : In a virtual SAN (VSAN), the inter-switch link (ISL) might fail after entering the suspend command, followed by the no suspend command.
Condition: This situation occurs if the no suspend command is entered after a VSAN suspend operation.
Workaround: After entering the suspend command, wait for at least 5 to 15 minutes and then use the no suspend command.
Symptom: Device-alias does not display any warnings when committing, even if the result is to overwrite an existing database with an empty one.
This can happen in a scenario where you provision a new switch and attach it to the existing fabric. The new switch might have a default config that is an empty device-alias database and device-alias is running in basic mode. When you bring up the ISL, device-alias merge fails because of the mode mismatch, log message is issued, and you might attempt to fix that by running, on the new switch with empty database:
This will push the empty database to the entire fabric and wipeout the existing one. It can lead to loss of traffic if zoning is done with device-alias members.
Workaround: Convert the new switch with an empty device-alias database to enhanced mode using the following sequence:
This triggers a device-alias merge and the new switch pick ups the existing database from the rest of the fabric.
Symptom : Maximum FCIP throughput on the MDS 9250i is limited to less than line rate for 10 Gbps interfaces.
Condition : This issue only applies to 10 Gbps FCIP interfaces on the MDS 9250i platform.
Workaround : There is no workaround.
Symptom : An FCSP-ESP enabled (encrypted) port that was working fails to come up after ISSU/ISSD followed by link flap.
Condition : This issue only affects FCSP encrypted ports on MDS 9700 DS-X9448-768K9 and MDS 9500 DS-X9248-256K9 and DS-X9232-256K9 switching modules after an ISSU or ISSD to an affected version of NX-OS.
Workaround : Only a switch reload will recover from this situation. The switch must be running a fixed release of NX-OS (NX-OS 6.2(11) or above) before the reload to prevent the issue from recurring after recovery.
Further Problem Description : The issue arises on affected version of NX-OS since these versions do not push the FCSP-ESP configuration to hardware. This results in a permanent FCSP-ESP configuration mismatch with the peer port. Hence the port will not come up.
Symptom : FCIP tunnels don't fully utilise the available TCP window size. This leads to underperforming FCIP tunnels that never achieve their configured bandwidth on higher latency links.When TCP send queue hits 2MB threshold, the FCIP tunnel is exerting flow control back to the FC ports utilizing the tunnel. This leads to Rx B2B credit depletion. You can see the current size of the send queue via the following command:
Condition : This issue applies when:
– NX-OS versions from 6.2(5) to 6.2(9c) inclusive, and
– the platform is an MDS 9500 or MDS 9222i, and
– latency on FCIP tunnel is high enough that a TCP window size greater than 2 MB is required
Workaround : Increase the number of FCIP tunnels.
Further Problem Description : The current TCP window size is displayed in the "Peer receive window" field of the show interface fcip command:
Peer receive window: Current: 4162 KB, Maximum: 4220 KB, Scale: 11
Symptom : System switchover takes too long a time [around 20 minutes] and standby gets reloaded before becoming HA-standby. Flogi process will consume 90 - 100% of CPU cycles during PSS restore and due to this, any end device activity like login and logout will not be processed by Flogi process and eventually gets timed out.
This may cause the flogi process to crash and if the standby is not in ha-standby status, the switch will reload.
Condition : The issue will happen if all of the the below conditions are met.
– The end device must have done a continuous Login - Logout [this is not a port flap but the end device doing a login flap without the port going down] to a switch running NX-OS less than 6.2.7. (or) 5.2.8e
– Max flogi key greater than the flogi bitset (See Further Problem Description below.)
– An ISSU to any version higher than NX-OS 6.2.7 or 5.2.8e from any version less than NX-OS 6.2.7 or 5.2.8e occur
– A Supervisor Switch-over happens.
Workaround : The workaround to recover - is to - identify the affected ports and flap them.
Note: Contact Cisco TAC to efficiently identify affected ports.
Further Problem Description : When there is repeated Flogi and Logo on an interface, the “Max Flogi key” count which is 16-bit will increment for every Login - Logout flap and after reaching 64k will wrap around and start from Zero. On the other hand, the “flogi bitset” count reaches 255 for every Login - Logout flap and after reaching 255 will stay put. When the “Max Flogi key” count is less than the “flogi bitset” the PSS recovery takes more time which is a bug. This issue is fixed and will not occur in Cisco MDS NX-OS Releases 6.2(7), 5.2(8e) and above - Bug CSCub40020.
If the issue has occurred in lower versions and when an ISSU to Cisco MDS Release NX-OS 6.2(7) or 5.2(8e) is done, it tries to recover the “Max flogi key”. If the recovery step ends up in Max flogi key < than flogi bitset value, the PSS recovery during further Switchover will take up more time. The time consumption of PSS recovery is directly proportional to the No. of Instances where the “Max Flogi key” is less than the “flogi bitset”
That is, in a scaled environment and when more and more ports or vsans are affected the time taken for PSS recovery is exponential.
The affected interface can be found by the following CLI:
interface fc2/5 in Vsan 1 and interface port-channel3 in Vsan 552 have Max flogi key greater than the flogi bitset [0x1(1) > 0 and 0x40(64) > 4] but interface port-channel3 in Vsan 1 has Max flogi key less than the highest flogi bitset value [0x40(64) < 255].
Symptom : Users remotely authenticated by RADIUS or TACACS+ cannot login to the system after ISSU. Also, the aaa group configuration has a deadtime greater than the maximum of 1440 minutes, for example:
Conditions : This issue only occurs for RADIUS or TACACS+ server groups.
Workaround : To recover after this issue has occurred:
1. Use a local account to login then reestablish a connection to the aaa servers with the one of the following commands:
This must be done for all server addresses in the affected group.
2. Reconfigure the deadtime of the server group to a value within the range of 0 to 1440. After the deadtime is within range, it can be removed with the no deadtime command.
To prevent this issue before an upgrade, initialise the deadtime and save the config, then remove it and save the config again. For example, for TACACS+:
Symptom : An ISL connected over a DWDM path does not reach link up state
Condition : This issue only applies to MDS 9700 DS-X9448-768K9 modules used with some DWDM vendors.
Symptom : An ISL does not initialize quickly across a DWDM connection. The link can take minutes, hours or even days to connect. Once connected, it is stable.
Condition : This issue only applies to DS-X9248-256K9 and DS-X9232-256K9 modules when connecting an ISL over a Tellabs 7100 DWDM path.
Symptom : Whenever we give the command to max-bandwidth-mbps in m9250i, although the maximum supported speed is 10Gig, it shows 1Gig as the maximum configurable bandwidth.
Condition : There is one condition when we have IPS port speed for m9250i speed set as 1Gig, then as of now, the user has to make sure he doesn't give the speed as 10Gig. Reason being it will show the 10Gig as max-bandwidth allowed even for 1Gig speed in m9250i. As of now, we don't have the intelligence in the cli to check for what speed the port speed is set to.
Hence when Port speed = 1Gig, we should give the value of max-bandwidth-mbps = 1Gig and not as 10Gig.
Workaround : There is no workaround.
Symptom : Callhome stops working and callhome tests fail.
Condition : Only destination profiles of full_txt are configured.
Workaround : To prevent from hitting this defect, configure an additional destination profile that is either short_txt or XML.
Symptom : MDS fabric switch running in NPV mode fails to generate port-monitor alerts.
Condition : Applies to all MDS fabric switches running in NPV mode using port-monitor.
Applies to all versions prior to NX-OS 6.2(13).
Will occur only in the following conditions:
- After one or more upstream NP or TNP ports goes down and then back up.
- For each (T)NP port that flaps, one F port at the end of the range of ports
will no longer be scanned for port-monitor counter events. For example, if the
(T)NP port fc1/1 flaps then the last F port being used(ex. fc1/48) will no
longer be scanned for port-monitor counter events
Workaround : There are two workarounds, one temporary and one permanent:
1 - Contact the TAC and they can assist with killing the port-monitor process. Once the port-monitor process restarts, all ports will be once again scanned.
This is only temporary in the sense that if an upstream (T)NP port flaps again the problem will recur.
2 - Move the (T)NP ports to the end of the ports on the switch. For example, if there are four (T)NP uplinks on a MDS 9148 or MDS 9148S, then move them to fc1/45-fc1/48. Once this has been done the problem will not recur.
Symptom : This issue was originally seen on a FICON enabled 9513, while attempting an ISSU from 6.2(11c) to 6.2(11e). The fcd process experienced a hap reset due to heartbeat loss, and that resulted in the ISSU being aborted.
Condition : ISSU w/ FICON enabled. Specific triggers not known at the moment.
Workaround : We have created debug plugins to clear this problem. As of now the debug plugins are available for the following.
The documentation set for the Cisco MDS 9000 Series includes the documents listed in this section. To find a document online, access the following URL:
http://www.cisco.com/en/US/products/ps5989/tsd_products_support_series_home.html
The documentation set for Cisco Prime Data Center Network Manager is available from the following URL:
http://www.cisco.com/en/US/products/ps9369/tsd_products_support_series_home.html
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.