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 nexus5kdocs@cisco.com
41
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
Example:
banner motd #
No Unauthorized Access
#
Remove the preceding spaces to become left-aligned:
banner motd #
No Unauthorized Access
#
2) Downgrade back to 4.2(1)N2(1) and remove the Banner. Then retry upgrade back to 5.0(2)N1(1)
3) Perform a 'write erase', after which the device wont be in a boot loop. You can then paste your
configuration back - however be sure to either remove the banner motd text or modify it to become
left-aligned.
CSCtj77234
Symptom: The command "enable" is not available after rebooting the switch even though "feature
privilege" appears in the configuration. This has been observed on NX-OS 5.0.2 and 5.0.3 on both
Nexus 5000 and Nexus 7000.
Workaround: Remove and re-add "feature privilege".
CSCtj86759
Symptom:
Nexus5000 do not see LLDP neighbour that do use Organization specific unknown TLV. Those
LLDP packet should be accepted even if some TLV’s are unknown.
LLDP packets are dropped with totla unrecognized TLV error
:
(config)# sh lldp traffic int ethernet 1/16
LLDP interface traffic statistics:
Total frames transmitted: 11473
Total entries aged: 0
*Total frames received: 11323*
Total frames received in error: 0
*Total frames discarded: 11323*
Total unrecognized TLVs: 11323
Workaround: None
CSCtj88849
Symptom:
When a VLAN is simultaneously added to the vpc peer-link and other vpc ports it does not pass
traffic, suspended by a vpc.
Example:
Port-channel 100 is configured as a vpc peer-link and port-channel 101-102 are
configured as vpcs
Switch(config)# interface Port-channel 100-102
Switch(config-if)# switchport trunk allowed vlan add 123
VLAN 123 may not become operational on port channels 101 and 102.
Workaround:
1) As a best practice, the VLAN needs to be operational on the vpc peer-link first before it can
brought on vpc ports. In the above example, the configuration needs to be broken up in to three steps.
Configure the vpc peer-link