Send documentation comments to nx5000-docfeedback@cisco.com
22
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1)
OL-16601-01
Caveats
Workaround: None.
• CSCsv30392
Symptom: The Cisco Nexus 5020 switch has a Pktmgr memory leak in version 4.0(0)N1(2). This
causes STP to stop functioning after awhile causing a Layer 2 Loop. After breaking the redundant
connections, the switch is unable to be managed, due to a No buffer space available message.
Condition: The Cisco Nexus 5020 switch is setup in a triangle topology with two 6500 switches.
Code version 4.0(0)N1(2) is loaded on the the Cisco Nexus 5020 switch. The redundant link had to
be shut down in order to stop the loop.
Workaround: To fix the broken state, do not configure SVI.
• CSCso99821
Symptom: If PVLANs are created and deleted continuously and without pausing, the Ethernet
interface may not be configurable and you have to reboot.
Workaround: Pause between the creation and deletion of PVLANs and do not perform multiple
PVLAN operations at the same time. Alternately, you can create a PVLAN before any PVLAN
interface is created and remove the switch port PVLAN from the interface before the PVLAN is
deleted.
• CSCsr52118
Symptom: When you perform delete, add, shutdown or no shutdown operations on a VLAN, the
port channel interface may lose VLAN membership in the forwarding plane. As a result, ports will
not participate in any of the forwarding operations on that VLAN. This behavior applies to access
port channels where the switch port access VLAN configuration matches the deleted and re-added
VLAN. This behavior can occur for trunk port channels, if the deleted or re-added VLAN matches
the native VLAN of the port channel.
Workaround: Enter the shutdown command or the no shutdown command on the port channel.
• CSCsr39670
Symptom: Although SNMP notification is enabled on the switch, traps for the power supply and fan
modules are not received.
Workaround: None.
• CSCsr47531
Symptom: When a VSAN is configured as SPAN source, traffic from all the member ports is
spanned to the SPAN destination port. When a switch is rebooted, the VSAN SPAN source remains
in the down state.
Workaround: Delete and add the VSAN sources for the SPAN session.
Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2a)
• CSCsu08988
Symptom: Telnet access is available only after reloading the Nexus 5020 switch with the no telnet
server enable command running.
Workaround: Execute the no telnet server enable command once again after reload even if the
command is saved in the startup-config. Additionally, you can also apply filters to the SVI to allow
only trusted hosts to communicate with the system.
To Next Page
Loading...
Need help?
General
