Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8), (OL-27554-04, December 10, 2012)
44
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8)
OL-27554-04
Caveats
Symptom: After creating an SME cluster in advanced mode, adding 500 disks to the disk group,
exporting the keys, and importing the keys again, there is no scroll option in the import manage key
window.
Workaround: None.
• CSCud49969
Symptom: If you enter the isapi health-check command after attaching the Cisco MDS 9000
18/4-Port Multiservice Module (MSM-18/4), the following error appears:
Memory Status: ERROR
Conditions: This symptom might be seen after attaching the MSM-18/4 module and entering the
isapi health-check command. The output shows “Memory Status: ERROR.”
Workaround: None.
• CSCtz19169
Symptom: After the primary KMC fails over to the secondary, KMC performance suffers. The
system attempts to reacquire connectivity to the primary KMC for each operation, and the system
waits for that attempt to time out before using the secondary KMC. Waiting for the timeout creates
a significant delay for failed over operations, particularly when scaled.
This symptom occurs when the primary KMC fails (because of loss of connectivity).
Workaround: Restore connectivity to the primary KMC.
• CSCtz40700
Symptom: When a trunk link fails, the 1.3.6.1.4.1.9.9.289.1.3 trap has an incorrect link failure
reason of “gracefully down.”
This symptom might be seen only when a link failure occurs on a E, TE, or TF port.
Workaround: Ignore the link down reason because the link down trap is valid.
• CSCtz40745
Symptom: A “VSAN down” trap is sent for VSAN 4094 when a trunk port goes down because the
VSAN is not configured on the trunk.
This symptom might be seen only when a link down occurs on a E, TE, or TF port.
Workaround: Ignore the trap.
• CSCua09712
Symptom: Communication errors that occur during master key rekey are not handled gracefully.
Workaround: None.
• CSCtz84847
Symptom: When creating a cluster, key management servers are not listed in the drop-down list.
Workaround: Manually enter the IP address of the server.
• CSCty47599
Symptom: For a failed master key rekey, the master key shares were generated and updated in the
CKMC.
Workaround: None.