S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Table 8
To SAN-OS Release Nondisruptive Downgrade Path
SAN-OS 2.0(1b)
SAN-OS 1.x
Use
Release 3.2(1). 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.
Table 9
FICON Downgrade Path from SAN-OS 3.2(1)
To SAN-OS Release with FICON Enabled
SAN-OS 3.0(3b)
SAN-OS 3.0(2)
SAN-OS 2.0(2b)
SAN-OS 1.3(4a)
Downgrading the SSI Image on Your SSM
Use the following guidelines when downgrading your SSI image on your SSM.
•
•
•
•
OL-14116-01
Nondisruptive Downgrade Path from SAN-OS Release 3.2(1)
Downgrade to SAN-OS Release 2.1(2b) and then downgrade to Release 2.0(1b).
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 9
to determine your FICON 3.2(1) nondisruptive downgrade path from Cisco SAN-OS
Downgrade Path
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
You can nondisruptively downgrade directly from SAN-OS Release 3.2(1).
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 downgrading from SAN-OS Release 3.2(1) to
SAN-OS Release 3.0(3b) or SAN-OS Release 3.0(2), and then to SAN-OS
Release 2.0(2b). An operationally down state includes
not-connected, SFP not present
of a show interface command. When an interface is administratively shut it
will then show as
or trunking do not need to be shut down.
Downgrade to SAN-OS Release 3.0(2). Use the shutdown command to shut
all the ports operationally down and administratively up on all the
Generation 1 modules before nondisruptively downgrading to Release
2.0(2b) and then downgrade to 1.3(4a).
On a system with at least one SSM installed, the install all command might fail on an SSM when
you downgrade from Cisco SAN-OS Release 3.2(1) to any SAN-OS 2.x release earlier than
SAN-OS Release 2.1(2e). Power down the SSM and perform the downgrade. Bring up the SSM with
the new bootvar set to the 2.x SSI image.
Downgrade the SSI boot images on the SSMs on the switch to a release version supported by your
Cisco SAN-OS release. Refer to the
Service Interface
Images.
SSM intelligent services traffic switching on SSM ports is disrupted on upgrades or downgrades.
Fibre Channel switching traffic on SSM ports is not disrupted under the following conditions:
All SSM applications are disabled. Use the show ssm provisioning CLI command to determine
–
if any applications are provisioned on the SSM. Use the no ssm enable feature configuration
mode CLI command to disable these features.
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1)
Downgrading Your Cisco MDS SAN-OS Software Image
, or
Error Disabled
Administratively down
Cisco MDS SAN-OS Release Compatibility Matrix for Storage
Link failure or
status in the output
. Interfaces that are currently up
23
Halaman Cetak