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

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8)

OL-27554-04

Caveats

If more than one peer is affected by this issue, then additional steps are needed. If the application

flows do not come online, then the application CLI commands need to be checked to verify that the

flows did not get deleted. If they did, then the flows need to be recreated again through the

application CLI command s or Cisco DCNM-SAN interface.

• CSCtw64713

Symptom: Occasionally, a 10-G ISL between a 32-port 8-Gbps Advanced Fibre Channel Switching

Module (DS-X9232-256K9) or a 48-port 8-Gbps Advanced Fibre Channel Switching Module

(DS-X9248-256K9) and an older generation Cisco MDS 9000 module can take a long time to come

up. The link can go into an error-disabled state.

Workaround: None.

• CSCty82906

Symptom: On a Windows XP system, master key rekey cannot detect a smart card and displays the

following message:

Exception reading smartcard:CKR_OPERATION_NOT_INITIALIZED

Workaround: None.

• CSCtq88900

Symptom: In an SME or IOA deployment, if the number of H->T flows that are added exceeds 512,

then subsequent disruptive platform events can leave an FCR unable to process interprocess (MTS)

messages at a rate fast enough to support the scaled configuration. This situation can cause an

MTS-buffers full condition in the FCR, which can result in unpredictable behavior. Some of the

resulting errors may be unrecoverable, and may require a disruptive restart of the flows.

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.

• 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:

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.

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.

• 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.

Workaround: None.

• CSCua61011