Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a) (OL-19964-02, September 2009)

Send documentation comments to mdsfeedback-doc@cisco.com

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.2(1a)

OL-19964-02

Related Documentation

Workaround: This issue is resolved.

• CSCsz22811

Symptom: Compression throughput on the MSM-18/4 module has been improved.

Workaround: This issue is resolved.

• CSCtb80346

Symptom: When an SFP is removed because a port if Administratively Down or Out of Service, a

syslog message should be generated.

Workaround: This issue is resolved.

Open Caveats

• CSCta22244

Symptom: On MDS switches running NX-OS Release 4.2(1a), an fctrace command or fcping

command will not show the correct path to the target switch if any of the switches are connected

through an ISL using any of the ports of the following modules:

• DS-X9248-48K9: 4/44-Port 8-Gbps Host-Optimized Fibre Channel Switching Module

• DS-X9248-96K9: 48-Port 8-Gbps Fibre Channel Switching Module

• DS-X9224-96K9: 24-Port 8-Gbps Fibre Channel Switching Module

The output of an fctrace or fcping command will not show any information about the switches

connected through the ports of these modules.

Workaround: None.

• CSCsq20408

Symptom: The show startup command displays aspects of the running configuration when SANtap

is configured and/or SANtap objects are created. When a user creates objects such as a CVT or DVT,

the configuration is showing in the running-configuration and in the startup-configuration without

copying the configuration into the startup-configuration.

Workaround: Issue a copy running-config startup-config command whenever you create objects

such as a CVT or DVT so that the running-configuration and startup-configuration are synchronized.

• CSCsy37951

Symptom: The Trunking F PortChannels feature is not available in NX-OS Release 4.1(1x);

however, a downgrade from Release 4.1(3a) or later to Release 4.1(1x) is nondisruptive, even when

the Trunking F PortChannels feature is enabled (using the feature fport-channel-trunk command)

while running Release 4.1(3a) or later.

Workaround: If a downgrade to Release 4.1(1x) is performed when the Trunking F PortChannels

feature is enabled, the switch will be in an inconsistent state. You must reload the switch after a

downgrade to Release 4.1(1x).