PDF(522.0 KB) View with Adobe Reader on a variety of devices
Updated:November 14, 2018
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.
The Cisco MDS 9000 Series of Multilayer Directors and Fabric Switches provides best-in-class high availability, scalability, security, and management, allowing you 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 addresses the stringent requirements of large data center storage environments: 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.
Choosing Between Cisco MDS NX-OS Releases
Cisco uses MDS NX-OS release numbering to indicate when significant features or hardware support are added to the code. This allows older trains to provide stability and newer trains to focus on new features and hardware.
Cisco MDS NX-OS Release 6.2(x) - This release train provides general support for all currently supported Cisco MDS platforms except for the Cisco MDS 9718 Director and the Cisco MDS 9124 Multilayer Fabric Switch. It should be the first choice to deploy unless there is a need for the new features and hardware supported in Cisco MDS NX-OS 7.3(x) train.
Cisco MDS NX-OS Release 7.3(x)D1(x) - This release train supports the same platforms as the 6.2(x) train as well as the Cisco MDS 9718 Director and the Cisco MDS 24-Port 40-Gbps Fibre Channel over Ethernet Module. It is based on Cisco MDS NX-OS Release 6.2(x).
Cisco MDS NX-OS Release 7.3(x)DY(x) - This release train supports the same platforms as the 7.3(x)D1(x) train as well as the Cisco MDS 24/10 port SAN Extension Module. It is based on Cisco MDS NX-OS Release 7.3(0)D1(1).
Details about the new features and hardware supported by each Cisco MDS NX-OS release can be found in the New Hardware and Software Features section in this document.
For detailed instructions for performing a software upgrade using Cisco DCNM, see the Cisco DCNM Release Notes.
General Upgrading Guidelines
Follow these general guidelines before 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 your upgrade will be nondisruptive.
Be aware that 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 Table 2 for the nondisruptive upgrade path for all MDS NX-OS releases.
– Gigabit Ethernet Ports : Traffic on Gigabit Ethernet or IPStorage ports are disrupted during an upgrade or downgrade. This includes the Gigabit Ethernet ports on the MDS 9000 16-Port Storage Services Node (SSN-16), IPStorage ports on the MDS 9250i, MSM-18+4 Module, and Cisco MDS 24/10 Port SAN Extension Module. Nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the upgrade is in progress.
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.
Nondisruptive Upgrade Paths
The software upgrade information in Table 2, Table 3, and Table 4 applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and intelligent services traffic.
Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 7.3(1)DY(1)
Use Table 2 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 7.3(1)DY(1). 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.
Upgrading from releases prior to Cisco MDS NX-OS Release 6.2(9) to Cisco MDS NX-OS Release 7.3(1)DY(1) is not supported. In such a scenario, we recommend that you first upgrade to Cisco MDS NX-OS Release 6.2(9) or higher and then upgrade to Cisco MDS NX-OS Release 7.3(1)DY(1).
Upgrading from Cisco MDS NX-OS Release 7.3(1)D1(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 Cisco MDS NX-OS Release 7.3(1)DY(1).
We recommend that you delete existing IP ACLs on the management interface before upgrading to Cisco MDS NX-OS Release 7.3(1)DY(1). You can reconfigure the IP ACLs after the upgrade is complete. For more information, see CSCvh30932.
Nondisruptive Upgrade Path and Ordered Upgrade Steps
MDS NX-OS:
7.3(0)DY(1)
Upgrade to MDS NX-OS Release 7.3(1)DY(1)
7.3(1)D1(1)
1. Downgrade to MDS NX-OS Release 7.3(0)D1(1)
2. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
All 6.2(9) and above releases
Upgrade directly to MDS NX-OS Release 7.3(1)DY(1)
All 6.2(7) and earlier 6.2(x) releases
1. Upgrade to MDS NX-OS Release 6.2(9)
2. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
All 5.2(x) releases
1. Upgrade to MDS NX-OS Release 6.2(9)
2. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
All 5.0(x) releases
1. Upgrade to MDS NX-OS Release 5.2(8h)
2. Upgrade to MDS NX-OS Release 6.2(9)
3. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
All 4.2(x) releases and 4.1(x) releases
1. Upgrade to MDS NX-OS Release 5.0(8a)
2. Upgrade to MDS NX-OS Release 5.2(8h)
3. Upgrade to MDS NX-OS Release 6.2(9)
4. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
MDS SAN-OS:
Release 3.3(2), 3.3(3), 3.3(4x), and 3.3(5x).
1. Upgrade to MDS NX-OS Release 4.2(9)
2. Upgrade to MDS NX-OS Release 5.0(8a)
3. Upgrade to MDS NX-OS Release 5.2(8h)
4. Upgrade to MDS NX-OS Release 6.2(9)
5. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
Release 3.3(1c), all 3.2(x), 3.1(x), and 3.0(x) releases
1. Upgrade to MDS SAN-OS Release 3.3(5b)
2. Upgrade to MDS NX-OS Release 4.2(9)
3. Upgrade to MDS NX-OS Release 5.0(8a)
4. Upgrade to MDS NX-OS Release 5.2(8h)
5. Upgrade to MDS NX-OS Release 6.2(9)
6. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
Release 2.1(3), 2.1(2e), 2.1(2d), and 2.1(2b)
1. Upgrade to MDS SAN-OS Release 3.3(1c)
2. Upgrade to MDS SAN-OS Release 3.3(5b)
3. Upgrade to MDS NX-OS Release 4.2(9)
4. Upgrade to MDS NX-OS Release 5.0(8a)
5. Upgrade to MDS NX-OS Release 5.2(8h)
6. Upgrade to MDS NX-OS Release 6.2(9)
7. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
Release 2.1(2), 2.1(1b), 2.1(1a), and 2.0(x)
1. Upgrade to MDS SAN-OS Release 2.1(2b), 2.1(2d), 2.1(2e), or 2.1(3)
2. Upgrade to MDS SAN-OS Release 3.3(1c)
3. Upgrade to MDS SAN-OS Release 3.3(5b)
4. Upgrade to MDS NX-OS Release 4.2(9)
5. Upgrade to MDS NX-OS Release 5.0(8a)
6. Upgrade to MDS NX-OS Release 5.2(8h)
7. Upgrade to MDS NX-OS Release 6.2(9)
8. Upgrade to MDS NX-OS Release 7.3(1)DY(1)
Release 1.x
1. Upgrade to MDS SAN-OS Release 1.3(4a)
2. Upgrade to MDS SAN-OS Release 2.1(2b)
3. Upgrade to MDS SAN-OS Release 3.3(1c)
4. Upgrade to MDS SAN-OS Release 3.3(5b)
5. Upgrade to MDS NX-OS Release 4.2(9)
6. Upgrade to MDS NX-OS Release 5.0(8a)
7. Upgrade to MDS NX-OS Release 5.2(8h)
8. Upgrade to MDS NX-OS Release 6.2(9)
9. Upgrade to MDS NX-OS Release7.3(1)DY(1)
Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 7.3(0)DY(1)
Use Table 3 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 7.3(0)DY(1). 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.
Upgrading from releases prior to Cisco MDS NX-OS Release 6.2(9) to Cisco MDS NX-OS Release 7.3(0)DY(1) is not supported. In such a scenario, we recommend that you first upgrade to Cisco MDS NX-OS Release 6.2(9) or higher and then upgrade to Cisco MDS NX-OS Release 7.3(0)DY(1).
Upgrading from Cisco MDS NX-OS Release 7.3(1)D1(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 Cisco MDS NX-OS Release 7.3(0)DY(1).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
MDS NX-OS:
7.3(1)D1(1)
1. Downgrade to MDS NX-OS Release 7.3(0)D1(1)
2. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
All 6.2(9) and above releases
Upgrade directly to MDS NX-OS Release 7.3(0)DY(1)
All 6.2(7) and earlier 6.2(x) releases
1. Upgrade to MDS NX-OS Release 6.2(9)
2. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
All 5.2(x) releases
1. Upgrade to MDS NX-OS Release 6.2(9)
2. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
All 5.0(x) releases
1. Upgrade to MDS NX-OS Release 5.2(8h)
2. Upgrade to MDS NX-OS Release 6.2(9)
3. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
All 4.2(x) releases and 4.1(x) releases
1. Upgrade to MDS NX-OS Release 5.0(8a)
2. Upgrade to MDS NX-OS Release 5.2(8h)
3. Upgrade to MDS NX-OS Release 6.2(9)
4. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
MDS SAN-OS:
Release 3.3(2), 3.3(3), 3.3(4x), and 3.3(5x).
1. Upgrade to MDS NX-OS Release 4.2(9)
2. Upgrade to MDS NX-OS Release 5.0(8a)
3. Upgrade to MDS NX-OS Release 5.2(8h)
4. Upgrade to MDS NX-OS Release 6.2(9)
5. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
Release 3.3(1c), all 3.2(x), 3.1(x), and 3.0(x) releases
1. Upgrade to MDS SAN-OS Release 3.3(5b)
2. Upgrade to MDS NX-OS Release 4.2(9)
3. Upgrade to MDS NX-OS Release 5.0(8a)
4. Upgrade to MDS NX-OS Release 5.2(8h)
5. Upgrade to MDS NX-OS Release 6.2(9)
6. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
Release 2.1(3), 2.1(2e), 2.1(2d), and 2.1(2b)
1. Upgrade to MDS SAN-OS Release 3.3(1c)
2. Upgrade to MDS SAN-OS Release 3.3(5b)
3. Upgrade to MDS NX-OS Release 4.2(9)
4. Upgrade to MDS NX-OS Release 5.0(8a)
5. Upgrade to MDS NX-OS Release 5.2(8h)
6. Upgrade to MDS NX-OS Release 6.2(9)
7. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
Release 2.1(2), 2.1(1b), 2.1(1a), and 2.0(x)
1. Upgrade to MDS SAN-OS Release 2.1(2b), 2.1(2d), 2.1(2e), or 2.1(3)
2. Upgrade to MDS SAN-OS Release 3.3(1c)
3. Upgrade to MDS SAN-OS Release 3.3(5b)
4. Upgrade to MDS NX-OS Release 4.2(9)
5. Upgrade to MDS NX-OS Release 5.0(8a)
6. Upgrade to MDS NX-OS Release 5.2(8h)
7. Upgrade to MDS NX-OS Release 6.2(9)
8. Upgrade to MDS NX-OS Release 7.3(0)DY(1)
Release 1.x
1. Upgrade to MDS SAN-OS Release 1.3(4a)
2. Upgrade to MDS SAN-OS Release 2.1(2b)
3. Upgrade to MDS SAN-OS Release 3.3(1c)
4. Upgrade to MDS SAN-OS Release 3.3(5b)
5. Upgrade to MDS NX-OS Release 4.2(9)
6. Upgrade to MDS NX-OS Release 5.0(8a)
7. Upgrade to MDS NX-OS Release 5.2(8h)
8. Upgrade to MDS NX-OS Release 6.2(9)
9. Upgrade to MDS NX-OS Release7.3(0)DY(1)
Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 7.3(1)D1(1)
Use Table 4 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 7.3(1)D1(1). 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.
Upgrading from releases prior to Cisco MDS NX-OS Release 6.2(9) to Cisco MDS NX-OS Release 7.3(1)D1(1) is not supported. In such a scenario, we recommend that you first upgrade to Cisco MDS NX-OS Release 6.2(17) or higher and then upgrade to Cisco MDS NX-OS Release 7.3(1)D1(1).
ISSU from Cisco MDS NX-OS Release 7.3(0)DY(1) to Cisco MDS NX-OS Release 7.3(1)D1(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 Cisco MDS NX-OS Release 7.3(1)D1(1).
Nondisruptive Upgrade Path and Ordered Upgrade Steps
MDS NX-OS:
7.3(0)D1(1)
Upgrade directly to MDS NX-OS Release 7.3(1)D1(1)
7.3(0)DY(1)
1. Downgrade to MDS NX-OS Release 7.3(0)D1(1)
2. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
All 6.2(9) and above releases
Upgrade directly to MDS NX-OS Release 7.3(1)D1(1)
All 6.2(7) and earlier 6.2(x) releases
1. Upgrade to MDS NX-OS Release 6.2(9)
2. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
All 5.2(x) releases
1. Upgrade to MDS NX-OS Release 6.2(9)
2. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
All 5.0(x) releases
1. Upgrade to MDS NX-OS Release 5.2(8h)
2. Upgrade to MDS NX-OS Release 6.2(9)
3. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
All 4.2(x) releases and 4.1(x) releases
1. Upgrade to MDS NX-OS Release 5.0(8a)
2. Upgrade to MDS NX-OS Release 5.2(8h)
3. Upgrade to MDS NX-OS Release 6.2(9)
4. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
MDS SAN-OS:
Release 3.3(2), 3.3(3), 3.3(4x), and 3.3(5x).
1. Upgrade to MDS NX-OS Release 4.2(9)
2. Upgrade to MDS NX-OS Release 5.0(8a)
3. Upgrade to MDS NX-OS Release 5.2(8h)
4. Upgrade to MDS NX-OS Release 6.2(9)
5. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
Release 3.3(1c), all 3.2(x), 3.1(x), and 3.0(x) releases
1. Upgrade to MDS SAN-OS Release 3.3(5b)
2. Upgrade to MDS NX-OS Release 4.2(9)
3. Upgrade to MDS NX-OS Release 5.0(8a)
4. Upgrade to MDS NX-OS Release 5.2(8h)
5. Upgrade to MDS NX-OS Release 6.2(9)
6. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
Release 2.1(3), 2.1(2e), 2.1(2d), and 2.1(2b)
1. Upgrade to MDS SAN-OS Release 3.3(1c)
2. Upgrade to MDS SAN-OS Release 3.3(5b)
3. Upgrade to MDS NX-OS Release 4.2(9)
4. Upgrade to MDS NX-OS Release 5.0(8a)
5. Upgrade to MDS NX-OS Release 5.2(8h)
6. Upgrade to MDS NX-OS Release 6.2(9)
7. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
Release 2.1(2), 2.1(1b), 2.1(1a), and 2.0(x)
1. Upgrade to MDS SAN-OS Release 2.1(2b), 2.1(2d), 2.1(2e), or 2.1(3)
2. Upgrade to MDS SAN-OS Release 3.3(1c)
3. Upgrade to MDS SAN-OS Release 3.3(5b)
4. Upgrade to MDS NX-OS Release 4.2(9)
5. Upgrade to MDS NX-OS Release 5.0(8a)
6. Upgrade to MDS NX-OS Release 5.2(8h)
7. Upgrade to MDS NX-OS Release 6.2(9)
8. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
Release 1.x
1. Upgrade to MDS SAN-OS Release 1.3(4a)
2. Upgrade to MDS SAN-OS Release 2.1(2b)
3. Upgrade to MDS SAN-OS Release 3.3(1c)
4. Upgrade to MDS SAN-OS Release 3.3(5b)
5. Upgrade to MDS NX-OS Release 4.2(9)
6. Upgrade to MDS NX-OS Release 5.0(8a)
7. Upgrade to MDS NX-OS Release 5.2(8h)
8. Upgrade to MDS NX-OS Release 6.2(9)
9. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
Nondisruptive Upgrade Path to Cisco MDS NX-OS Release 7.3(0)D1(1)
Use Table 5 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 7.3(0)D1(1). 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.
Follow these general guidelines before you perform a software downgrade:
Issue the system no acl-adjacency-sharing user EXEC command to disable ACL adjacency usage on Generation 2 modules (Cisco MDS 9500 Directors). Generation 2 modules or switches can have one or more ports in port groups that share common resources such as bandwidth and buffer credits. If this command fails, reduce the number of zones, IVR zones, TE ports, or a combination of these in the system and issue the command again.
Disable all features that are not supported by the downgrade release. Use the show incompatibility system downgrade-image command to determine what you need to disable.
Use the show install all impact downgrade-image command to determine if your downgrade will be nondisruptive.
Be aware that some features impact whether a downgrade is disruptive or nondisruptive:
– Fibre Channel Ports : Fibre Channel ports can be nondisruptively downgraded without affecting traffic on the ports.
– Gigabit Ethernet Ports : Traffic on Gigabit Ethernet or IPStorage ports is disrupted during a downgrade. This includes the Gigabit Ethernet ports on the MDS 9000 16-Port Storage Services Node (SSN-16), IPStorage ports in MDS 9250i, MSM-18+4 module, and 24/10 Port SAN Extension Module. Nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the downgrade is in progress.
Find the NX-OS or SAN-OS image that you want to downgrade to in the To NX-OS or 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 the below tables applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP and intelligent services traffic.
Downgrading from Cisco MDS NX-OS Release 7.3(1)D1(1) to Cisco MDS NX-OS Release 7.3(0)D1(1) 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 the Cisco MDS NX-OS Release 7.3(0)D1(1) and later 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 7.3(1)D1(1) to Cisco MDS NX-OS Release 7.3(0)D1(1) is not supported on a Cisco MDS 9250i Switch which has only one online PSU.
Downgrading from Cisco MDS NX-OS Release 7.3(1)D1(1) to Cisco MDS NX-OS Release 7.3(0)D1(1) 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 7.3(1)D1(1) to Cisco MDS NX-OS Release 7.3(0)D1(1) 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.
Nondisruptive Downgrade Paths
Nondisruptive Downgrade Path to Cisco MDS NX-OS Release 7.3(1)DY(1)
Downgrading directly from Cisco MDS NX-OS Release 7.3(1)DY(1) to releases prior to 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 7.3(1)D1(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 7.3(1)D1(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).
Table 6 Nondisruptive Downgrade Path from NX-OS Release 7.3(1)DY(1)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Path and Ordered Downgrade Steps
NX-OS:
7.3(1)D1(1)
1. Downgrade to MDS NX-OS Release 7.3(0)D1(1)
2. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
7.3(0)D1(1)
Downgrade to MDS NX-OS Release 7.3(0)D1(1)
All 7.3(x) releases
Downgrade to MDS NX-OS Release 7.3(1)D1(1)
All 6.2(9) and above releases
Downgrade directly from NX-OS Release 7.3(1)DY(1)
All 6.2(9) and earlier releases
Downgrade to NX-OS Release 6.2(13a)
All 5.2(x) releases
Downgrade to NX-OS Release 6.2(13a)
All 5.0(x) releases
1. Downgrade to NX-OS Release 6.2(13a)
2. Downgrade to NX-OS Release 5.2(8h)
3. Downgrade to NX-OS Release 5.0(8a)
All 4.2(x) and 4.1(x) releases
1. Downgrade to NX-OS Release 6.2(13a)
2. Downgrade to NX-OS Release 5.2(8h)
3. Downgrade to NX-OS Release 5.0(8a)
4. Downgrade to NX-OS Release 4.2(x) or 4.1(x)
Nondisruptive Downgrade Path to Cisco MDS NX-OS Release 7.3(0)DY(1)
Downgrading directly from Cisco MDS NX-OS Release 7.3(0)DY(1) to releases prior to 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 7.3(0)DY(1) to Cisco MDS NX-OS Release 7.3(1)D1(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)D1(1).
Table 7 Nondisruptive Downgrade Path from NX-OS Release 7.3(0)DY(1)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Path and Ordered Downgrade Steps
NX-OS:
All 7.3(x) releases
1. Downgrade to MDS NX-OS Release 7.3(0)D1(1)
2. Upgrade to MDS NX-OS Release 7.3(1)D1(1)
All 6.2(9) and above releases
Downgrade directly from NX-OS Release 7.3(0)DY(1)
All 6.2(9) and earlier releases
Downgrade to NX-OS Release 6.2(13a)
All 5.2(x) releases
Downgrade to NX-OS Release 6.2(13a)
All 5.0(x) releases
1. Downgrade to NX-OS Release 6.2(13a).
2. Downgrade to NX-OS Release 5.2(8h).
3. Downgrade to NX-OS Release 5.0(8a).
All 4.2(x) and 4.1(x) releases
1. Downgrade to NX-OS Release 6.2(13a)
2. Downgrade to NX-OS Release 5.2(8h)
3. Downgrade to NX-OS Release 5.0(8a)
4. Downgrade to NX-OS Release 4.2(x) or 4.1(x)
Nondisruptive Downgrade Path to Cisco MDS NX-OS Release 7.3(1)D1(1)
Downgrading directly from Cisco MDS NX-OS Release 7.3(1)D1(1) to releases prior to 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(17) or higher and then downgrade to the required release.
Table 8 Nondisruptive Downgrade Path from NX-OS Release 7.3(1)D1(1)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Path and Ordered Downgrade Steps
NX-OS:
All 7.3(x) releases
Downgrade directly from NX-OS Release 7.3(1)D1(1)
All 6.2(9) and above releases
Downgrade directly from NX-OS Release 7.3(1)D1(1)
All 6.2(9) and earlier releases
Downgrade to NX-OS Release 6.2(17)
All 5.2(x) releases
Downgrade to NX-OS Release 6.2(17)
All 5.0(x) releases
1. Downgrade to NX-OS Release 6.2(17)
2. Downgrade to NX-OS Release 5.2(8h)
3. Downgrade to NX-OS Release 5.0(8a)
All 4.2(x) and 4.1(x) releases
1. Downgrade to NX-OS Release 6.2(17)
2. Downgrade to NX-OS Release 5.2(8h)
3. Downgrade to NX-OS Release 5.0(8a)
4. Downgrade to NX-OS Release 4.2(x) or 4.1(x)
Nondisruptive Downgrade Path to Cisco MDS NX-OS Release 7.3(0)D1(1)
Table 9 Nondisruptive Downgrade Path from NX-OS Release 7.3(0)D1(1)
To NX-OS or SAN-OS Release
Nondisruptive Downgrade Path and Ordered Downgrade Steps
New Hardware Features in Cisco MDS NX-OS Release 7.3(1)DY(1)
There are no new hardware features introduced in Cisco MDS NX-OS Release 7.3(1)DY(1).
New Software Features in Cisco MDS NX-OS Release 7.3(1)DY(1)
This section lists the new software features introduced in Cisco MDS NX-OS Release 7.3(1)DY(1).
FCIP Write Acceleration Support
Support for FCIP write acceleration on FCIP port channels between a Cisco MDS 9250i switch and a Cisco MDS 24/10 port SAN Extension Module in a Cisco MDS 9700 Director. For more information, see the Cisco MDS 9000 Series IP Services Configuration Guide.
IPSec Support on Cisco MDS 24/10 Port SAN Extension Module
This feature allows users to enhance the security of Cisco MDS Switches by automatically blocking login attempts when a possible denial-of-service (DoS) attack is detected. For more information, see the Cisco MDS 9000 Series Security Configuration Guide.
New Hardware Features in Cisco MDS NX-OS Release 7.3(0)DY(1)
This section lists the new hardware chassis and features introduced in Cisco MDS NX-OS Release 7.3(0)DY(1).
Cisco MDS 24/10 Port SAN Extension Module
The Cisco MDS 24/10 port SAN Extension Module is supported on Cisco MDS 9700 Series Multilayer Directors. This module provides a high performance, flexible, unified platform for deploying enterprise class disaster recovery and business continuance SAN extension solutions.
New Software Features in Cisco MDS NX-OS Release 7.3(0)DY(1)
This section lists the new software features introduced in Cisco MDS NX-OS Release 7.3(0)DY(1).
Configuring FCIP Tunnels for Maximum Performance on Cisco MDS 24/10 Port SAN Extension Module
This feature enables users to achieve maximum FCIP performance on Cisco 24/10 port SAN Extension Module. For detailed information about this feature, see the Cisco MDS 9000 Series IP Services Configuration Guide.
Changing Link Speed on Cisco MDS 24/10 Port SAN Extension Module
This feature enables users to change the link speed on IP Storage interfaces between 1 Gbps and 10 Gbps on Cisco MDS 24/10 port SAN Extension Module. For detailed information about this feature, see the Cisco MDS 9000 Series IP Services Configuration Guide.
FC-Redirect Support for Cisco MDS 9396S and Cisco MDS 9148S Switches.
New Hardware Features in Cisco MDS NX-OS Release 7.3(0)D1(1)
This section lists the new hardware chassis and features introduced in Cisco MDS NX-OS Release 7.3(0)D1(1).
Cisco MDS 9718 Director
The Cisco MDS 9718 Director has 18 slots for one or two supervisor modules and up to 16 I/O modules. The chassis also supports up to six fabric modules, up to 16 AC or DC 3 kW power supplies, and three fan trays.
Cisco MDS 24-Port 40-Gbps Fibre Channel Over Ethernet Module
The Cisco MDS 24-Port 40-Gigabit Fibre Channel over Ethernet (FCoE) Module (DS-X9824-960K9) provides Cisco Unified Fabric connectivity to the SAN fabric at 40 Gbps link speeds.
New Software Features in Cisco MDS NX-OS Release 7.3(0)D1(1)
This section lists the new software features introduced in Cisco MDS NX-OS Release 7.3(0)D1(1).
NX-API
NX-API is a Representational State Transfer (REST) API framework that allows programmatic access to a Cisco MDS switch over HTTP/HTTPS. NX-API provides the configuration and management capabilities of Cisco MDS NX-OS CLIs with web-based APIs, allowing users to control the Cisco MDS switch using a web browser.
Power on Auto Provisioning (POAP) is supported on Cisco MDS 9700 Series Switches. POAP automates the process of upgrading software images and installing configuration files on Cisco MDS Switches which are deployed in the network for the first time.
Power on Auto Provisioning (POAP) is facilitated on 9148S, 9250, 9300 Multilayer Fabric Switches and Cisco MDS 9700 and Cisco MDS 9500 Multilayer Director class switches with the presence of an USB device containing the configuration script file.
This feature introduces commands to test the health of interswitch links between Cisco MDS switches in a network with the help of the following 3 tests:
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 9148S 48-Port Multilayer Fabric Switch, the, and the Cisco MDS 9396S 96-Port Multilayer Fabric Switch.
Note A license is not required to use the Cisco MDS 24 Port 40 Gigabit Fibre Channel over Ethernet Module (DS-X9824-960K9), and the Cisco MDS 48 Port 10 Gigabit Fibre Channel over Ethernet Module (DS-X9848-480K9).
The standard software package that is bundled at no charge with the Cisco MDS 9000 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 Data Sheet for more information.
Note The IVR feature on Cisco MDS 9700 Series Directors with the Cisco MDS 24/10 port SAN Extension Module (DS-X9334-K9) requires an Enterprise package.
SAN Extension Over IP Package
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.
Note The FCIP feature on Cisco MDS 9700 Series Directors with the Cisco MDS 24/10 port SAN Extension Module (DS-X9334-K9) does not require a license.
Data Mobility Manager Package
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 theCisco MDS 9000 Data Mobility Manager License - Fact Sheet for more information. The Data Mobility Manager package is for use only with Cisco MDS 9000 Series switches.
On-Demand Port Activation License
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, and the Cisco MDS 9396S Multilayer Fabric Switch. As needed, customers can expand switch connectivity by licensing additional ports.
I/O Accelerator Package
The Cisco I/O Accelerator (IOA) package activates IOA 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.
Deprecated and Changed Features
Zoning Features
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.
Starting from Cisco MDS NX-OS Release 7.3(0)D1(1), the following hardware modules are not supported:
Cisco MDS 4-Gbps Fabric Switch for HP c-Class BladeSystem
Cisco MDS 4-Gbps Fabric Switch for IBM BladeCenter
Limitations and Restrictions
The following limitations are described:
Pause Frame Timeout and Congestion Frame Timeout Support
The Cisco MDS 24 port 40 Gigabit FCoE (DS-X9824-960K9) Module does not support the Pause Frame Timeout and Congestion Frame Timeout features.
FCIP Support
In Cisco MDS NX-OS Releases 7.3(0)DY(1) and 7.3(1)DY(1), FCIP Write Acceleration is not supported between 24/10 San Extension Module and Cisco 18+4 MSM and Cisco SSN16 Modules.
In Cisco MDS NX-OS Releases 7.3(0)DY(1) and 7.3(1)DY(1), 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.
In Cisco MDS NX-OS Releases 7.3(0)DY(1) and 7.3(1)DY(1), Write Acceleration on FCIP port channels should not be configured between two MDS 9700 Series switches with Cisco MDS 24/10 port SAN Extension Module under the following conditions:
If traffic flows between an FCoE port and an FC port through an FCIP port channel.
If traffic flows between an FCIP port and an FC port through an FCIP port channel.
40GE IP Storage Interfaces Support
In Cisco MDS NX-OS Releases 7.3(0)DY(1) and 7.3(1)DY(1), 40GE IP Storage Interfaces are not supported.
iSCSI Support
In Cisco MDS NX-OS Release 7.3(0)DY(1), iSCSI is not supported on the Cisco MDS 9700 Directors with Cisco MDS 24/10 port SAN Extension Modules.
DS-CAC-1200W Power Supply Unit
In Cisco MDS NX-OS Release 7.3(0)DY(1) and 7.3(1)DY(1), DS-CAC-1200W power supply unit and DS-C96S-FAN-I as port side intake fan tray are not supported on the Cisco MDS 9396S Switch.
No traffic sent across an FCIP interface with tcp max-bandwidth-mbps 33 or less.
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:
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:
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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)