HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Re - Page 18

FICON Supported Releases, Current Release with FICON, Enabled, Upgrade Path, Table 9

Page 18 highlights

Upgrading Your Cisco MDS NX-OS Software Image Send documentation comments to [email protected] Table 9 lists additional SAN-OS and NX-OS releases that support FICON. Refer to the specific release notes for FICON upgrade path information. Table 9 FICON Supported Releases FICON Supported Releases NX-OS Release 4.2(1a) Release 4.1(1c) SAN-OS Release 3.3(1c) Release 3.2(2c) Release 3.0(3b) Release 3.0(3) Release 3.0(2) Release 2.0(2b) Use Table 10 to determine your FICON nondisruptive upgrade path to Cisco MDS NX-OS Release 4.1(1c) Find the image release number you are currently using in the Current Release with FICON Enabled column of the table and follow the recommended path. Table 10 FICON Nondisruptive Upgrade Path to MDS NX-OS Release 4.1(1c) Current Release with FICON Enabled Upgrade Path SAN-OS 3.3(1c) You can nondisruptively upgrade directly to NX-OS Release 4.1(1c). SAN-OS 3.2(2c) First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS Release 4.1(1c). SAN-OS 3.0(3b) First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS Release 4.1(1c). SAN-OS 3.0(3) First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS Release 4.1(1c). SAN-OS 3.0(2) First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS Release 4.1(1c). SAN-OS 2.0(2b) Use the interface shutdown command to administratively shut any Fibre Channel ports on Generation 1 modules that are in an operationally down state before nondisruptively upgrading from SAN-OS Release 2.0(2b) to SAN-OS Release 3.0(2) or SAN-OS Release 3.0(3b), and then upgrade to Release 3.3(1c). An operationally down state includes Link failure or not-connected, SFP not present, or Error Disabled status in the output of a show interface command. When an interface is administratively shut it will then show as Administratively down. Interfaces that are currently up or trunking do not need to be shut down. SAN-OS 1.x Upgrade to SAN-OS Release 3.0(2). Use the interface shutdown command to shut all the ports operationally down and administratively up on all the Generation 1 modules before nondisruptively upgrading to Release 2.0(2b) and then upgrade to 1.3(4a). Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a) 18 OL-19964-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

Send documentation comments to [email protected]
18
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a)
OL-19964-02
Upgrading Your Cisco MDS NX-OS Software Image
Table 9
lists additional SAN-OS and NX-OS releases that support FICON. Refer to the specific release
notes for FICON upgrade path information.
Use
Table 10
to determine your FICON nondisruptive upgrade path to Cisco MDS NX-OS
Release 4.1(1c) Find the image release number you are currently using in the Current Release with
FICON Enabled column of the table and follow the recommended path.
Table 9
FICON Supported Releases
FICON Supported Releases
NX-OS
Release 4.2(1a)
Release 4.1(1c)
SAN-OS
Release 3.3(1c)
Release 3.2(2c)
Release 3.0(3b)
Release 3.0(3)
Release 3.0(2)
Release 2.0(2b)
Table 10
FICON Nondisruptive Upgrade Path to MDS NX-OS Release 4.1(1c
)
Current Release with FICON
Enabled
Upgrade Path
SAN-OS 3.3(1c)
You can nondisruptively upgrade directly to NX-OS Release 4.1(1c).
SAN-OS 3.2(2c)
First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS
Release 4.1(1c).
SAN-OS 3.0(3b)
First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS
Release 4.1(1c).
SAN-OS 3.0(3)
First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS
Release 4.1(1c).
SAN-OS 3.0(2)
First upgrade to SAN-OS Release 3.3(1c), and then upgrade to NX-OS
Release 4.1(1c).
SAN-OS 2.0(2b)
Use the
interface shutdown
command to administratively shut any Fibre
Channel ports on Generation 1 modules that are in an operationally down
state before nondisruptively upgrading from SAN-OS Release 2.0(2b) to
SAN-OS Release 3.0(2) or SAN-OS Release 3.0(3b), and then upgrade
to Release 3.3(1c). An operationally down state includes
Link failure
or not-connected, SFP not present
, or
Error Disabled
status in the
output of a
show interface
command. When an interface is
administratively shut it will then show as
Administratively down
.
Interfaces that are currently up or trunking do not need to be shut down.
SAN-OS 1.x
Upgrade to SAN-OS Release 3.0(2). Use the
interface shutdown
command to shut all the ports operationally down and administratively up
on all the Generation 1 modules before nondisruptively upgrading to
Release 2.0(2b) and then upgrade to 1.3(4a).