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

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

Page 15 highlights

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

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