HP Cisco MDS 8/24c Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Rel - Page 19

FICON Downgrade Paths, To NX-OS or SAN-OS, Release, Nondisruptive Downgrade Path

Page 19 highlights

Downgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] Table 13 Nondisruptive Downgrade Path from NX-OS Release 5.2(1) To NX-OS or SAN-OS Release Nondisruptive Downgrade Path NX-OS: All 5.0(x) releases You can nondisruptively downgrade directly from NX-OS Release 5.2(1).1,2 All 4.2(x) and 4.1(x) Downgrade to any NX-OS Release 5.0(x) and then downgrade to NX-OS releases Release 4.2(x) or 4.1(x)1 SAN-OS: All 3.3(x) releases Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, and then downgrade to SAN-OS Release 3.3(x). All 3.2(x), 3.1(x), Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade 3.0(x) releases, and all to SAN-OS Release 3.3(x), and then downgrade to Release 3.2(x), Release 2.1(x) releases. 3.1(x)., Release 3.0(x), or Release 2.1(x). All 2.0(x) releases. Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade to SAN-OS Release 3.3(x), then downgrade to Release 2.1(2x), and then downgrade to Release 2.0(x). Release 1.x Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade to SAN-OS Release 3.3(x), then downgrade to SAN-OS to Release 2.1(2b), then to Release 1.3(4a), and then downgrade to your SAN-OS 1.x release. 1. If you install a Generation 4 module in an MDS 9509 or MDS 9506 switch and perform a full switch reload following the installation of NX-OS Release 5.2(1), then you cannot nondisruptively download from NX-OS Release 5.2(1) to NX-OS 5.0(x). 2. A downgrade from NX-OS Release 5.2(1) disrupts and stops all FCoE traffic because FCoE requires Cisco NX-OS Release 5.2(1). FICON Downgrade Paths Table 14 lists the downgrade paths for FICON releases. Find the image release number that you want to downgrade to in the To Release with FICON Enabled column of the table and follow the recommended downgrade path. Table 14 FICON Downgrade Path To Release with FICON Enabled NX-OS Release 4.2(1b) NX-OS Release 4.1(1c) SAN-OS 3.3(1c) SAN-OS 3.2(2c) SAN-OS 3.0(3b) SAN-OS 3.0(2) Downgrade Path You can nondisruptively downgrade directly from NX-OS Release 4.2(7b). You can nondisruptively downgrade directly from NX-OS Release 4.2(1b). You can nondisruptively downgrade directly from NX-OS Release 4.1(1c). First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release 3.2(2c). First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release 3.0(3b). First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release 3.0(2). OL-25090-01 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1) 19

  • 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]
19
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1)
OL-25090-01
Downgrading Your Cisco MDS SAN-OS Software Image
FICON Downgrade Paths
Table 14
lists the downgrade paths for FICON releases. Find the image release number that you want to
downgrade to in the
To Release with FICON Enabled
column of the table and follow the recommended
downgrade path.
Table 13
Nondisruptive Downgrade Path from NX-OS Release 5.2(1)
To NX-OS or SAN-OS
Release
Nondisruptive Downgrade Path
NX-OS:
All 5.0(x) releases
You can nondisruptively downgrade directly from NX-OS Release 5.2(1).
1,2
1.
If you install a Generation 4 module in an MDS 9509 or MDS 9506 switch and perform a full switch reload following the
installation of NX-OS Release 5.2(1), then you cannot nondisruptively download from NX-OS Release 5.2(1) to NX-OS
5.0(x).
2.
A downgrade from NX-OS Release 5.2(1) disrupts and stops all FCoE traffic because FCoE requires Cisco NX-OS Release
5.2(1).
All 4.2(x) and 4.1(x)
releases
Downgrade to any NX-OS Release 5.0(x) and then downgrade to NX-OS
Release 4.2(x) or 4.1(x)
1
SAN-OS:
All 3.3(x) releases
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, and then
downgrade to SAN-OS Release 3.3(x).
All 3.2(x), 3.1(x),
3.0(x) releases, and all
2.1(x) releases.
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade
to SAN-OS Release 3.3(x), and then downgrade to Release 3.2(x), Release
3.1(x)., Release 3.0(x), or Release 2.1(x).
All 2.0(x) releases.
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade
to SAN-OS Release 3.3(x), then downgrade to Release 2.1(2x), and then
downgrade to Release 2.0(x).
Release 1.x
Downgrade to NX-OS Release 4.2(x) or Release 4.1(x) first, then downgrade
to SAN-OS Release 3.3(x), then downgrade to SAN-OS to Release 2.1(2b),
then to Release 1.3(4a), and then downgrade to your SAN-OS 1.x release.
Table 14
FICON Downgrade Path
To Release with FICON Enabled
Downgrade Path
NX-OS Release 4.2(1b)
You can nondisruptively downgrade directly from NX-OS Release 4.2(7b).
NX-OS Release 4.1(1c)
You can nondisruptively downgrade directly from NX-OS Release 4.2(1b).
SAN-OS 3.3(1c)
You can nondisruptively downgrade directly from NX-OS Release 4.1(1c).
SAN-OS 3.2(2c)
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.2(2c).
SAN-OS 3.0(3b)
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.0(3b).
SAN-OS 3.0(2)
First downgrade to SAN-OS Release 3.3(1c) and then downgrade to Release
3.0(2).