Cisco Mds 9000 NX Os Release Notes 842f
Cisco Mds 9000 NX Os Release Notes 842f
Release Notes
Release 8.4(2f)
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
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 addresses 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 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.
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(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.
◦ 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.
8.(x) and above releases1 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).
All 6.2(x) releases prior to Step 1. Upgrade directly to MDS NX-OS Release 6.2(13a)
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)
● 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.
1
If the SAN Analytics feature is enabled, then disable the SAN Analytics feature using the no feature analytics command before
upgrading from Cisco MDS NX-OS 8.2(x) or Cisco MDS NX-OS 8.3(x) to Cisco MDS NX-OS Release 9.2(1) or later. However, you
can upgrade from Cisco MDS NX-OS Release 8.4(1) and later releases to Cisco MDS NX-OS Release 9.2(1) or later without
disabling the feature.
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.
● 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).
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
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.
Deprecated Hardware
From Cisco MDS NX-OS Release 8.1(1), the following hardware models are not supported:
DS-X9748-3072 64 Gbps Fibre Channel Switching 9, 11, 13, 15, 25, 27, 29, 31 AES 128 bit
module
DS-X9648- 32 Gbps Fibre Channel Switching 9-12, 25-28, 41-44 AES 128 bit
1536K9 Module
DS-X9448- 16 Gbps Fibre Channel Switching All FC ports AES 128 bit
768K9 module
DS-X9334-K9 24/10 Port SAN Extension All FC ports AES 128 bit
Module
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
Resolved Issues
Severity 1 (Catastrophic) Issues
CSCwc76047 Supervisor/Fabric switch reload after new F-port Port Channel is 9.2(1)
brought up
8.4(2d)
8.1(1)
7.3(0)D1(1)
6.2(1)
CSCwd34476 Cisco NXOS SSH X.509v3 Cert Auth w/Unsupported Remote 9.3(1)
Authorization Priv Escalation Issues
8.1(1)
7.3(0)D1(1)
CSCwd63288 "Ldap Daemon" crashes on MDS 9000 due to heartbeat failure. 8.5(1)
CSCwe00201 MDS: DDAS commit failure. Reason: registered modules didn't 9.2(1a)
respond to validation request in time.
CSCwe09928 Device alias force commit modifies zone members on peer 9.3(2)
switch
8.4(2a)
CSCwe25542 MDS 9148S running 8.4.2d Port with a faulty SFP leads to 8.4(2d)
CPU/System busy condition
CSCwe31401 MDS9700:pltfm_config crash when ISSU from 8.4(2c) to 8.4(2d) 8.4(2c), 8.4(1)
while smart lic enabled
8.3(1)
8.2(1)
8.1(1)
6.2(13)
CSCvv93277 Interface CRCs not incrementing on MDS 32G 8.4(1), 8.4(1a), 8.4(2), 8.4(2a),
modules/switches. 8.4(2b)
8.3(1), 8.3(2)
8.2(1), 8.2(2)
8.1(1), 8.1(1a), 8.1(1b)
CSCwb74960 Callhome Process Causing Hangs in: show callhome, show 8.4(2b), 8.4(2c), 8.4(1a, 8.4(1))
running-config, copy run start
CSCwd31164 Cisco NX-OS Software for MDS 9000 Series CLI Command 9.3(1.76)
Injection
CSCwd31826 "fdmi" service stops functioning properly with signal 11 (core 9.2(2)
will be saved)
CSCwd34477 Cisco NXOS SSH X.509v3 Cert Auth w/Unsupported Remote 9.3(1)
Authorization Priv Escalation Issues
CSCwd61297 Device unable to communicate with other devices using IVR 8.3(2)
CSCwe46073 'show tech-support details' command hangs and doesn't print 9.3(1)
any output
8.4(2e)
CSCwd36586 Display issue with standby information in 'show tech-support ha' 9.3(1.79)S0
CSCwd69614 Add Nexus 9000 OUI 0xe069ba to the default MDS OUI 8.4(2d)
database for port-channel to stay online
Open Issues
Severity 2 (Severe) Issues
CSCvp48050 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)
CSCvx47078 f32_mac_sw_creditmon: Port 0 Port mode not valid errors floods 8.5(1)
under fcmac event-history.
8.4(2c), 8.4(2d)
CSCvj93031 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)
CSCvs23106 SCSI target discovery service running even after removal of last DS- 8.5(1)
X9334-K9 module from switch
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)
CSCvo22835 All flows are briefly suspended while moving an IOA flow between 2 8.5(1)
clusters.
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)
CSCvp70681 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)
CSCvx37657 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
http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-
software/products-release-notes-list.html
Licensing Information
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/8_x/config/licensing/cisco_m
ds9000_licensing_guide_8x.html
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/hw/regulatory/compliance/RCSI.ht
ml
Compatibility Information
http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-
software/products-device-support-tables-list.html
http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-
software/products-installation-guides-list.html
http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-
software/products-installation-and-configuration-guides-list.html
Command-Line Interface
http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-
software/products-command-reference-list.html
http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-software/tsd-
products-support-troubleshoot-and-alerts.html
Documentation Feedback
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.
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:
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.