HP Cisco MDS 9216A Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Re - Page 19

Downgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] Table 6 Nondisruptive Downgrade Path from SAN-OS Release 3.1(2a) To SAN-OS Release Nondisruptive Downgrade Path 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. Use Table 7 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.1(2a). 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. Note Cisco MDS SAN-OS Release 3.1(2a) is not FICON certified. Table 7 FICON Downgrade Path from SAN-OS 3.1(2a) To SAN-OS Release with FICON Enabled SAN-OS 3.0(2) SAN-OS 2.0(2b) SAN-OS 1.3(4a) Downgrade Path You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). 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.1(2a) to 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.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). Downgrading the SSI Image on Your SSM Use the following guidelines when downgrading your SSI image on your SSM. • On a system with at least one SSM installed, the install all command might fail on an SSM when you downgrade from Cisco SAN-OS Release 3.1(2a) to any SAN-OS 2.x release earlier than SAN-OS Release 2.1(2e). Power down the SSM and perform the downgrade. Bring up the SSM with the new bootvar set to the 2.x SSI image. OL-12208-03 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(2a) 19