HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 14

Upgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] Step 4 Follow the onscreen instructions to complete the installation of Device Manager. Note If you use a Java JDK instead of a JRE on Solaris, you might encounter a problem trying to install the Device Manager from a web browser. This can happen because the installer heap limit of 256 MB is not sufficient. If you have this problem, save the jnlp link as file, increase the heap limit to 512 MB, and run javaws element-manager.jnlp at the shell prompt. General Upgrading Guidelines Use the following guidelines when upgrading to Cisco MDS SAN-OS Release 3.3(3): • Install and configure dual supervisor modules. • Issue the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive. • Follow the recommended guidelines for upgrading a Cisco MDS 9124 Switch as described in "Upgrading a Cisco MDS 9124 Switch" section on page 21. • Follow the guidelines for upgrading a single supervisor switch as described in "Performing a Disruptive Upgrade on a Single Supervisor MDS Family Switch" section on page 22. • Be aware that some features impact whether an upgrade is disruptive or nondisruptive: - Fibre Channel Ports: Traffic on Fibre Channel ports can be nondisruptively upgraded. See Table 6 for the nondisruptive upgrade path for all SAN-OS releases. - SSM: Intelligent services traffic on the SSM, such as SANTap, NASB, and FC write acceleration, is disrupted during an upgrade. SSM Fibre Channel traffic is not. - Gigabit Ethernet Ports: Traffic on Gigabit Ethernet ports is disrupted during an upgrade or downgrade. This includes IPS modules and the Gigabit Ethernet ports on the MPS-14/2 module, the MSM-18/4 module, and the MDS 9222i switch. 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 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 17 for these instructions. - FICON: If you have FICON enabled, the upgrade path is different. See Table 7. Use Table 6 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.3(3). Find the image release number you are currently using in the Current column of the table and use the path recommended. Note On an MDS 9222i switch, an upgrade from SAN-OS Release 3.2(x), Release 3.3(1a), or Release 3.3(1c) to SAN-OS Release 3.3(3) fails when there is an active FC-Redirect configuration (created by Cisco SME or Cisco DMM applications) on the switch. An active FC-Redirect configuration is defined as: Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3) 14 OL-14116-11