S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
40
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(2)
OL-25090-02
Caveats
This symptom was seen because the Call Home feature had duplicate message throttling disabled
and there were flapping interfaces that generated thousands of Call Home messages. These
messages filled up the ISAN directory.
Workaround
: This issue is resolved.
Open Caveats
•
CSCtn72391
Symptom
: Following a switch reload or a software upgrade, the startup configuration occasionally
does not display feature fcip.
Workaround
: Once the switch is completely up, copy the running configuration to the startup
configuration by entering the
copy running-config startup-config
command.
•
CSCtq41235
Symptom
: After you enter the
shut
command followed by the
no shut
command on a range of
interfaces, STP convergence is slow. This issue might be seen because bringing up a large number
of interfaces is delayed due to pacing of the interfaces.
Workaround
: Enter the
shut
command followed by the
no shut
command on a smaller range of
interfaces.
•
CSCtr10877
Symptom
: Following an ISL flap that isolates some switches in the fabric (and the corresponding
FCR peers) and then later merges them again, some FCR peers might get out of sync with the SSM
switch FCR peer (that is, the FCR peer that owns a configuration) during the peer discovery phase.
Consequently, some application flows might not come online, or might even get deleted.
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.
•
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.
