Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8), (OL-27554-04, December 10, 2012)

38
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8)
OL-27554-04
Caveats
This symptom only occurs for the specific failure case of the active supervisor with a faulty link to
the fabric.
Workaround: This issue is resolved.
CSCuc91171
Symptom: Cisco NX-OS software fails to save the running configuration and the following error
message appears:
Service "fcns" failed to save its configuration
This symptom only occurs after the configuration has been saved many times (approximately 500
times). Because saving the running configuration is part of an upgrade, this issue can impact
upgrades from an affected software release.
Workaround: This issue is resolved.
CSCud12362
Symptom: The MSM-18/4 module fails with the following message:
%RM-SLOT1-2-CPP_CATASTROPHIC_ERROR: ERROR: Component (Partner Software) caused
critical error. Service Module will be reloaded
If the supervisor module in the Cisco MDS 9222i switch experiences this issue, the failure causes
the whole system to reload.
This issue can occur in SANTap environments when the WAN is slow. Under these conditions, the
DPP software might fail which causes the CPP software to reset the module.
Workaround: This issue is resolved.
CSCtt46972
Symptom: A Cisco MDS 9000 Series switch is not able to display the source and destination of
queued frames in human readable format.
This issue applies to troubleshooting the Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel
Switching Module (DS-X9232-256K9), the Cisco MDS 9000 48-port 8-Gbps Advanced Fibre
Channel Switching Module (DS-X9248-256K9). and the Cisco MDS 9148 48-Port Multilayer
Fabric Switch (DS-C9148-K9).
Workaround: This issue is resolved.
CSCtz44601
Symptom: A username cannot be deleted.
Workaround: This issue is resolved.
CSCua98554
Symptom: After entering the clear zone ? command, not all options appear. Only smart-zoning
commands appear.
Workaround: This issue is resolved.
CSCub52174
Symptom: The following syslog message should display a reason as to why the FCID allocation
failed:
%FLOGI-1-MSG_FLOGI_REJECT_FCID_ERROR: %$VSAN x%$ [VSAN 10, Interface fcx/y: mode[F]]
FLOGI rejected - FCID allocation failed.
Workaround: This issue is resolved.
CSCub57007