HP Cisco MDS 9120 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Rel - Page 18

Downgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] - Fibre Channel Ports: Traffic on Fibre Channel ports can be nondisruptively downgraded. See Table 6 for the nondisruptive downgrade path for all SAN-OS releases. - SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write acceleration, is disrupted during a downgrade. SSM Fibre Channel traffic is not. - Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during a downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module. Those nodes that are members of VSANs traversing an FCIP ISL are impacted, and a fabric reconfiguration occurs. iSCSI initiators connected to the Gigabit Ethernet ports lose connectivity to iSCSI targets while the downgrade is in progress. - iSCSI: If you are downgrading from SAN-OS version 3.0(x) to a lower version of SAN-OS, enable iSCSI if an IPS module or a MPS-14/2 module is online in the switch. Otherwise, the downgrade will disrupt traffic. - 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 13 for these instructions. - FICON: If you have FICON enabled, the downgrade path is different. See Table 7. - iSNS: The iSNS feature does not support a graceful downgrade from Cisco MDS SAN-OS Release 3.1(2a) to any earlier SAN-OS release. Prior to a downgrade from Cisco SAN-OS 3.1(2a), disable the MDS iSNS server and remove all configurations associated with the MDS iSNS client. Use Table 6 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.1(2a). 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 6 applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP and SSM intelligent services traffic. Table 6 Nondisruptive Downgrade Path from SAN-OS Release 3.1(2a) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 3.1(2) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 3.1(1) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 3.0(3a) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 3.0(3) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 3.0(2a) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 3.0(2) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 3.0(1) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 2.1(3) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 2.1(2e) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 2.1(2d) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). SAN-OS 2.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2a). 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). Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(2a) 18 OL-12208-03