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
56
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(1b)
OL-17675-02
Caveats
CSCsr28197
Symptom: The error messages for Device-Alias Merge do not provide information to be able to
identify offending Device-Aliases or PWWNs associated with the merge failures.
Workaround: This issue is resolved.
CSCsr28302
Symptom: DPVM merge failure messages to not indicate why the merge failed.
Workaround: This issue is resolved.
CSCsr32181
Symptom: Removing a power supply or a fan module does not send alerts to the host.
Workaround: This issue is resolved.
CSCsr40527
Symptom: The RDL process fails due to many fcpings in a loop. This issue may occur when fcping
is running in a script.
Workaround: This issue is resolved.
CSCsr47868
Symptom: The show port internal information command shows the service state as
out-of-service; however, the RAM data does not show out-of-service.
Workaround: This issue is resolved.
CSCsr49173
Symptom: A network management application may occasionally detect 100% CPU utilization when
monitoring an MDS switch using SNMP. The show process cpu command does not show high
utilization.
Workaround: This issue is resolved.
CSCsr49954
Symptom: A Recoverpoint Appliance with a Qlogic HBA sends an 8-byte RFT_ID instead of
standard 32bytes.This causes FC4 features to be incorrectly registered.
Workaround: This issue is resolved.
CSCsr68482
Symptom: In disjointed VSANs, all switches configured with an application in a region may not
become Cisco Fabric Services (CFS) peers as shown in the following diagram:
VSAN : X VSAN : Y
Switch 1---------------------Switch 2----------------- Switch 3
(application enabled (application enabled
in the CFS region) in the CFS region)
In the example above, if an application is enabled in a CFS region (for example, in region ID 10) on
Switch 1 and Switch 3 and on Switch 2, then that application is enabled in the default region or in
a different CFS region. In this scenario, the CFS on intermediate switch Switch 2 does not forward
data to other switches and those switches become separate fabrics for that application.
Workaround: This issue is resolved.