HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Re - Page 26

Downgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] Table 11 Nondisruptive Downgrade Path from NX-OS Release 4.2(1a) (continued) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 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(4). SAN-OS 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(3). SAN-OS 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(2b). SAN-OS 2.0(1b) Downgrade to SAN-OS Release 3.3(x) first, then to Release 2.1(2x), and then downgrade to Release 2.0(1b). SAN-OS 1.x 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. FICON Downgrade Paths Table 12 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. 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) 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 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. 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). Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a) 26 OL-19964-02