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

General Upgrading Guidelines, Cisco Device Manager, javaws element-manager.jnlp

Page 19 highlights

Upgrading Your Cisco MDS NX-OS Software Image Send documentation comments to mdsfeedback-doc.com. Step 1 Step 2 Step 3 Step 4 Enter the IP address of the switch in the Address field of your browser. Click the Cisco Device Manager link in the Device Manager installation window. Click Next to begin the installation. 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 Note To upgrade to NX-OS Release 4.1(3a) from SAN-OS Release 3.2(3a) or earlier, first upgrade to SAN-OS Release 3.3(1x) and then upgrade to NX-OS Release 4.1(3a). Use the following guidelines when upgrading to Cisco MDS NX-OS Release 4.1(x): • Install and configure dual supervisor modules. • Issue the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive. • Be aware that you need to enable Telnet following the upgrade. See "Enabling Telnet Required After an Upgrade" section on page 20. • Follow the recommended guidelines for upgrading a Cisco MDS 9124 or MDS 9134 Switch as described in "Upgrading a Cisco MDS 9124 or Cisco MDS 9134 Switch" section on page 27. • 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 28. • Make note of the information concerning SANTap when performing upgrades on a Cisco MDS 9222i switch, as described in "Upgrading an MDS 9222i Switch with SANTap or Invista is Provisioned on the SSM" section on page 20. • Be aware of the impact of an upgrade on VSAN 4079 if you are upgrading from SAN-OS Release 3.x to NX-OS 4.1(3a). See the "Upgrading Effect on VSAN 4079" section on page 20 for details. • 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 10 for the nondisruptive upgrade path for all NX-OS and 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 OL-17675-05 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a) 19

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54

Send documentation comments to mdsfeedback-doc.com.
19
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a)
OL-17675-05
Upgrading Your Cisco MDS NX-OS Software Image
Step 1
Enter the IP address of the switch in the Address field of your browser.
Step 2
Click the
Cisco Device Manager
link in the Device Manager installation window.
Step 3
Click
Next
to begin the installation.
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
Note
To upgrade to NX-OS Release 4.1(3a) from SAN-OS Release 3.2(3a) or earlier, first upgrade to SAN-OS
Release 3.3(1x) and then upgrade to NX-OS Release 4.1(3a).
Use the following guidelines when upgrading to Cisco MDS NX-OS Release 4.1(x):
Install and configure dual supervisor modules.
Issue the
show install all impact
upgrade-image
CLI command to determine if your upgrade will
be nondisruptive.
Be aware that you need to enable Telnet following the upgrade. See
“Enabling Telnet Required After
an Upgrade” section on page 20
.
Follow the recommended guidelines for upgrading a Cisco MDS 9124 or MDS 9134 Switch as
described in
“Upgrading a Cisco MDS 9124 or Cisco MDS 9134 Switch” section on page 27
.
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 28
.
Make note of the information concerning SANTap when performing upgrades on a Cisco MDS
9222i switch, as described in
“Upgrading an MDS 9222i Switch with SANTap or Invista is
Provisioned on the SSM” section on page 20
.
Be aware of the impact of an upgrade on VSAN 4079 if you are upgrading from SAN-OS Release
3.x to NX-OS 4.1(3a). See the
“Upgrading Effect on VSAN 4079” section on page 20
for details.
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 10
for the nondisruptive upgrade path for all NX-OS and 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