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]
26
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
switchport trunk allowed vlan add 413-418,429-434,445-450,461-466
....
....
b. VLANs created on the switch themselves comprise of 10 or more discontinuous ranges.
vlan
1,101-103,127-129,153-154,160-161,167-168,174-175,181-182,188-189,195-196,202-203,209-
222,237-238,253-254,269-270,285-286,301-302,317-318,333-334,349-350,365-366,381-382,39
7-398,413-414,429-430,445-446,461-462,477-478
....
....
Workaround: - Allowed VLAN list configured under any of the trunk interfaces should comprise
of less than 10 discontinuous VLAN-ranges.
- VLANs created on the switch should comprise of less than 10 discontinuous ranges.
- If this configuration of 10 or more discontinuous VLAN-ranges is already present in start-up
config from earlier releases, then 'write erase' is required by breaking into kickstart prompt.
• CSCtj29477
Symptom:
When the UDLD feature is turned on, Cisco Nexus 5000 Series vPC unified port may be
error disabled due to UDLD Empty echo upon MCT flap. Another similar symptom is the other
switch that is connected to the Cisco Nexus 5000 Series.
Workaround: Enable error recovery on both the MCT and vPC port.
• CSCtj34994
• CSCtj42415
Symptom:
When a Cisco Nexus 2000 Series Fabric Extender port that is a member of more than
2000 VLANs is configured as a TX span source, the following syslog error is printed:
%$ VDC-1 %$ %FWM-2-FWM_SPAN_EGR_MCAST_ERROR: FwM SPAN fex source programming has
failed. Error: Fex Po/interfaces should be part of < 2000 vlans to be a monitor
source.
Workaround: Once VLAN membership for the FEX port is brought down to a reasonable number,
the issue can be cleared by either performing a shut/no shut of the monitor session or removing the
Fabrix Extender port as SPAN src and adding it back
• CSCtj44387
Symptom:
On the Cisco Nexus 5000 Series switches, performing snmpwalk on a BRIDGE-MIB
when the vpc peer-link is going down, causes high cpu utilization. This may result in some processes
crashing.
Workaround: A BRIDGE-MIB should not be used under stressful conditions.
• CSCtj53287
Symptom:
On the Cisco Nexus 5500 platform, due to a limitation Fibre channel ports cannot be
configured as RX sources in a monitor session. The following sources are blocked in the CLI as a
result of the above limitation:
– Fibre channel ports: fc x/y
– SAN port channels: san-port-channel x
– VSAN: vsan x
This limitation does not apply to FCoE VLAN and VFC interfaces. FC and SAN port channel
interfaces can be configured as TX sources with no issue.