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]
25
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: If the eth1/39 is up with traffic running and you configure a channel-group command
under the eth1/39, it displays junk values after the port channel is created.
Eugene1(config-monitor)# show interface port-channel 1
port-channel1 is up
input rate 1.22 Gbps, 2.36 Mpps; output rate 867.62 Mbps, 1.69 Mpps
RX
18446743955409989970 unicast packets 18446744035193376576 multicast packets 0
broadcast packets
18446743916893814929 input packets 18446733960470130948 bytes
0 jumbo packets 0 storm suppression packets
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
18446743955125934157 unicast packets 18446744073706175895 multicast packets 0
broadcast packets
18446743955122558435 output packets 18446736484122209748 bytes
0 jumbo packets
0 output errors 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble
0 Tx pause
1 interface resets
This happens when show int po 1 counters shows huge counter values when an interface with
running traffic is added to the port channel. And this happens to a newly created port channel that
does not have any members to begin with
.
Workaround: Use the clear counters command.
• CSCtj27113
Symptom:
When the UDLD feature is turned on and LACP rate fast is configured on an MCT
unified port on a Cisco Nexus 5000 Series or a Cisco Nexus 5500 switch, the MCT port may go to
UDLD empty echo and turn error disabled.
Workaround: Enable error recovery on the MCT unified port.
• CSCtj27689
Symptom:
If there are 10 or more discontinuous VLAN-ranges created on the switch or configured
under any of the trunk interfaces, then forwarding(fwm) service can crash on Cisco Nexus 5000
Series switch running versions 4.2(1)N1(1) or 4.2(1)N2(1). This leads to reloading of the box.
Note The actual number of VLAN ranges allowed could be slightly more than 10 depending on actual
VLAN values used while defining ranges. If this configuration of 10 or more discontinuous
VLAN-ranges is present in a start-up config, then it could lead to continuous reload of the box
due to fwm service crash each time.
There are two different conditions when this issue can be seen:
a. When 10 or more discontinuous VLAN ranges are configured under any of the trunk interfaces
using allowed vlan list command
E.g.
interface Ethernet2/4
switchport mode trunk
switchport trunk allowed vlan 221-226,237-242,253-258,269-274
switchport trunk allowed vlan add 285-290,301-306,317-322,333-338
switchport trunk allowed vlan add 349-354,365-370,381-386,397-402