Installation guide

43
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6)
OL-27554-01
Caveats
Workaround: This issue is resolved.
• CSCty01206
Symptom: After upgrading Fabric Manager Server and the Cisco Key Management Centers (KMC)
from Cisco NX-OS Release 4.2(3) to Release 5.0(4d) to Release 5.2(1), the old tape key replication
relationships are lost. However, you are able to create new tape key replication relationships for the
newly created tape-backup groups.
This symptom occurs following an upgrade of the KMC to Cisco NX-OS Release 5.2(1).
Workaround: This issue is resolved.
• CSCty59664
Symptom: After releasing the local zone lock through Cisco Fabric Manager, the fabric lock still
exists and the IVR commit does not happen.
Workaround: This issue is resolved.
• CSCty61259
Symptom: During an ISSU from Cisco NX-OS Release 4.2(3) to Release 5.0(7), the standby
supervisor failed to boot to the new version, but the boot variables were modified to the new release,
which is not the expected behavior.
Workaround: This issue is resolved.
• CSCtz53329
Symptom: The standby supervisor resets and this message is logged in the syslog:
%SYSMGR-2-GSYNC_SNAPSHOT_SRVFAILED: Service "syslogd" on active supervisor
failed to store its snapshot (error-id 0x80480018).
%SYSMGR-2-STANDBY_BOOT_FAILED: Standby supervisor failed to boot up
Condition: This situation only occurs if the standby supervisor reloads many times.
Workaround: None.
More Information: Contact Cisco TAC to recover from this issue.
• CSCtz59701
Symptom: An EPLD upgrade failed because an incorrect fabric controller was detected.
Workaround: This issue is resolved.
• CSCtz73068
Symptom: The ethport process failed on the active supervisor and then on the standby supervisor
after a switchover that was triggered by hap-reset, which caused a switch reload.
switch# show system reset-reason
----- reset reason for Supervisor-module 5 (from Supervisor in slot 5) ---
1) At 645162 usecs after Wed May 2 11:56:56 2012
Reason: Reset triggered due to HA policy of Reset
Service: ethport hap reset
Version: 5.2(2a)
----- reset reason for Supervisor-module 6 (from Supervisor in slot 6) ---
1) At 685033 usecs after Wed May 2 12:01:03 2012
Reason: Reset triggered due to HA policy of Reset
Service: ethport hap reset
Version: 5.2(2a)
Four core files were created, two for each supervisor module.
switch# show cores
Module Instance Process-name PID Date(Year-Month-Day Time)