Cisco MDS 9000 Series Release Notes, Release 8.4(2d)
Available Languages
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- US/Canada 800-553-2447
- Worldwide Support Phone Numbers
- All Tools
Feedback
Feedback
This document describes the features, issues, and deployment guidelines for the Cisco MDS NX-OS software for the use on the Cisco MDS 9000 Series Switches. Use this document in combination with documents listed in the “Obtaining Documentation and Submitting a Service Request” section.
Note: The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product.
Note: Release notes are updated on an as needed basis 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.
| Date |
Description |
| November 06, 2023 |
Added CSCvv93277 in the Resolved Caveats section. |
| October 27, 2022 |
Added CSCwb29379 in the Open Caveats section. |
| March 23, 2022 |
Added CSCwb14523 in the Open Caveats section. |
| March 22, 2022 |
Added CSCvz72463 in the Resolved Caveats section. |
| February 16, 2022 |
Initial release. |
Introduction
The Cisco MDS 9000 Series of Multilayer Directors and Fabric Switches provide best-in-class high availability, scalability, security, and management, that enables to deploy high-performance storage-area networks. Layering a rich set of intelligent features onto a high-performance switch fabric, the Cisco MDS 9000 Series has the flexibility to fit small deployments as well as to address the stringent requirements of large data center storage environments: high availability, security, scalability, ease of management, and seamless integration of new technologies.
About Software Images
The Cisco MDS NX-OS operating system is shipped with the Cisco MDS 9000 Series Switches. The Cisco MDS NX-OS software consists of two images: the kickstart image and the system image. These images can be upgraded or downgraded to different versions. The versions of both images must match for the system to boot.
Each model of Cisco MDS switch has unique kickstart and system images. For more information on the image names for each Cisco MDS switch, see the Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide, Release 8.x.
To download new Cisco MDS 9000 Series software, including Cisco MDS NX-OS and Cisco DCNM management software, go to the Storage Networking Software download website at https://software.cisco.com/download/find/MDS.
Choosing Between Cisco MDS NX-OS Open Systems Releases
Cisco uses release numbering to indicate the maturity of a Cisco MDS NX-OS release train. Cisco MDS NX-OS major versions are incremented when significant software features or hardware support are added. Because of the focus on new features and hardware, all defects may not yet have been fixed. After an initial release, minor version numbers of the train are incremented, and only security patches and defect fixes are added, providing better stability to the new features and updated security.
Details about the new features and hardware supported by Cisco MDS NX-OS Release 8.4(2d) can be found in the “New Hardware and Software Features” section. For information about other releases, refer to the Release Notes on the Cisco MDS 9000 NX-OS and SAN-OS Software documentation page.
For Cisco recommended MDS NX-OS releases for each type of hardware, see the Recommended Releases for Cisco MDS 9000 Series Switches document.
Components Supported
For information on supported software and hardware components, see the Cisco MDS 9000 Series Compatibility Matrix.
FICON
Cisco MDS NX-OS Release 8.4(2d) is not IBM FICON qualified. For more information on releases that are IBM FICON qualified, see http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-software/products-release-notes-list.html.
Upgrading Cisco MDS NX-OS Software Image
This section lists the guidelines recommended for upgrading Cisco MDS NX-OS software image and includes the following topics:
● General Upgrading Guidelines
● Open Systems Nondisruptive Upgrade Paths
For detailed instructions for performing a software upgrade using Cisco DCNM, see the Cisco DCNM Release Notes.
This section lists the general guidelines for performing a software upgrade:
● Install and configure dual supervisor modules before the upgrade.
● Issue the show install all impact upgrade-image command to determine if the upgrade will be nondisruptive.
● Some features are impacted whether an upgrade is disruptive or nondisruptive:
◦ Fibre Channel Ports: Fibre Channel ports can be nondisruptively upgraded without affecting traffic on the ports. See the “Open Systems Nondisruptive Upgrade Paths” section for all MDS NX-OS releases.
◦ Fibre Channel over Ethernet (FCoE) Ports: FCoE ports can be nondisruptively upgraded without affecting traffic on the ports. See the “Open Systems Nondisruptive Upgrade Paths” section for all MDS NX-OS releases.
◦ IP Storage (IPS) Ports: Traffic on IPS ports on Cisco MDS 9250i, and Cisco MDS 24/10-Port SAN Extension Modules is disrupted during an upgrade or downgrade. Nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration may occur. If supported, iSCSI initiators connected to the IPS ports lose connectivity to iSCSI targets while the upgrade is in progress.
Note: In addition to these guidelines, review the information in the "Limitations and Restrictions" section before a software upgrade to determine if a feature may possibly behave differently following the upgrade.
◦ To upgrade or downgrade to a Cisco MDS NX-OS release version, the same release version of the kickstart and system images in the install all command must be used.
◦ If you are upgrading Cisco MDS 9700 Series Directors from Cisco MDS NX-OS Release 8.3(1), Release 8.3(2), Release 8.4(1), or Release 8.4(1a) to Release 8.4(2) or later, ensure that you perform a switchover before upgrading. For more information, see CSCvt87216.
Open Systems Nondisruptive Upgrade Paths
The software upgrade information in this section applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and intelligent services traffic.
Table 1. Nondisruptive Upgrade Paths to Cisco MDS NX-OS Release 8.4(2d)
| Current Release |
Nondisruptive Upgrade Paths and Ordered Upgrade Steps |
| MDS NX-OS: |
|
| All 8.x releases[1] |
Upgrade directly to MDS NX-OS Release 8.4(2d) |
| All 7.3(x) releases |
Step 1. Upgrade directly to MDS NX-OS Release 8.1(1b) Step 2. Upgrade to MDS NX-OS Release 8.4(2d) |
| 6.2(29) and above releases |
Upgrade directly to MDS NX-OS Release 8.4(2d) |
| 6.2(13a) until 6.2(27) |
Step 1. Upgrade directly to MDS NX-OS Release 8.1(1b) Step 2. Upgrade to MDS NX-OS Release 8.4(2d) |
| All 6.2(x) releases prior to 6.2(13a) |
Step 1. Upgrade directly to MDS NX-OS Release 6.2(13a) Step 2. Upgrade to MDS NX-OS Release 8.1(1b) Step 3. Upgrade to MDS NX-OS Release 8.4(2d) |
Downgrading Cisco MDS NX-OS Software Image
This section lists the guidelines recommended for ISSD of Cisco MDS NX-OS software image and includes the following topics:
● General Downgrading Guidelines
● Open Systems Nondisruptive Downgrade Paths
General Downgrading Guidelines
Follow these general guidelines before performing a software downgrade:
● Disable all features that are not supported by the downgrade release. Use the show incompatibility system downgrade-image command to determine the features that needs to be disabled.
● Use the show install all impact downgrade-image command to determine if the downgrade is nondisruptive.
● The following features are impacted during a downgrade, whether it is a nondisruptive downgrade or a disruptive downgrade:
◦ Fibre Channel Ports: Fibre Channel ports can be nondisruptively downgraded without affecting traffic on the ports. See the “Open Systems Nondisruptive Downgrade Paths” section for all MDS NX-OS releases.
◦ Fibre Channel over Ethernet (FCoE) Ports: FCoE ports can be nondisruptively downgraded without affecting traffic on the ports. See the “Open Systems Nondisruptive Downgrade Paths” section for all MDS NX-OS releases.
◦ FCoE Ports: FCoE ports can be nondisruptively downgraded without affecting traffic on the ports.
◦ IPS Ports: Traffic on IPS ports on Cisco MDS 9250i, and Cisco MDS 24/10-Port SAN Extension Modules is disrupted during an upgrade or downgrade. Nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration may occur. If supported, iSCSI initiators connected to the IPS ports lose connectivity to iSCSI targets while the upgrade is in progress.
Find the MDS NX-OS image that you want to downgrade to in the Target Release column of the Table 2 and follow the steps in the order specified to perform the downgrade.
Note: The software downgrade information in the below tables applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP and intelligent services traffic.
● Any hardware that is not supported by the downgrade release version will be powered down when the downgrade release starts running. Power off and or remove any unsupported components before downgrading. For more information about supported hardware see the Cisco MDS 9000 Series Compatibility Matrix.
● If you are downgrading to Cisco MDS NX-OS Release 8.1(x), Release 8.2(x), Release 8.3(x), or Release 8.4(1x) from Release 8.4(2x) and if smart license and VSAN policy for a role are configured, ensure that you disable Smart Licensing or disable VSAN policy for only the role before downgrading or performing a switchover. You can reenable these features after downgrading or performing the switchover. For more information, see CSCvy19014.
● If you are downgrading from Cisco MDS NX-OS Release 9.2(1) or later releases to a release prior to Cisco MDS NX-OS Release 9.2(1), ensure that you use the clear logging onboard txwait command after downgrading. Otherwise, logging to the OBFL TxWait file may cease with an error. For more information, see the Cisco MDS 9000 Series Interfaces Configuration Guide, Release 9.x.
ISSD Guidelines for Cisco MDS 9396S Switch
● Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(0)D1(1) or Cisco MDS NX-OS Release 6.2(13a) is not supported on a Cisco MDS 9396S Switch which has DS-CAC-1200W as a power supply unit (PSU) and DS-C96S-FAN-I as port side intake fan tray.
● Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 6.2(13) is not supported on the Cisco MDS 9396S Multilayer Fabric Switch. The minimum recommended image for Cisco MDS 9396S Multilayer Fabric Switch is 6.2(13a).
ISSD Guidelines for Cisco MDS 9250i Switch
● Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(0)D1(1), or 6.2(13a) and lower is not supported on a Cisco MDS 9250i Switch which has only one online PSU.
● Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(0)D1(1), or 6.2(13a) and lower on a Cisco MDS 9250i Switch with two online PSUs results in loss of N:N grid redundancy. The switch will run in non-redundant mode.
● Downgrading from Cisco MDS NX-OS Release 8.x to Cisco MDS NX-OS Release 7.3(0)D1(1), or 6.2(13a) and lower on a Cisco MDS 9250i Switch with three online PSUs results in loss of N:N grid redundancy. The switch will run in N+1 power redundant mode.
Open Systems Nondisruptive Downgrade Paths
● Downgrading directly from Cisco MDS NX-OS Release 8.1(1) and Release 8.1(1b) to releases before Cisco MDS NX-OS Release 6.2(9) is not supported. In such a scenario, we recommend that you first downgrade to Cisco MDS NX-OS Release 6.2(13a) or higher and then downgrade to the required release.
● Downgrading directly from Cisco MDS NX-OS Release 8.1(1) to Cisco MDS NX-OS Release 7.3(0)DY(1) is not supported. In such a scenario, we recommend that you first downgrade to Cisco MDS NX-OS Release 7.3(0)D1(1) and then upgrade to 7.3(0)DY(1).
● Downgrading directly from Cisco MDS NX-OS Release 8.1(1) to Cisco MDS NX-OS Release 7.3(1)DY(1) is not supported. In such a scenario, we recommend that you first downgrade to Cisco MDS NX-OS Release 7.3(0)D1(1) and then upgrade to 7.3(1)DY(1).
● Downgrading from Cisco MDS NX-OS Release 8.1(1) and Release 8.1(1b) is not supported if the FLOGI Scale Optimization feature is enabled on the Cisco MDS 9718 Switches.
Table 2. Nondisruptive Downgrade Paths from NX-OS Release 8.4(2d)
| Target Release |
Nondisruptive Downgrade Paths and Ordered Downgrade Steps |
| MDS NX-OS: |
|
| All 8.x releases |
Downgrade to the target release |
| All 7.3(x) releases |
Step 1. Downgrade directly to MDS NX-OS Release 8.1(1b) Step 2. Downgrade to the target release |
| 6.2(29) and above releases |
Downgrade to the target release |
| 6.2(13a) until 6.2(27) |
Step 1. Downgrade directly to MDS NX-OS Release 8.1(1b) Step 2. Downgrade to the target release |
| All 6.2(x) releases prior to 6.2(13a) |
Step 1. Downgrade directly to MDS NX-OS Release 8.1(1b) Step 2. Downgrade to MDS NX-OS Release 6.2(13a) Step 3. Downgrade to the target release |
New Hardware and Software Features
● New Hardware Features in Cisco MDS NX-OS Release 8.4(2d)
● New Software Features in Cisco MDS NX-OS Release 8.4(2d)
New Hardware Features in Cisco MDS NX-OS Release 8.4(2d)
There are no new hardware features in Cisco MDS NX-OS Release 8.4(2d).
New Software Features in Cisco MDS NX-OS Release 8.4(2d)
There are no new software features in Cisco MDS NX-OS Release 8.4(2d).
Unsupported Features
Data Mobility Manager
From Cisco MDS NX-OS Release 8.1(1), the Cisco MDS Data Mobility Manager is not supported on Cisco MDS 9000 Series Switches.
Zoning Features
LUN zoning, read-only zones, and broadcast zones are no longer supported.
If these features are already configured, completely remove all the configurations that include these features before attempting to boot any module. In addition, you cannot configure these features after you bring up any module.
XRC Acceleration License
From Cisco MDS NX-OS Release 8.1(1a), the Cisco Extended Remote Copy (XRC) acceleration license is obsoleted on Cisco MDS 9000 Series Switches due to improvements in the mainframe XRC feature.
FICON Tape Acceleration
FICON Tape Acceleration (FTA) is not supported on Cisco MDS 24/10 SAN Extension Module in Cisco MDS NX-OS Release 8.1(1a) but it is supported in Cisco MDS NX-OS Release 8.1(1b), Release 8.4(1a), Release 8.4(2b), and Release 8.4(2c).
Virtual Router Redundancy Protocol (VRRP)
From Cisco MDS NX-OS Release 8.3(1) and later, the VRRP feature is not supported on Cisco MDS 9000 Series Switches.
Deprecated Hardware
From Cisco MDS NX-OS Release 8.1(1), the following hardware models are not supported:
● Cisco MDS 9513
● Cisco MDS 9509
● Cisco MDS 9506
● Cisco MDS 9500 Series Supervisor-2A Module
● Cisco MDS 24-Port 8-Gbps Fibre Channel Switching Module
● Cisco MDS 48-Port 8-Gbps Fibre Channel Switching Module
● Cisco MDS 32-Port 8-Gbps Advanced Fibre Channel Switching Module
● Cisco MDS 48-Port 8-Gbps Advanced Fibre Channel Switching Module
● Cisco MDS 10-Gbps 8-Port FCoE Module
● Cisco MDS 16-Port Storage Services Node (SSN-16)
● Cisco MDS 18/4-Port Multiservice Module (MSM)
Fibre Channel Read Diagnostic Parameters
Fibre Channel RDP querying is not supported on NPV, Port Channel, or FCoE links.
Slow Drain Detection and Congestion Isolation
ER_RDY is not supported on FC interfaces running at 10 Gbps.
FCIP Support
● In Cisco MDS NX-OS Release 8.1(1) or later, FCIP Write Acceleration is not supported between 24/10 San Extension Module and Cisco 18+4 MSM module and between 24/10 San Extension Module and Cisco SSN16 module.
● In Cisco MDS NX-OS Release 8.1(1) or later, FCIP Write Acceleration along with IVR is not supported on FCIP tunnels configured on Cisco MDS 9700 Series switches.
● FCIP tunnels using Cisco MDS 24/10 Port SAN Extension Module cannot be used across FSPF equal cost paths.
● On Cisco MDS 24/10 Port SAN Extension Module, configuring multiple ECMP port channels with FCIP members in the same VSAN is not a valid configuration. If this is configured, then the traffic will flow through only one of the port channels.
iSCSI Support
iSCSI is not supported on Cisco MDS 9700 Directors with Cisco MDS 24/10 port SAN Extension Modules.
HVDC PSU Support
The Cisco MDS 9700 HVDC PSU (DS-CHV-3.5KW) is not supported in Cisco MDS NX-OS Releases 8.1(1) and Release 8.1(1a). Do not attempt to load these releases on devices equipped with these PSUs or the systems will fail to power up.
Cisco TrustSec FC Link Encryption
Cisco TrustSec FC Link Encryption support is available only on certain ports for the following modules:
● 48-port 2/4/8/16-Gbps Fibre Channel switching module (DS-X9448-768K9)
● 48-port 4/8/16/32-Gbps Fibre Channel switching module (DS-X9648-1536K9)
● 48-port 32-Gbps Fibre Channel Switching Module (DS-X9648-1536K9)
● Cisco MDS 9000 24/10-Port SAN Extension Module (DS-X9334-K9)
● Cisco MDS 9132T 32-Gbps 32-Port Fibre Channel Fabric Switch
● Cisco MDS 9148T 32-Gbps 48-Port Fibre Channel Fabric Switch
● Cisco MDS 9396T 32-Gbps 96-Port Fibre Channel Fabric Switch
● Cisco MDS 9396S 16-Gbps 96-Port Fibre Channel Fabric Switch
Caveats
● Subscribing for Important Product Update Notifications
● Resolved Defects in Cisco MDS NX-OS Release 8.4(2d)
● Open Defects in Cisco MDS NX-OS Release 8.4(2d)
Subscribing for Important Product Update Notifications
Cisco provides a subscription service to notify of important events related to the Cisco MDS software and hardware for the following categories:
● Cisco Security Advisories
● Field Notices
● End-of-Sale, End-of-Life, and End-of-Support Announcements
● Software Updates [New, Certified, Software Advisories, Deferred, Obsoleted]
● Updates to Known Bugs
We recommend that you at least subscribe to the Field Notices, Security Advisories, and Software Updates [New, Certified, Software Advisories, Deferred, Obsoleted] categories, if not all categories, so that you can receive notifications about any critical product issues.
To subscribe to a category for receiving notifications of important updates:
1. Go to https://cway.cisco.com/mynotifications, and log in to your account.
2. Click Create Subscription.
3. Follow the onscreen instructions.
Note: You must renew your notification subscriptions annually.
Resolved Defects in Cisco MDS NX-OS Release 8.4(2d)
Severity 1 (Catastrophic) Defects
| Defect ID |
Description |
Known Impacted Releases |
| Module hangs or resets after 450-460 days uptime due to 'machine check' error. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
Severity 2 (Severe) Defects
| Defect ID |
Description |
Known Impacted Releases |
| * fcid entry is missing from active zone after trying to register duplicate port name. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| ISSU/D is disruptive on MDS fabric switches with error 0x40930073 after SFTP to bootflash. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| 'vsh' process crashes while executing 'show fcdomain internal info mts'. |
8.4(2a), 8.4(2b), 8.4(2c) |
|
| Supervisor 4 usb-storage timeout. |
8.5(1) 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| ISSU results in switch 9250i reboot (fcns crash). |
8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| SSH service does not dump core file when it crashes. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| Port Channel output discards after single member link failure with in-order-guarantee configured. |
8.4(2a), 8.4(2b), 8.4(2c) |
|
| Copy/auto-copy for Kernel core doesn't work unless "show cores" is executed. |
8.4(2c) |
|
| Zone service crashed with signal 6 on MDS 9148S. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) |
|
| Parity error in TCAM may lead to traffic disruption. |
8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| vshd hap reset. |
8.4(2a), 8.4(2b), 8.4(2c) |
|
| End devices encounter errors or do not respond after MDS Fabric switch ISSU. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| RIB process die during booting up of module DS-X9648-1536K9. |
8.4(2a), 8.4(2b), 8.4(2c) |
|
| Recover after CPU core stall self detected on supervisor. |
8.4(2b), 8.4(2c) |
|
| Cisco FXOS and NX-OS Software Cisco Discovery Protocol Service Denial of Service. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| Ports stay in 'notConnected' state after losing link. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1b) |
|
| IVR hap reset crash caused MDS 9710s switches to reboot. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1a), 8.1(1b) |
|
| Chassis IDPROM corruption. |
8.4(2b), 8.4(2c) |
Severity 3 (Moderate) Defects
| Defect ID |
Description |
Known Impacted Releases |
| %SYSMGR-2-TMP_DIR_FULL syslog repeated endlessly, flushing out other needed logs. |
8.5(1) 8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(2) |
|
| Interface CRCs not incrementing on MDS 32G modules/switches. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| EEM script blocks certain PTS and after 32 blocked terminal logging stops working. |
8.5(1) 8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) |
|
| Interface CRCs not incrementing on MDS 32G modules/switches |
8.4(2b), 8.4(2a), 8.4(2), 8.4(1a), 8.4(1) 8.1(1) |
|
| On MDS "system timestamp format rfc5424" is not working for messages sent to remote logging servers. |
8.4(2a), 8.4(2b), 8.4(2c) |
|
| 16G FICON port is getting corrupt and losing path with FEC enabled on 32G module. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1b) |
|
| Reloading a switch by a remotely authenticated LDAP user causes CLI error messages. |
8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| "port-security" crash on MDS 9000. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| 'ishow core backtrace': not working with valid pid + unable to SCP core files after invalid pid. |
8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| Group of 16 Gbps ports goes to 'Hardware Failure' state (%PORT-5-IF_DOWN_HW_FAILURE). |
8.5(1) |
|
| FCIP throughput for some routes through MDS9700 24/10 FCIP module reduced after replacing the module. |
8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| SYSMGR-2-SERVICE_CRASHED: Service "snmpd". |
8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| MDS zoneset activate fails: Device-alias enhanced zone member unsupported in device-alias basic mode. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| SNMP-server user privilege password is not updated. |
8.5(1) |
|
| BA_ACC sent by remote FCIP-peer MDS may not set 'end sequence' to 1. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(2) |
|
| XBAR initialization failure message indicates 'not enough memory' when PCIe bus failure. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| UDP/Secure syslog not working after a syslog process restart. |
8.4(2c) |
|
| snmp-server host port automatically changes. |
8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| PMON False Alarms reported for a "core type " port-channel ,but PMON configured only for Edge ports. |
8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| FSPF "Error in processing interface timer event" msg and switch becomes isolated from fabric. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) |
|
| 'show system internal fcoe_mgr info global' defaults to detailed output. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| 'system auto-collect tech-support' missing from cfg, command completion/inline help not working. |
8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| IPStorage interface input error counters not incrementing. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| MDS 9710 switch does not allow /31 mask in IPS storage interface. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) |
|
| `reload system non-disruptive` fails if volatile memory is full and reloads switch. |
8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| Improve logging when a spinlock lockup occurs. |
8.4(2b), 8.4(2c) |
|
| Members added to existing port-channel DOWN with "Isolation due to port-channel mis-configuration". |
8.4(2b), 8.4(2c) |
|
| DS-X9648-1536K9: DS-X9648-1536K9 Acltcam crash seen during ISSU. |
8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
|
| The local user account login fails with error of "account expired" in 8.4.(2x)/8.5(1) versions. |
8.4(2a), 8.4(2b), 8.4(2c) |
|
| Autozone issues messages on the same devices that are registered without initiator or target. |
8.4(2c) |
|
| GLDN :: MDS : FAST : Sec-Cry-Mgt/Sec-Tls-Curr copy https failing for curl. |
8.4(2c) |
Severity 4 (Minor) Defects
| Defect ID |
Description |
Known Impacted Releases |
| Add OUI 0x4CE176 to OUI Database - Port-channels and trunking not working with OUI 0x4CE176. |
8.4(1), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) |
Severity 5 (Cosmetic) Defects
| Defect ID |
Description |
Known Impacted Releases |
| Add missing newlines in kernel nvram crash log output. |
8.4(2b), 8.4(2c) |
Severity 6 (Enhancement) Defects
| Defect ID |
Description |
Known Impacted Releases |
| 'ivr diagnostics' should report VSANs which are not stable. |
8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| Need to log debugging info when partition has unexpectedly high usage. |
8.4(2c) |
Open Defects in Cisco MDS NX-OS Release 8.4(2d)
Severity 2 (Severe) Defects
| Defect ID |
Description |
Known Impacted Releases |
| MDS 9700 Control Plane Packet drop seen during when switch comes up. |
8.5(1) 8.4(1), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) |
|
| ISSD: Install has failed. Return code 0x40930039 (aborting due to failed upgrade). |
8.4(2d) |
|
| Service "zone" (PID XXXX) hasn't caught signal 6 (core will be saved). |
9.2(1), 9.2(2) 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) |
|
| End devices unable to communicate - FCNS rejects all FC CT queries with 'logical busy' |
9.2(2) 8.4(2d) |
Severity 3 (Moderate) Defects
| Defect ID |
Description |
Known Impacted Releases |
| running snmpwalk IPv6 displays error "Received source port is zero". |
8.5(1) 8.4(1), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) |
|
| IPSec enabled FCIP tunnels don't come up after switch or module reload if tunnels are more than 18. |
8.5(1) 8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| MDS DS-X9648-1536K9 ports went to notConnected state after many port flaps. |
8.5(1) 8.4(2c), 8.4(2d) |
|
| f32_mac_sw_creditmon: Port 0 Port mode not valid errors floods under fcmac event-history. |
8.5(1) 8.4(2c), 8.4(2d) |
|
| SEC-CRY-PRIM TLS failures on N7K and MDS. |
8.4(2d) |
Severity 4 (Minor) Defects
| Defect ID |
Description |
Known Impacted Releases |
| M9132T, M9396S MDS9148T : pam_ftp(ftp:auth): conversation failed syslog is in the show tech details. |
8.5(1) 8.4(1), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) 8.3(2), 8.3(1) 8.2(2), 8.2(1) |
|
| "show system login failures" does not display IPv6 addresses. |
8.5(1) 8.4(1), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) 8.3(2), 8.3(1) |
|
| IPS_mgr running even after removal of DS-X9334-K9 card. |
8.5(1) 8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) 8.3(1), 8.3(2) 8.2(1), 8.2(2) 8.1(1), 8.1(1a), 8.1(1b) |
|
| Non-disruptive reload cmd is causing reinitializing of the error disabled ports on other line cards. |
8.5(1) 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) |
|
| Remove misleading merge failed message for ficonstat in non-FICON VSAN. |
8.5(1) 8.4(2b), 8.4(2c), 8.4(2d) |
|
| M9710:Syntax error while parsing 'show ficon stat internal diagnostics info' - sh tech details. |
8.4(2d) |
Severity 6 (Enhancement) Defects
| Defect ID |
Description |
Known Impacted Releases |
| While moving IOA flow between 2 clusters, all flows are briefly suspended. |
8.5(1) 8.4(1), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) 8.3(2), 8.3(1) 8.2(2), 8.2(1) 8.1(1b), 8.1(1a), 8.1(1) |
|
| MDS: Receiver stays in “idle”; no streaming to one receiver; single threaded telemetry. |
8.5(1) 8.4(1), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) |
|
| Need to log nonvolatile logs about BIOS programming errors. |
8.5(1) 8.4(2c), 8.4(2d) 8.3(2) |
Related Documentation
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
Release Notes
Licensing Information
Regulatory Compliance and Safety Information
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/hw/regulatory/compliance/RCSI.html
Compatibility Information
Installation and Upgrade
Configuration Guides
Command-Line Interface
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.
Legal Information
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. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2022 Cisco Systems, Inc. All rights reserved.