HP Cisco MDS 8/12c Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Rel - Page 37

Open Caveats, Symptom, Workaround, copy running-config startup-config, no shut

Page 37 highlights

Caveats Send documentation comments to [email protected] 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. 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 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 OL-25090-01 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1) 37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44

Send documentation comments to [email protected]
37
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(1)
OL-25090-01
Caveats
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.
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 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