HP Cisco MDS 8/12c Release Note page 37

Cisco mds 9000 family release notes for cisco mds nx-os release 5.2(1) (ol-25090-01, july 2011)
Hide thumbs Also See for Cisco MDS 8/12c:
Table of Contents

Advertisement

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
Open Caveats
OL-25090-01
Symptom: The interval for the default port-monitor policy is incorrect. The default is 60 seconds,
but it should be 1 second.
Workaround: This issue is resolved.
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 do the following. If the application flows do not
come online, then the application CLI commands s may 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 DCNM-SAN interface.
CSCtr24502
Symptom: Following a switch reload or a module reload, throughput drops with local switching
enabled because the local switching configuration is lost after the reload.
Workaround: Enable local switching again after the switch reloads or the module reloads.
CSCtq76711
Symptom: The 8-port FCoE module (DS-X9708-K9) fails to boot up after it is power cycled. This
issue might be seen if there are enough local routes to exhaust the hardware table space on the FCoE
module.
Workaround: Remove enough local routes so that the remaining routes do not exhaust the hardware
resources of the FCoE module and then reload the FCoE module.
CSCtq79432
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1)
Caveats
37

Advertisement

Table of Contents
loading

Table of Contents