It is likely the flushed traffic is in the input queue to CPU, but a
6500 can also account for rx queuing drops in this drops counter as an
aggregate counter.
In the show queueing output, we see 81 packets dropped:
Packets dropped on Receive:
BPDU packets: 0
queue thresh dropped [cos-map]
---------------------------------------------------
1 1 81 [0 1 2 3 4 5 6 7 ]
I would watch the individual interfaces (show queueing interface) to see
if these dropped packets add up to the input queue drops you see on the
port-channel.
Can you run "show module" for us?
Regards,
John Gill
cisco
919.392.2309
On 6/11/11 12:41 PM, Pete Lumbis wrote:
The input queue is the queue between the interface and the CPU, only
process switched traffic hits this queue. Drops in the input queue are
almost always due to a busy CPU.
If you happen to have packets in the queue (the first number is
greater than 0) you can run "show buffers input interface<INTERFACE>
dump" and decode the packets.
Also check out this troubleshooting doc
http://www.cisco.com/en/US/products/hw/routers/ps133/products_tech_note09186a0080094791.shtml
-Pete
On Fri, Jun 10, 2011 at 7:46 AM, Mohammad Khalil<[email protected]> wrote:
hi all
i have etherchannel consisting of 5 G interfaces
the port-channel is assigned to VLAN 10 (SVI created)
i cleared the counters on the interface yesterday and today
Input queue: 0/75/962/962 (size/max/drops/flushes)
what is the issue ?
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
