Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1a) (OL14116-02, October 2007)

Send documentation comments to mdsfeedback-doc@cisco.com
21
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1a)
OL-14116-02
Downgrading Your Cisco MDS SAN-OS Software Image
IVR: With IVR enabled, you must follow additional steps if you are downgrading from Cisco
SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the “Upgrading with IVR Enabled” section
on page 15 for these instructions.
FICON: If you have FICON enabled, the downgrade path is different. See Table 8.
iSNS: The iSNS feature does not support a graceful downgrade from Cisco MDS SAN-OS
Release 3.2(1a) to any earlier SAN-OS release. Prior to a downgrade from Cisco SAN-OS
3.2(1a), disable the MDS iSNS server and remove all configurations associated with the MDS
iSNS client.
Use Table 7 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.2(1a). Find
the SAN-OS image you want to downgrade to in the To SAN-OS Release column of the table and use
the path recommended.
Note The software downgrade information in Table 7 applies only to Fibre Channel switching traffic.
Downgrading system software disrupts IP and SSM intelligent services traffic.
Table 7 Nondisruptive Downgrade Path from SAN-OS Release 3.2(1a)
To SAN-OS Release Nondisruptive Downgrade Path
SAN-OS 3.2(1) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.1(4) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.1(3a) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.1(2a) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.1(2) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.1(1) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.0(3a) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.0(3) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.0(2a) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.0(2) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 3.0(1) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 2.1(3) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 2.1(2e) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 2.1(2d) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
SAN-OS 2.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1a).
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).