HP Cisco MDS 9216A Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Rel - Page 20

Gigabit Ethernet Ports, Inter-VSAN Routing IVR, FICON, Upgrading with, IVR Enabled

Page 20 highlights

Upgrading Your Cisco MDS NX-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 23 for these instructions. - FICON: If you have FICON enabled, the upgrade path is different. See Table 12. Use Table 11 to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 4.1(1b), 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(1), or Release 3.3(1a) to Cisco MDS NX-OS Release 4.1 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 On an MDS 9222i switch, if SANTap or Invista is provisioned on a Storage Services Module (SSM) in slot2, then an In Service Software Upgrade (ISSU) to NX-OS Release 4.1(1b) is not supported. The upgrade to NX-OS Release 4.1(1b) 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(1b). Note The software upgrade information in Table 11 applies only to Fibre Channel switching traffic. Upgrading system software disrupts IP traffic and SSM intelligent services traffic. Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(1b) 20 OL-17675-02

  • 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
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66

Send documentation comments to [email protected]
20
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(1b)
OL-17675-02
Upgrading Your Cisco MDS NX-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 23
for these instructions.
FICON
: If you have FICON enabled, the upgrade path is different. See
Table 12
.
Use
Table 11
to determine your nondisruptive upgrade path to Cisco MDS NX-OS Release 4.1(1b), 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(1), or Release 3.3(1a)
to Cisco MDS NX-OS Release 4.1 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
On an MDS 9222i switch, if SANTap or Invista is provisioned on a Storage Services Module (SSM) in
slot2, then an In Service Software Upgrade (ISSU) to NX-OS Release 4.1(1b) is not supported. The
upgrade to NX-OS Release 4.1(1b) 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(1b).
Note
The software upgrade information in
Table 11
applies only to Fibre Channel switching traffic.
Upgrading system software disrupts IP traffic and SSM intelligent services traffic.