Cisco Cisco MDS 9000 NX-OS Software Release 5.2 Notas de publicación
50
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8)
OL-27554-04
Caveats
Workaround: Use CFS regions if a large number (greater than 512) of application flows need to be
configured. CFS regions segment the FCR peer topology into manageable proportions.
configured. CFS regions segment the FCR peer topology into manageable proportions.
•
CSCtr50223
Symptom: On the MDS 9513 switch, when an MSM-18/4 module boots up, it sends a request to the
supervisor module to mount the modflash on the MSM-18/4 module. If there is a timeout or error in
response, the following syslog message displays:
supervisor module to mount the modflash on the MSM-18/4 module. If there is a timeout or error in
response, the following syslog message displays:
2011 Jul 14 01:18:13 sw-dc5-br2-12 %LC_MNT_MGR-SLOT3-2-LC_MNT_MGR_ERROR: SUP mount
failed. MTS receive timedout
2011 Jul 14 01:19:06 sw-dc5-br2-12 %PROC_MGR-SLOT3-2-ERR_MSG: ERROR: PID 1144
(lc_mnt_mgr) exited abnormally, exit status (0xa)
2011 Jul 14 01:19:06 sw-dc5-br2-12 %MODULE-2-MOD_MINORSWFAIL: Module 3 (serial:
JAE1141ZB43) reported a failure in service lc_mnt_mgr
This issue might be seen when the supervisor module is unusually busy and cannot process the
mount request from the MSM-18/4 module, or the actual mount command on the supervisor takes a
long time.
mount request from the MSM-18/4 module, or the actual mount command on the supervisor takes a
long time.
Workaround: Reload the MSM-18/4 module in the same slot/module where the modflash mount
failed. A request will be sent to the supervisor to mount the modflash.
failed. A request will be sent to the supervisor to mount the modflash.
•
CSCty82821
Symptom: After creating an SME cluster, adding disks to a disk group, changing some disk states,
and starting master key rekey, the key creation date is invalid.
and starting master key rekey, the key creation date is invalid.
Workaround: None.
•
CSCua61011
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.
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:
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.”
isapi health-check command. The output shows “Memory Status: ERROR.”
Workaround: None.
•
CSCud72991
Symptom: A port drops all packets originating from the supervisor module. The packets are
dropped as TIMEOUT drops. The port is up and has all of its allotted Tx B2B credits, but the input
and output rate is 0 frames per second.
dropped as TIMEOUT drops. The port is up and has all of its allotted Tx B2B credits, but the input
and output rate is 0 frames per second.
Workaround: Enter the shut command followed by the no shut command on the port to recover it.
•
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.
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).