HP Cisco MDS 9020 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Rel - Page 22

To SAN-OS Release, Nondisruptive Downgrade Path, Table 8

Page 22 highlights

Downgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] - IVR: With IVR enabled, you must follow additional steps if you are downgrading 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 downgrade path is different. See Table 9. - iSNS: The iSNS feature does not support a graceful downgrade from Cisco MDS SAN-OS Release 3.2(1) to any earlier SAN-OS release. Prior to a downgrade from Cisco SAN-OS 3.2(1), disable the MDS iSNS server and remove all configurations associated with the MDS iSNS client. Use Table 8 to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.2(1). Find the SAN-OS image you want to downgrade to in the To SAN-OS Release column of the table and use the path recommended. Note The software downgrade information in Table 8 applies only to Fibre Channel switching traffic. Downgrading system software disrupts IP and SSM intelligent services traffic. Table 8 Nondisruptive Downgrade Path from SAN-OS Release 3.2(1) To SAN-OS Release Nondisruptive Downgrade Path SAN-OS 3.1(4) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.1(3a) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.1(2a) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.1(2) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.1(1) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.0(3a) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.0(3) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.0(2a) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.0(2) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 3.0(1) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 2.1(3) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 2.1(2e) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 2.1(2d) You can nondisruptively downgrade directly from SAN-OS Release 3.2(1). SAN-OS 2.1(2b) You can nondisruptively downgrade directly from SAN-OS Release 3.1(2b). SAN-OS 2.1(2) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(2). SAN-OS 2.1(1b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1b). SAN-OS 2.1(1a) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1a). SAN-OS 2.0(4a) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4a). SAN-OS 2.0(4) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4). SAN-OS 2.0(3) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(3). SAN-OS 2.0(2b) Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(2b). Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1) 22 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]
22
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1)
OL-14116-01
Downgrading Your Cisco MDS SAN-OS Software Image
IVR
: With IVR enabled, you must follow additional steps if you are downgrading 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 downgrade path is different. See
Table 9
.
iSNS
: The iSNS feature does not support a graceful downgrade from Cisco MDS SAN-OS
Release 3.2(1) to any earlier SAN-OS release. Prior to a downgrade from Cisco SAN-OS 3.2(1),
disable the MDS iSNS server and remove all configurations associated with the MDS iSNS
client.
Use
Table 8
to determine your nondisruptive downgrade path from Cisco SAN-OS Release 3.2(1). Find
the SAN-OS image you want to downgrade to in the To SAN-OS Release column of the table and use
the path recommended.
Note
The software downgrade information in
Table 8
applies only to Fibre Channel switching traffic.
Downgrading system software disrupts IP and SSM intelligent services traffic.
Table 8
Nondisruptive Downgrade Path from SAN-OS Release 3.2(1)
To SAN-OS Release
Nondisruptive Downgrade Path
SAN-OS 3.1(4)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.1(3a)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.1(2b)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.1(2a)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.1(2)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.1(1)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.0(3a)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.0(3)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.0(2a)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.0(2)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 3.0(1)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 2.1(3)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 2.1(2e)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 2.1(2d)
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
SAN-OS 2.1(2b)
You can nondisruptively downgrade directly from SAN-OS Release 3.1(2b).
SAN-OS 2.1(2)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(2).
SAN-OS 2.1(1b)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1b).
SAN-OS 2.1(1a)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.1(1a).
SAN-OS 2.0(4a)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4a).
SAN-OS 2.0(4)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(4).
SAN-OS 2.0(3)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(3).
SAN-OS 2.0(2b)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(2b).