Troubleshooting guide

Send documentation comments to [e-mail]
26
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(3)
OL-14116-04
Caveats
• CSCsl24773
Symptom: If there are tape paths bound to the Cisco SME interface on an MDS 9222i switch, an
upgrade on the MDS 9222i switch fails.
Workaround: This issue is resolved.
• CSCsl28481
Symptom: Cisco SME is not supported on the HP VLS6100.
Workaround: This issue is resolved.
• CSCsl53000
Symptom: In images prior to Release 3.2(3) on the Cisco 4 Gb Fibre Channel Switch Module for
IBM BladeCenter, when NPV is enabled, the VPD chassis manager does not run on the switch. The
following will occur:
– The switch will not POST to the Management Module when booting.
– The switch will not process any requests from the Management Module to disable external
management or disable external ports.
– If you try to change the switch IP address through the Management Module, the switch will
become unresponsive and will require service.
If NPV is not enabled, the switch will communicate correctly with the chassis Management Module.
Workaround: This issue is resolved.
• CSCsl65880
Symptom: On the MDS 9222i switch, the internal communication channel between the data path
processor and the module processor may fail after deleting or adding multiple tape devices in a
cluster. This may cause the host to lose communication with the tapes.
Workaround: This issue is resolved.
• CSCsl65911
Symptom: In rare instances, deleting tape devices corresponding to a target port from a Cisco SME
configuration causes the host to lose connectivity to the tape drive for a long time.
Workaround: This issue is resolved.
• CSCsl66072
Symptom: During a hitless upgrade from SAN-OS Release 3.0(x) (or lower) to Release 3.1(x) (or
higher), and a subsequent switchover or hitless upgrade, under certain runtime conditions, the
Port-Channel Manager process (PCM) may terminate and potentially cause the switch to reboot.
This issue occurs with MDS 95xx platforms only regardless of the supervisor version.
Workaround: This issue is resolved.
• CSCsl75365
Symptom: Using the Fabric Manager Standalone version, the client stops after configuration
changes are made.
Workaround: This issue is resolved.
• CSCsl02669
Symptom: When an incorrect fabric identifier is assigned to a fabric during initial discovery,
Performance Manager displays the wrong number of flows when fabrics are discovered at a later
time.
Workaround: This issue is resolved.