Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(1b) (OL-17675-02, October 2008)

Send documentation comments to mdsfeedback-doc@cisco.com
23
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(1b)
OL-17675-02
Upgrading Your Cisco MDS NX-OS Software Image
Use Table 12 to determine your FICON nondisruptive upgrade path to Cisco MDS NX-OS Release
4.1(1b) Find the image release number you are currently using in the Current Release with FICON
Enabled column of the table and use the path recommended.
Upgrading with IVR Enabled
An Inter-Switch Link (ISL) flap resulting in fabric segmentation or a merge during or after an upgrade
from Cisco MDS SAN-OS Release 2.0(x) to a later image where IVR is enabled might be disruptive.
Some possible scenarios include the following:
FCIP connection flapping during the upgrade process resulting in fabric segmentation or merge.
ISL flap results in fabric segmentation or merge because of hardware issues or a software bug.
ISL port becomes part of PCP results in fabric segmentation or merge because of a port flap.
If this problem occurs, syslogs indicate a failure and the flapped ISL could remain in a down state
because of a domain overlap.
Table 12 FICON Nondisruptive Upgrade Path to NX-OS Release 4.1(1b)
Current Release with
FICON Enabled Upgrade Path
SAN-OS 3.3(1c) You can nondisruptively upgrade directly to NX-OS Release 4.1(1b)
SAN-OS 3.0(3b) First upgrade to SAN-OS Release 3.3(1c) and then upgrade to NX-OS
Release 4.1(1b)
SAN-OS 3.0(2) First upgrade to SAN-OS Release 3.3(1c) and then upgrade to NX-OS
Release 4.1(1b)
SAN-OS 3.0(1) and
earlier
First upgrade to SAN-OS Release 3.3(1c) and then upgrade to NX-OS
Release 4.1(1b)
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).