HP Cisco MDS 9124 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Rel - Page 15
Upgrading an MDS 9216 Switch with iSCSI Enabled, Upgrading with IVR Enabled, Current Release
View all HP Cisco MDS 9124 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 15 highlights
Upgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] Table 6 FICON Nondisruptive Upgrade Path to SAN-OS 3.2(1a) Current Release with FICON Enabled SAN-OS 2.0(2b) SAN-OS 1.x Upgrade Path 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 upgrading from SAN-OS Release 2.0(2b) to SAN-OS Release 3.0(2) or SAN-OS Release 3.0(3b), and then upgrade to Release 3.2(1a). 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. Upgrade to SAN-OS Release 3.0(2). Use the interface shutdown command to shut all the ports operationally down and administratively up on all the Generation 1 modules before nondisruptively upgrading to Release 2.0(2b) and then upgrade to 1.3(4a). Upgrading an MDS 9216 Switch with iSCSI Enabled Following a software upgrade to Cisco SAN-OS Release 3.2(1a) on a Cisco MDS 9216, 9216A, or 9216i Switch, you need to enable iSCSI on all modules where iSCSI interfaces were present before the upgrade. Use the iscsi enable module slot-number command to enable iSCSI, then issue the copy running-config startup-config command to have the configuration take effect. Upgrading with IVR Enabled An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive. Some possible scenarios include the following: • FCIP connection flapping during the upgrade process resulting in fabric segmentation or merge. • ISL flap results in fabric segmentation or merge because of hardware issues or a software bug. • ISL port becomes part of PCP results in fabric segmentation or merge because of a port flap. If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state because of a domain overlap. This issue was resolved in Cisco SAN-OS Release 2.1(2b); therefore, you must upgrade to Release 2.1(2b) before upgrading to Release 3.2(1a). An upgrade from Cisco SAN-OS Releases 2.1(1a), 2.1(1b), or 2.1(2a) to Release 2.1(2b) when IVR is enabled requires that you follow the procedure below, and OL-14116-02 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1a) 15