Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6b) (OL-27554-03 D0, December 21, 2013)

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

OL-27554-03

Caveats

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

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.

• CSCtz09820

Symptom: In Generation 4 modules, the following errors might be observed. They are not a cause

for concern to the normal operation of the hardware. These errors are logged in the onboard

persistent log and can be viewed by entering the show logging onboard exception-log command

after attaching to the module.

TBIRD_FWD_EBM_0_SER_PARITY_XXX : Informational

TBIRD_FWD_EBM_0_PACK0_EPR_DROP : Informational

TBIRD_FWD_EBM_1_PACK3_MISS_SOF : Informational

TBIRD_FWD_EBM_1_PACK0_MISS_EOP : Informational

TBIRD_FWD_EBM_1_PACK0_SF_TOO_SMALL : Informational

These errors are reported when there are internal correctable conditions encountered during

operation, and the corrective action is taken. They do not necessarily indicated a problem with the

switch or module.

The following error can occur in cases of corrupted frames in the ingress path (due to a bad cable or

SFP). It does not necessarily indicated a problem with the switch hardware.

THB_IPA_IPA0_INTR_FLD_ERR_FROM_MEM : Warning

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