HP Cisco MDS 8/24c Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Rel - Page 19

Upgrading Your Cisco MDS NX-OS Software Image Send documentation comments to [email protected] Table 13 FICON Nondisruptive Upgrade Path to MDS NX-OS Release 4.2(1b) (continued) Current Release with FICON Enabled Upgrade Path SAN-OS 3.2(2c) SAN-OS 3.0(3b) First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS Release 4.2(1b). SAN-OS 3.0(3) SAN-OS 3.0(2) SAN-OS 2.0(2b) 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.3(1c). 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. SAN-OS 1.x 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 Effect on VSAN 4079 If you upgrade to NX-OS Release 5.0(4b), and you have not created VSAN 4079, the NX-OS software will automatically create VSAN 4079 and reserve it for EVFP use. If VSAN 4079 is reserved for EVFP use, the switchport trunk allowed vsan command will filter out VSAN 4079 from the allowed list. In the following example, the allowed list appears on a separate line following the command: switch(config-if)# switchport trunk allowed vsan 1-4080 1-4078,4080 switch(config-if)# If you have created VSAN 4079, the upgrade to NX-OS Release 5.0(4b) will have no affect on VSAN 4079. If you downgrade to a release of NX-OS lower than NX-OS Release 4.1(x) after NX-OS Release 5.0(4b) creates VSAN 4079 and reserves it for EVFP use, the VSAN will no longer be reserved. 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. OL-21012-04 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4b) 19