HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Re - Page 20

Upgrading Your Cisco MDS NX-OS Software Image Send documentation comments to mdsfeedback-doc.com. 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 upgrade is in progress. - Inter-VSAN Routing (IVR): With IVR enabled, you must follow additional steps if you are upgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or 2.1.(2a). See the "Upgrading with IVR Enabled" section on page 23 for these instructions. - FICON: If you have FICON enabled, the upgrade path is different. See Table 11. Use Table 10 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 4.1(3a), find the image release number you are currently using in the Current column of the table, and use the path recommended. Note The software upgrade information in Table 10 applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and SSM intelligent services traffic. Upgrading an MDS 9222i Switch with SANTap or Invista is Provisioned on the SSM On an MDS 9222i switch, if SANTap or Invista is provisioned on a Storage Services Module (SSM) in slot 2, then an In Service Software Upgrade (ISSU) to NX-OS Release 4.1(3a) is not supported. The upgrade to NX-OS Release 4.1(3a) is supported if you set boot variables, save the configuration, and reload the switch. If the switch is running SAN-OS Release 3.3(1a) or earlier, first upgrade to SAN-OS Release 3.3(1c) and then upgrade to NX-OS Release 4.1(3a). Enabling Telnet Required After an Upgrade Following an upgrade from SAN-OS 3.x to NX-OS 4.x, you need to enable the Telnet server if you require a Telnet connection. As of MDS NX-OS Release 4.1(1b), the Telnet server is disabled by default on all switches in the Cisco MDS 9000 Family. In earlier releases, the Telnet server was enabled by default. Upgrading Effect on VSAN 4079 If you are upgrading from a SAN-OS Release 3.x to NX-OS Release 4.1(3a), 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, as shown in the following example: 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 4.1(3a) will have no affect on VSAN 4079. If you downgrade after NX-OS Release 4.1(3) creates VSAN 4079 and reserves it for EVFP use, the VSAN will no longer be reserved. Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a) 20 OL-17675-05