Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8b) (OL-27554-06, July 12, 2013)

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

OL-27554-06

Caveats

• CSCug76835

Symptom: Cisco MDS DS-X9232-256K9 and DS-X924256K9 switching modules attempt to log

unnecessary EEM events to syslog on the supervisor.

Condition: This issue only includes reporting hardware events such as interrupts.

Workaround: This issue is resolved.

• CSCub93429

Symptom: On Cisco MDS 9000 Family switches, CLI help (?) does not list all the available

commands, keywords, and arguments for a user. Also, the tab key command completion does not

work.

Condition: This issue occurs only for users with role-based access control (RBAC)-based privileges

that access the switch through the CLI.

Workaround: This issue is resolved.

• CSCug92379

Symptom: Syslog stops logging new messages on the switch.

Condition: This situation occurs if there are many Embedded Event Manager (EEM) events. The

EEM logs consume excessive file system resources, which impacts the syslog operation.

Workaround: This issue is resolved.

Open Caveats

• CSCtr10877

Symptom: Some Fibre Channel Routing (FCR) peers might get out of sync with the master switch

FCR peer after an Inter-Switch Link (ISL) flap. This might cause the intelligent application flows

not to come online or to get deleted.

Workaround: This issue might occur when using any of the following FCR intelligent applications:

–

Storage Media Encryption (SME)

–

IO Acceleration (IOA)

–

Data Mobility Manager (DMM)

Workaround: Check the intelligent applications to verify whether any flows are deleted on the

problematic switch. If they did, you must recreate flows again through the application CLI or the

Cisco Fabric Manager or Cisco Data Center Network Manager (DCNM)-SAN interface.

Enter the following supervisor CLI commands on the problematic FCR switch that triggers it to

resync its configuration with the rest of the fabric.

For a single switch, use the following command:

test fc-redirect config sync-with-fabric

If more than one peer is affected by this issue, use the following command:

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