Caveats
S e n d d o c u m e n t a t i o n c o m m e n t s t o n e x u s 5 k d o c s @ c i s c o . c o m
CSCso91286
•
Symptom: When TACACS+ authentication is used to authenticate AAA users using ACS, the Cisco
Nexus 5000 Series switch ignores the user to role binding information specified in the ACS. Users
are logged in with their default roles. The default role for a new user is network-operator and for a
user who is an administrator is network-admin.
Workaround: The user-to-role binding needs to be configured locally on the Cisco Nexus 5000
Series switch for the role binding to take effect.
•
CSCsu32247
Symptom: The Cisco Nexus 5000 Series switch executes the power on self test (POST) at bootup
to validate hardware integrity of the ASICs. When a Fibre Channel port is connected to an HBA, the
HBA driver could assert a LOS that causes a false failure to be reported by POST for one of the
ASICs. As a result, all the ports serviced by the ASIC on the GEM are marked for hwFailure.
Workaround: Bypass POST at bootup by performing the following steps:
switch(config)# diagnostic bootup level bypass
switch(config)# copy running-config startup-config
switch(config)# reload
CSCsv05115
•
Symptom: The Cisco Nexus 5000 Series switch crashes if CFS callhome is enabled on a it after a
CFS callhome commit is performed on an attached MDS.
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 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.
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
20
OL-16601-01
Stampa la pagina