Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(2)N1(1) and NX-OS Release 5.0(2)N2(1) OL-22747-02, December 2010)

Send documentation comments to [e-mail]
28
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(2)N1(1) and NX-OS Release 5.0(2)N2(1)
OL-22747-02
Caveats
Symptom: This is the case of having an STP topology with parallel links (there is a loop) on the
secondary switch with a path cost for the non-vpc ports is smaller than the vpc ports. Therefore,
peer-link would end up being blocked by STP. In this case, transient traffic loop could be formed.
Workaround: Recommended best practice topology for deployment does not have parallel links to
vPCs that have their cost tweaked to be higher than vPCs. By default all vPC links have preferred
(smaller) cost over non vPC links.
• CSCtf98638
Symptom: The message "%SYSMGR-5-SUBPROC_KILLED "System Manager (core-client) (PID
7679) hasn't caught signal 9 (no core)." is printed when the system is rebooting after an install.
Freeing memory in the file system.
2010 Apr 1 08:39:09 SW2-5020-ANIL %$ VDC-1 %$ %CALLHOME-2-EVENT: SW_CRASH
cimxmlserver in slot 1 crashed with crash type : stateful crash
[####################] 100% -- SUCCESS
Loading images into memory.
[####################] 100% -- SUCCESS
Saving supervisor runtime state.
Apr 1 08:39:18 %SYSMGR-5-SUBPROC_KILLED "System Manager (core-client)" (PID 7679)
hasn't caught signal 9 (no core).
[####################] 100% -- SUCCESS
Workaround: There is no functional impact. Ignore the message
• CSCtg33706
Symptom: Debug LACP is not available on the Fabric Extender ports
Workaround: Use LACP event histories etc. on the Fabric Extender. Other show commands should
also help with debug information.
• CSCtd15304
Symptom: When you perform a Cisco Nexus 5000 series switch software install using the Fabric
Manager, the Success Reset status message is shown just before the switch reboots.
Workaround: To determine the status of the software install, do the following:
– Close the wizard and go to the main FM screen
– Click on the Rediscover...button in the toolbar and wait for the rediscovery to complete. Once
the rediscovery is complete, you may encounter either of the scenarios:
• If the topology shows the switch with a cross, the switch is rebooting/down. Wait for some time
and repeat the second step again.
If the topology shows the switch as discovered/managed, select the corresponding fabric tree node
from the Logical Domains tree. In the right hand side panel, under the Switches tab information
about the switches along with their current versions is displayed. Use this to confirm the status of
the software install.
• CSCtd70554
Symptom: When you downgrade from the Cisco NX-OS Releases 4.1(3)N2(1) or 4.1(3)N2(1a) to
the Cisco NX-OS Release 4.1(3)N1(1) or 4.1(3)N1(1a), the feature fc-port-security command
does not get converted to feature port-security. As a result, the FC port security configuration gets
lost and remains disabled.
Workaround: After the downgrade to Cisco NX-OS Releases 4.1(3)N1(1) or 4.1(3)N1(1a),
re-enable the FC port security feature by executing the command feature port-security.