Downgrading Your Cisco MDS SAN-OS Software Image
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Note
A downgrade from NX-OS Release 4.2(1a) to SAN-OS Release 3.3(1x) is not supported on MDS
switches, when FC-Redirect based applications, such as Data Mobility Manager or Storage Media
Encryption, are configured in the fabric if either of the following conditions are satisfied:
A target for which FC-Redirect is configured is connected locally and there are Generation 1
1.
modules with ISLs configured in the switch.
A host, for which FC-redirect is configured, is connected locally on a Generation 1 module.
2.
If these conditions exist, remove the application configuration for these targets and hosts before
proceeding with the downgrade.
Use
Table 11
the SAN-OS image you want to downgrade to in the To SAN-OS Release column of the table and use
the path recommended.
Note
The software downgrade information in
Downgrading system software disrupts IP and SSM intelligent services traffic.
Table 11
To SAN-OS Release Nondisruptive Downgrade Path
NX-OS 4.1(3a)
NX-OS 4.1(1c)
NX-OS 4.1(1b)
SAN-OS 3.3(4)
SAN-OS 3.3(3)
SAN-OS 3.3(2)
SAN-OS 3.3(1c)
SAN-OS 3.3(1a)
SAN-OS 3.2(3a)
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a)
24
SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write
–
acceleration, is disrupted during a downgrade. SSM Fibre Channel traffic is not.
–
Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during a downgrade.
This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module, the
MSM-18/4 module, and the MDS 9222i switch. Those nodes that are members of VSANs
traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators
connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the downgrade
is in progress.
IVR: With IVR enabled, you must follow additional steps if you are downgrading from Cisco
–
SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the
on page 19
for these instructions.
–
FICON: If you have FICON enabled, the downgrade path is different. See the
Downgrade Paths" section on page
to determine the nondisruptive downgrade path from Cisco NX-OS Release 4.2(1a). Find
Nondisruptive Downgrade Path from NX-OS Release 4.2(1a)
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
Downgrade to SAN-OS Release 3.3(x) first and then downgrade to Release
3.2(3a).
"Upgrading with IVR Enabled" section
26.
Table 11
applies only to Fibre Channel switching traffic.
"FICON
OL-19964-02
Друкувати сторінку