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

General Upgrading Guidelines

Page 15 highlights

Upgrading Your Cisco MDS NX-OS Software Image Send documentation comments to [email protected] To migrate to IVR-NAT mode, follow these steps: 1. Stop or divert all applications on servers that depend on IVR. - If CFS distribution is not enabled for IVR, then perform steps 2 through 4 on all switches where IVR is enabled. - If CFS distribution is enabled for IVR, then enter the ivr commit command following step 2, step 3, and step 4 to distribute the changes to other switches. 2. Deactivate the IVR zone set by entering the no ivr zoneset activate command. 3. Enable IVR NAT by entering the ivr nat command. 4. Activate the IVR zone set by entering the ivr zoneset activate command. 5. Start or re-establish all application that were stopped in step 1. The network can now run in IVR-NAT mode. General Upgrading Guidelines Follow these general guidelines before performing a software upgrade: • Review the nondisruptive upgrade path to release 5.2(1) in Table 10. • Install and configure dual supervisor modules before the upgrade. • Issue the show install all impact upgrade-image CLI command to determine if your upgrade will be nondisruptive. • Be aware that some features impact whether an upgrade is disruptive or nondisruptive: - Fibre Channel Ports: Fibre Channel ports can be nondisruptively upgraded without affecting traffic on the ports. See Table 10 for the nondisruptive upgrade path for all NX-OS and SAN-OS releases. - 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 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. - FICON: If you have FICON enabled, the upgrade path is different. See the "FICON Supported Releases and Upgrade Paths" section on page 17. Note In addition to these guidelines, you may want to review the information in the "Limitations and Restrictions" section prior to a software upgrade to determine if a feature may possibly behave differently following the upgrade. Use Table 10 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 5.2(1), 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 intelligent services traffic. OL-25090-01 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1) 15

  • 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

Send documentation comments to [email protected]
15
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1)
OL-25090-01
Upgrading Your Cisco MDS NX-OS Software Image
To migrate to IVR-NAT mode, follow these steps:
1.
Stop or divert all applications on servers that depend on IVR.
If CFS distribution is not enabled for IVR, then perform steps 2 through 4 on all switches where
IVR is enabled.
If CFS distribution is enabled for IVR, then enter the
ivr commit
command following step 2,
step 3, and step 4 to distribute the changes to other switches.
2.
Deactivate the IVR zone set by entering the
no ivr zoneset activate
command.
3.
Enable IVR NAT by entering the
ivr nat
command.
4.
Activate the IVR zone set by entering the
ivr zoneset activate
command.
5.
Start or re-establish all application that were stopped in step 1.
The network can now run in IVR-NAT mode.
General Upgrading Guidelines
Follow these general guidelines before performing a software upgrade:
Review the nondisruptive upgrade path to release 5.2(1) in
Table 10
.
Install and configure dual supervisor modules before the upgrade.
Issue the
show install all impact
upgrade-image
CLI command to determine if your upgrade will
be nondisruptive.
Be aware that some features impact whether an upgrade is disruptive or nondisruptive:
Fibre Channel Ports
:
Fibre Channel ports
can be nondisruptively upgraded without affecting
traffic on the ports. See
Table 10
for the nondisruptive upgrade path for all NX-OS and SAN-OS
releases.
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 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.
FICON
: If you have FICON enabled, the upgrade path is different. See the
“FICON Supported
Releases and Upgrade Paths” section on page 17
.
Note
In addition to these guidelines, you may want to review the information in the
“Limitations and
Restrictions”
section prior to a software upgrade to determine if a feature may possibly behave
differently following the upgrade.
Use
Table 10
to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 5.2(1), 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 intelligent services traffic.