Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2) (OL-14116-10 C0, November 2008)

Send documentation comments to [e-mail]
25
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Downgrading Your Cisco MDS SAN-OS Software Image
Use Table 10 to determine your nondisruptive downgrade path, if you have FICON enabled, from Cisco
SAN-OS Release 3.3(2). Find the image release number you are currently using in the Current Release
with FICON Enabled column of the table and use the path recommended.
SAN-OS 2.1(2d) You can nondisruptively downgrade directly from SAN-OS Release 3.3(2).
SAN-OS 2.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.3(2).
SAN-OS 2.1(2) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(2).
SAN-OS 2.1(1b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1b).
SAN-OS 2.1(1a) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1a).
SAN-OS 2.0(4a) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4a).
SAN-OS 2.0(4) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4).
SAN-OS 2.0(3) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(3).
SAN-OS 2.0(2b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(2b).
SAN-OS 2.0(1b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(1b).
SAN-OS 1.x Downgrade to SAN-OS to Release 2.1(2b), then to Release 1.3(4a), and then
downgrade to your SAN-OS 1.x release.
Table 9 Nondisruptive Downgrade Path from SAN-OS Release 3.3(2)
To SAN-OS Release Nondisruptive Downgrade Path
Table 10 FICON Downgrade Path from SAN-OS 3.3(2)
To SAN-OS Release with FICON Enabled Downgrade Path
SAN-OS 3.0(3b) You can nondisruptively downgrade directly from SAN-OS Release 3.3(2).
SAN-OS 3.0(2) You can nondisruptively downgrade directly from SAN-OS Release 3.3(2).
SAN-OS 2.0(2b) Use the interface shutdown command to administratively shut any Fibre
Channel ports on Generation 1 modules that are in an operationally down
state before nondisruptively downgrading from SAN-OS Release 3.3(2) to
SAN-OS Release 3.0(3b) or SAN-OS Release 3.0(2), and then to SAN-OS
Release 2.0(2b). An operationally down state includes
Link failure or
not-connected, SFP not present
, or Error Disabled status in the output
of a show interface command. When an interface is administratively shut it
will then show as
Administratively down. Interfaces that are currently up
or trunking do not need to be shut down.
SAN-OS 1.3(4a) Downgrade to SAN-OS Release 3.0(2). Use the shutdown command to shut
all the ports operationally down and administratively up on all the
Generation 1 modules before nondisruptively downgrading to Release
2.0(2b) and then downgrade to 1.3(4a).