Installation guide

ManualsBrandsCisco ManualsComputer equipmentDS-X9530-SF1-K9 - Supervisor-1 Module - Control Processor

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

OL-27554-01

Caveats

Workaround: Enter the following supervisor commands on the problematic FCR peer, which will

trigger this FCR peer to resync with the rest of the fabric, and force it to come out of the error state:

switch# test fc-redirect config sync-with-fabric

switch# test fc-redirect config sync-with-fabric all-peers

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.

• CSCty59570

Symptom: After replacing a smart card that reached the maximum number of shares (16), the new

smart card gets stuck in the initializing state.

Workaround: None.

• CSCty68838

Symptom: Periodic FCIP port flaps might occur when Tape Acceleration and IP compression are

enabled and the MTU is configured at 9000. This situation might lead to a failure of an IPS core.

This symptom might be seen when the following configuration is applied to an FCIP tunnel:

–

Tape Acceleration (TA) is enabled.

–

Write Acceleration (required for TA) is enabled.

–

IP compression in enabled.

–

The MTU size is 9000.

Workaround:

This issue does not occur if TA is not configured and other parameters remain the same.

This issue does not occur if the MTU size of up to 2500 is configured and other parameters remain

the same.

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

• CSCua12379

Symptom: On a Windows 7 32-bit system, there is an issue with the Java version detect plugin. In

addition, the pkcs11wrapper.dll file is not copied over correctly.

Workaround: None.

• CSCub47799

Symptom: Zone crash or switch reload occurs after renaming an enhanced device-alias.