Cisco AP776A - Nexus Converged Network Switch 5020 Catatan Rilis - Halaman 25

Jelajahi secara online atau unduh pdf Catatan Rilis untuk Beralih Cisco AP776A - Nexus Converged Network Switch 5020. Cisco AP776A - Nexus Converged Network Switch 5020 44 halaman. Cisco nexus 5000 series release notes release 4.1(3)n1(1) (ol-16601-01 h0, july 2009)
Juga untuk Cisco AP776A - Nexus Converged Network Switch 5020: Catatan Rilis (48 halaman), Catatan Rilis (26 halaman), Catatan Rilis (22 halaman), Panduan Referensi Cepat (14 halaman), Catatan Rilis (3 halaman), Catatan Rilis (26 halaman)

Cisco AP776A - Nexus Converged Network Switch 5020 Catatan Rilis
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 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)
Downgrading the SSI Image on Your SSM
Use the following guidelines when downgrading your SSI image on 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
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
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.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
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
for Cisco MDS 9000 EPLD Images
Refer to the
Cisco Data Center Interoperability Support Matrix
chapter in the
Cisco MDS 9000 Family CLI Configuration Guide, Release
on downgrading your SSM.
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(3)
Downgrading Your Cisco MDS SAN-OS Software Image
, or
Error Disabled
Administratively down
Cisco MDS NX-OS Release Compatibility Matrix for Storage
Cisco MDS 9000 Family Release Notes
to upgrade your EPLD image.
Link failure or
status in the output
. Interfaces that are currently up
and the "Managing Modules"
3.x, for information
25