Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4) (OL-21012-02, November 2010)

Send documentation comments to [e-mail]
24
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4)
OL-21012-02
Downgrading Your Cisco MDS SAN-OS Software Image
FICON Downgrade Paths
Table 14 lists the downgrade paths for FICON releases. Find the image release number that you want to
downgrade to in the To Release with FICON Enabled column of the table and follow the recommended
downgrade path.
2.0(4a)
2.0(4)
2.0(3)
2.0(2b)
2.0(1b)
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade
to SAN-OS Release 3.3(x), then downgrade to Release 2.1(2x), and then
downgrade to Release 2.0(x).
1.x Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade
to SAN-OS Release 3.3(x), then 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 13 Nondisruptive Downgrade Path from NX-OS Release 5.0(4) (continued)
To NX-OS or SAN-OS
Release Nondisruptive Downgrade Path
Table 14 FICON Downgrade Path from NX-OS Release 4.1(1c)
To Release with FICON Enabled Downgrade Path
SAN-OS 3.3(1c) You can nondisruptively downgrade directly from NX-OS Release 4.1(1c).
SAN-OS 3.2(2c) First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.2(2c).
SAN-OS 3.0(3b) First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.0(3b).
SAN-OS 3.0(2) First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.0(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 NX-OS Release 4.1 to
SAN-OS Release 3.3(1c) then 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.3(1c) and then to 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).