Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6b) (OL-27554-03 D0, December 21, 2013)

41
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(6b)
OL-27554-03
Caveats
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.
• 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.
• CSCty59570
Symptom: After replacing a smart card that reached the maximum number of shares (16), the new
smart card gets stuck in the initializing state.
Workaround: None.
• CSCty68838
Symptom: Periodic FCIP port flaps might occur when Tape Acceleration and IP compression are
enabled and the MTU is configured at 9000. This situation might lead to a failure or an IPS core.
This symptom might be seen when the following configuration is applied to an FCIP tunnel:
– Tape Acceleration (TA) is enabled.
– Write Acceleration (required for TA) is enabled.
– IP compression in enabled.
– The MTU size is 9000.
Workaround:
This issue does not occur if TA is not configured and other parameters remain the same.
This issue does not occur if the MTU size of up to 2500 is configured and other parameters remain
the same.