Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8), (OL-27554-04, December 10, 2012)

42
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.2(8)
OL-27554-04
Caveats
This symptom might be seen when the IP address is configured on the mgmt0 interface.
Workaround: This issue is resolved.
• CSCub92848
Symptom: Configuring the LDAP search map in the output of the show ldap-server groups
command incorrectly shows “Serach map” which should be “Search map.”
This symptom might be seen when configuring LDAP on a Cisco MDS 9000 switch.
Workaround: This issue is resolved.
• CSCtz91659
Symptom: The show tech port-channel command should include additional outputs.
Workaround: This issue is resolved.
• CSCua22667
Symptom: Inband frames that are dropped at the supervisor module are not included in some
debugging commands.
Workaround: This issue is resolved.
• CSCuc09003
Symptom: A CLI command is needed to allow a user to enable or disable sending RSCNs to edge
devices when the switch management configuration changes because the FC-MI specification
changed.
By default, Cisco NX-OS software will not send RSCNs when the switch management configuration
changes. The rscn permit type nport event switch-config command is a new command to change
this behavior is:
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.
• 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