HP Cisco MDS 9120 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Rel - Page 14

Current, Nondisruptive Upgrade Path, Table 6, Nondisruptive Upgrade Path to SAN-OS Release 3.21

Page 14 highlights

Upgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] - 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. 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. - 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 16 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.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 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.2(1) Current Nondisruptive Upgrade Path SAN-OS 3.1(4) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.1(3a) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.1(2b) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.1(2a) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.1(2) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.1(1) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.0(3a) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.0(3) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.0(2a) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.0(2) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 3.0(1) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 2.1(3) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 2.1(2e) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 2.1(2d) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 2.1(2b) You can nondisruptively upgrade directly to SAN-OS Release 3.2(1). SAN-OS 2.1(2) Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.2(1). or Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.2(1). or. Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.2(1). or Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.2(1). Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1) 14 OL-14116-01

  • 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]
14
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1)
OL-14116-01
Upgrading Your Cisco MDS SAN-OS Software Image
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.
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.
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 16
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.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 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.2(1)
Current
Nondisruptive Upgrade Path
SAN-OS 3.1(4)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.1(3a)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.1(2b)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.1(2a)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.1(2)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.1(1)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.0(3a)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.0(3)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.0(2a)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.0(2)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 3.0(1)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 2.1(3)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 2.1(2e)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 2.1(2d)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 2.1(2b)
You can nondisruptively upgrade directly to SAN-OS Release 3.2(1).
SAN-OS 2.1(2)
Upgrade to SAN-OS Release 2.1(2b) and then upgrade to Release 3.2(1).
or
Upgrade to SAN-OS Release 2.1(2d) and then upgrade to Release 3.2(1).
or.
Upgrade to SAN-OS Release 2.1(2e) and then upgrade to Release 3.2(1).
or
Upgrade to SAN-OS Release 2.1(3) and then upgrade to Release 3.2(1).