HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 25

Downgrading the SSI Image on Your SSM, Downgrading an MDS 9222i Switch - interoperability matrix

Page 25 highlights

Downgrading Your Cisco MDS SAN-OS Software Image Send documentation comments to [email protected] Table 9 FICON Downgrade Path from SAN-OS 3.3(3) To SAN-OS Release with FICON Enabled SAN-OS 2.0(2b) SAN-OS 1.3(4a) Downgrade Path 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.3(1c) 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 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. 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). Downgrading the SSI Image on Your SSM Use the following guidelines when downgrading your SSI image on your SSM. • 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.3(3) 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 Cisco MDS NX-OS Release Compatibility Matrix for Storage 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 command to determine if any applications are provisioned on the SSM. Use the no ssm enable feature configuration mode command to disable these features. - The EPLD version on the SSM is at 0x07 or higher. Use the show version module slot epld command to determine your EPLD version. Refer to the Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images to upgrade your EPLD image. - Refer to the Cisco Data Center Interoperability Support Matrix and the "Managing Modules" chapter in the Cisco MDS 9000 Family CLI Configuration Guide, Release 3.x, for information on downgrading your SSM. Downgrading an MDS 9222i Switch If you are running MDS NX-OS 4.1(1x) on an MDS 9222i switch and you need to downgrade to a SAN-OS 3.3(x) release, you can downgrade to Release 3.3(2), 3.3(1c), or 3.3(1a), but you cannot downgrade to 3.3(3). A nondisruptive downgrade from NX-OS 4.1(1x) to SAN-OS 3.3(3) is not supported on the MDS 9222i switch. This restriction does not apply to other platforms. OL-14116-11 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3) 25

  • 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]
25
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3)
OL-14116-11
Downgrading Your Cisco MDS SAN-OS Software Image
Downgrading the SSI Image on Your SSM
Use the following guidelines when downgrading your SSI image on your SSM.
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.3(3) 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
Cisco MDS NX-OS Release Compatibility Matrix for Storage
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
command to determine if
any applications are provisioned on the SSM. Use the
no ssm enable feature
configuration
mode command to disable these features.
The EPLD version on the SSM is at 0x07 or higher. Use the
show version module
slot
epld
command to determine your EPLD version. Refer to the
Cisco MDS 9000 Family Release Notes
for Cisco MDS 9000 EPLD Images
to upgrade your EPLD image.
Refer to the
Cisco Data Center Interoperability Support Matrix
and the “Managing Modules”
chapter in the
Cisco MDS 9000 Family CLI Configuration Guide, Release 3.x
,
for information
on downgrading your SSM.
Downgrading an MDS 9222i Switch
If you are running MDS NX-OS 4.1(1x) on an MDS 9222i switch and you need to downgrade to a
SAN-OS 3.3(x) release, you can downgrade to Release 3.3(2), 3.3(1c), or 3.3(1a), but you cannot
downgrade to 3.3(3). A nondisruptive downgrade from NX-OS 4.1(1x) to SAN-OS 3.3(3) is not
supported on the MDS 9222i switch. This restriction does not apply to other platforms.
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 downgrading from SAN-OS Release 3.3(1c) 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
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.3(4a)
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).
Table 9
FICON Downgrade Path from SAN-OS 3.3(3)
To SAN-OS Release with FICON Enabled
Downgrade Path