Oversubscribing the card would cause output drops, not input queue drops. As someone else mentioned, this is punted traffic.
I'd suggest using NetDR to find out. http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/116475-technote-product-00.html On Mon, Oct 20, 2014 at 9:42 PM, PlaWanSai RMUTT CPE IX < [email protected]> wrote: > k1#sho int te1/4 | inc dro > Input queue: 1/75/3907395/3653900 (size/max/drops/flushes); Total output > drops: 0 > > k1#sho int te1/4 | inc rat > Queueing strategy: fifo > 30 second input rate 3,570,331,000 bits/sec, 365776 packets/sec > 30 second output rate 496789000 bits/sec, 231843 packets/sec > k1#sho int te1/3 | inc rat > Queueing strategy: fifo > 30 second input rate 1,752,208,000 bits/sec, 185679 packets/sec > 30 second output rate 257731000 bits/sec, 122720 packets/sec > k1#sho int te1/2 | inc rat > Queueing strategy: fifo > 30 second input rate 3,602,173,000 bits/sec, 425089 packets/sec > 30 second output rate 2326376000 bits/sec, 351745 packets/sec > k1#sho int te1/1 | inc rat > Queueing strategy: fifo > 30 second input rate 371,024,000 bits/sec, 175235 packets/sec > 30 second output rate 2565494000 bits/sec, 291311 packets/sec > > Traffics are we trying to put through this card about 9 Gbps. > > k1#sho int te1/4 | inc dro > Input queue: 1/75/3910272/3656732 (size/max/drops/flushes); Total output > drops: 0 > > Thank you very much. > > _______________________________________________ > 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/
