Installation guide

61
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6)
OL-27554-01
Caveats
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.
• CSCuh27347
Symptom: During an In Service Software Upgrade (ISSU) or In Service Software Downgrade
(ISSD), ports that are administratively up and also in the not-connected state get reinitialized.
Condition: This issue affects all Cisco MDS dual-supervisor systems.
Workaround: If starting an ISSU/ISSD from an affected version of Cisco MDS NX-OS software,
ensure that all ports that are administratively up, but not connected, are shut down during the
ISSU/ISSD.
More Information: This might cause the Cisco MDs Generation 3 Fibre Channel switching
modules to drop all outbound traffic with the OFFLINE and TIMEOUT errors. For more
information, see CSCuf31077.
• CSCum30306
Symptom: The security service crashes when configuring an SSH authentication key.
Configuring SSH keys multiple times within 10 minutes results in a HAP reset that resets the active
supervisor.
Condition: This issue intermittently occurs when configuring an SSH authentication key.
Workaround: To avoid the supervisor reset, do not configure more than 2 SSH keys per 10 minutes.