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

Current, Nondisruptive Upgrade Path, Gigabit Ethernet Ports, Inter-VSAN Routing IVR, FICON

Page 15 highlights

Upgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] - 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 the "FICON Supported Releases and Upgrade Paths" section on page 17. Use Table 6 to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.3(4a). 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(4a) 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: • FC-Redirect configuration for hosts or target connected locally • FC-Redirect configuration created by application running on that switch. If an upgrade is attempted when an active configurations is present, the switch will go into a disruptive upgrade. Note The software upgrade information in Table 6 applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and SSM intelligent services traffic. Table 6 Nondisruptive Upgrade Path to SAN-OS Release 3.3(4a) Current Nondisruptive Upgrade Path SAN-OS 3.3(4) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.3(3) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.3(2) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.3(1c) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.3(1a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.2(3a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.2(3) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.2(2c) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.2(1a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.1(4) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.1(3a) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). SAN-OS 3.1(2b) You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a). OL-14116-13 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4a) 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

Send documentation comments to [email protected]
15
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4a)
OL-14116-13
Upgrading Your Cisco MDS SAN-OS Software Image
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 the
“FICON Supported
Releases and Upgrade Paths” section on page 17
.
Use
Table 6
to determine your nondisruptive upgrade path to Cisco SAN-OS Release 3.3(4a). 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(4a) 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:
FC-Redirect configuration for hosts or target connected locally
FC-Redirect configuration created by application running on that switch.
If an upgrade is attempted when an active configurations is present, the switch will go into a disruptive
upgrade.
Note
The software upgrade information in
Table 6
applies only to Fibre Channel switching traffic. Upgrading
system software disrupts IP traffic and SSM intelligent services traffic.
Table 6
Nondisruptive Upgrade Path to SAN-OS Release 3.3(4a)
Current
Nondisruptive Upgrade Path
SAN-OS 3.3(4)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.3(3)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.3(2)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.3(1c)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.3(1a)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.2(3a)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.2(3)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.2(2c)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.2(1a)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.1(4)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.1(3a)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).
SAN-OS 3.1(2b)
You can nondisruptively upgrade directly to SAN-OS Release 3.3(4a).