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
Table 11
To SAN-OS Release Nondisruptive Downgrade Path
SAN-OS 2.0(4)
SAN-OS 2.0(3)
SAN-OS 2.0(2b)
SAN-OS 2.0(1b)
SAN-OS 1.x
FICON Downgrade Paths
Table 12
downgrade to in the
downgrade path.
Table 12
FICON Downgrade Path from NX-OS Release 4.1(1c)
To Release with FICON Enabled
NX-OS 4.1(1c)
SAN-OS 3.3(1c)
SAN-OS 3.2(2c)
SAN-OS 3.0(3b)
SAN-OS 3.0(2)
SAN-OS 2.0(2b)
SAN-OS 1.3(4a)
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a)
26
Nondisruptive Downgrade Path from NX-OS Release 4.2(1a) (continued)
Downgrade to SAN-OS Release 3.3(x) first, then to Release 2.1(2x), and then
downgrade to Release 2.0(4).
Downgrade to SAN-OS Release 3.3(x) first, then to Release 2.1(2x), and then
downgrade to Release 2.0(3).
Downgrade to SAN-OS Release 3.3(x) first, then to Release 2.1(2x), and then
downgrade to Release 2.0(2b).
Downgrade to SAN-OS Release 3.3(x) first, then to Release 2.1(2x), and then
downgrade to Release 2.0(1b).
Downgrade to SAN-OS Release 3.3(x) first, 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.
lists the downgrade paths for FICON releases. Find the image release number that you want to
To Release with FICON Enabled
Downgrade Path
You can nondisruptively downgrade directly from NX-OS Release 4.2(1a).
You can nondisruptively downgrade directly from NX-OS Release 4.1(1c).
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.2(2c).
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.0(3b).
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.0(2).
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
Error Disabled
an interface is administratively shut it will then show as
. Interfaces that are currently up or trunking do not need to be shut
down
down.
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).
column of the table and follow the recommended
Link failure or not-connected, SFP not present
status in the output of a show interface command. When
, or
Administratively
OL-19964-02
Print Page