Cisco MDS 9000 Series Release Notes, Release 8.4(2f)
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
Note: The documentation set for this product strives to use bias-free language. For 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 |
| December 22, 2023 |
Added CSCwf85545 to the Open Issues section. |
| November 06, 2023 |
Added CSCvv93277 in the Resolved Issues section. |
| March 30, 2023 |
Initial release. |
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 addresses the stringent requirements of large data center storage environments: high availability, security, scalability, ease of management, and seamless integration of new technologies.
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 NDFC 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(2f) 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.
For information on supported software and hardware components, see the Cisco MDS 9000 Series Compatibility Matrix.
Cisco MDS NX-OS Release 8.4(2f) 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 NDFC, see Cisco NDFC 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.
◦ 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(2f)
| Current Release |
Nondisruptive Upgrade Paths and Ordered Upgrade Steps |
| 8.(x) and above releases[1] |
Upgrade directly to MDS NX-OS Release 8.4(2f)) |
| 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(2f) |
| 6.2(29) and above releases |
Step 1. Upgrade to MDS NX-OS Release 8.4(2c) or 8.4(2d). Step 2. Upgrade to MDS NX-OS Release 8.4(2f). |
| 6.2(13a) until 6.2(27) |
Step 1. Upgrade to MDS NX-OS Release 8.1(1b) Step 2. Upgrade to MDS NX-OS Release 8.4(2f) |
| 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(2f) |
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:
o 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.
o 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.
o IPS Ports: Traffic on IPS ports on Cisco MDS 9220i 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 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.
● Non-disruptive downgrading from Cisco MDS NX-OS Release 8.5(1) to 8.4(x) is not supported. For more information, see CSCwd18183.
● 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.
● 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.
Open Systems Nondisruptive Downgrade Paths
The software downgrade information in this section applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP traffic and intelligent services traffic.
Table 2. Nondisruptive Downgrade Paths from NX-OS Release 8.4(2f)
| Target Release |
Nondisruptive Downgrade Paths and Ordered Downgrade Steps |
| 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 |
Step 1. Downgrade directly to MDS NX-OS Release 8.4(2c) or 8.4(2d). Step 2. 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(2f)
● New Software Features in Cisco MDS NX-OS Release 8.4(2f)
New Hardware Features in Cisco MDS NX-OS Release 8.4(2f)
There are no new hardware features in Cisco MDS NX-OS Release 8.4(2f).
New Software Features in Cisco MDS NX-OS Release 8.4(2f)
There are no new software features in Cisco MDS NX-OS Release 8.4(2f).
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.
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 is supported on certain ports for the following modules:
Table 3. Cisco TrustSec FC Link Encryption
| Model |
Description |
Cisco TrustSec Capable Ports |
Encryption Key Length |
| DS-X9748-3072 |
64 Gbps Fibre Channel Switching module |
9, 11, 13, 15, 25, 27, 29, 31 |
AES 128 bit |
| DS-X9648-1536K9 |
32 Gbps Fibre Channel Switching Module |
9-12, 25-28, 41-44 |
AES 128 bit |
| DS-X9448-768K9 |
16 Gbps Fibre Channel Switching module |
All FC ports |
AES 128 bit |
| DS-X9334-K9 |
24/10 Port SAN Extension Module |
All FC ports |
AES 128 bit |
| DS-C9132T-K9 |
MDS 9132T Fabric Switch |
9-12, 25-28 |
AES 128 bit |
| DS-C9148T-K9 |
MDS 9148T Fabric Switch |
9-12, 25-28, 41-44 |
AES 128 bit |
| DS-C9396T-K9 |
MDS 9396T Fabric Switch |
Base ports: 9-12, 25-28, 41-44 |
AES 128 bit |
| DS-C9396S-K9 |
MDS 9396S Fabric Switch |
LEM ports: 57-60, 73-76, 89-92 |
AES 128 bit |
Severity 1 (Catastrophic) Issues
| Defect ID |
Description |
Known Impacted Releases |
| MDS switch continuously rebooting |
8.4(2c), 8.4(1) |
Severity 2 (Severe) Issues
| Defect ID |
Description |
Known Impacted Releases |
| CPUHOG on linecard may lead to traffic disruption |
8.4(2) |
|
| Supervisor/Fabric switch reload after new F-port Port Channel is brought up |
9.2(1) 8.4(2d) 8.1(1) 7.3(0)D1(1) 6.2(1) |
|
| Cisco NXOS SSH X.509v3 Cert Auth w/Unsupported Remote Authorization Priv Escalation Issues |
9.3(1) 8.1(1) 7.3(0)D1(1) |
|
| core-dmon process crashes and reloads unexpectedly due to HA policy of Reset |
9.3(1) 9.2(1), 9.2(1a) 8.5(1) 8.4(1) 8.3(1) 8.2(1) 8.1(1) |
|
| "Ldap Daemon" crashes on MDS 9000 due to heartbeat failure. |
8.5(1) |
|
| MDS: DDAS commit failure. Reason: registered modules didn't respond to validation request in time. |
9.2(1a) |
|
| Device-alias rename does not rename zone members |
9.3(2) 8.4(1a) |
|
| Device alias force commit modifies zone members on peer switch |
9.3(2) 8.4(2a) |
|
| MDS 9148S running 8.4.2d Port with a faulty SFP leads to CPU/System busy condition |
8.4(2d) |
|
| MDS9700:pltfm_config crash when ISSU from 8.4(2c) to 8.4(2d) while smart lic enabled |
8.4(2c), 8.4(1) 8.3(1) 8.2(1) 8.1(1) 6.2(13) |
Severity 3 (Moderate) Issues
| Defect ID |
Description |
Known Impacted Releases |
| 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) |
|
| Internal fcns error about invalid VSAN |
8.4(2b) |
|
| Callhome Process Causing Hangs in: show callhome, show running-config, copy run start |
8.4(2b), 8.4(2c), 8.4(1a, 8.4(1)) |
|
| Unexpected "vlan-mgr" service crash |
8.4(2c) |
|
| Credit monitoring disabled on a port after TrustSec exception |
8.4(2c) |
|
| Cisco NX-OS Software CLI Command Injection Vulnerability |
8.1(1) |
|
| Server interfaces on an NPV switch don't come up |
9.2(1a), 9.2(1) 8.5(1) 8.4(2d), 8.4(2c), 8.4(2a), 8.4(2) 8.4(1a), 8.4(1) 8.2(1)SMU(0.2) 8.3(1), 8.3(1)SMU(0.13) 8.1(1b), 8.1(1a) |
|
| ACL consistency checker displays failures and errors |
8.4(1a) |
|
| Cisco NX-OS Software for MDS 9000 Series CLI Command Injection |
9.3(1.76) |
|
| "fdmi" service stops functioning properly with signal 11 (core will be saved) |
9.2(2) |
|
| Cisco NXOS SSH X.509v3 Cert Auth w/Unsupported Remote Authorization Priv Escalation Issues |
9.3(1) |
|
| Device unable to communicate with other devices using IVR |
8.3(2) |
|
| Kernel panic on MDS 9148S |
8.4(2d) |
|
| MDS 9148S listening to non-essential TCP port |
8.4(2e) |
|
| 'show tech-support details' command hangs and doesn't print any output |
9.3(1) 8.4(2e) |
Severity 4 (Minor) Issues
| Defect ID |
Description |
Known Impacted Releases |
| Internal fcns error about invalid VSAN |
9.3(2) 8.4(2d) 8.4(2c) |
Severity 5 (Cosmetic) Issues
| Defect ID |
Description |
Known Impacted Releases |
| Display issue with standby information in 'show tech-support ha' |
9.3(1.79)S0 |
Severity 6 (Enhancement) Issues
| Defect ID |
Description |
Known Impacted Releases |
| Add "show device-alias merge conflicts" in show tech-support details |
9.2(2) |
|
| Add Nexus 9000 OUI 0xe069ba to the default MDS OUI database for port-channel to stay online |
8.4(2d) |
|
| Add "show fdmi internal event-history" in show tech-support details and slowdrain |
8.4(2d) |
| Defect ID |
Description |
Known Impacted Releases |
| MDS 9700 control plane packet drops after switch boot |
8.5(1) 8.4(1), 8.4(1a), 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) |
Severity 3 (Moderate) Issues
| Defect ID |
Description |
Known Impacted Releases |
| 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) |
|
| "port" service crash |
8.4(2f), 8.4(2e) |
Severity 4 (Minor) Issues
| Defect ID |
Description |
Known Impacted Releases |
| 'show tech details' triggers 'pam_ftp(ftp:auth): conversation failed - ftpd' syslogs |
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) |
|
| IPv6 source address not displayed in log in failure logs |
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) |
|
| SCSI target discovery service running even after removal of last DS-X9334-K9 module from switch |
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) |
|
| Nondisruptive reload causes reinitialization of error disabled ports on other linecards |
8.5(1) 8.4(2), 8.4(2a), 8.4(2b), 8.4(2c), 8.4(2d) |
|
| Remove misleading ficonstat 'merge failed' message in non-FICON VSAN |
8.5(1) 8.4(2b), 8.4(2c), 8.4(2d) |
|
| Linecard fails to boot up with '%PORT-5-MODULE_BRINGUP_NOT_ALLOWED' error |
8.4(2c) 8.1(1) |
Severity 6 (Enhancement) Issues
| Defect ID |
Description |
Known Impacted Releases |
| All flows are briefly suspended while moving an IOA flow between 2 clusters. |
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) |
|
| Streaming to telemetry receiver stops, receiver stays in "idle" state |
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) |
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
To provide technical feedback on this document, or to report an error or omission, send your comments to mds-docfeedback@cisco.com. We appreciate your feedback.
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: https://www.cisco.com/c/en/us/about/legal/trademarks.html. 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-2023 Cisco Systems, Inc. All rights reserved.