[c-nsp] 6509 input queue drops

[Lee Riemer]

Is the port the traffic is going to egress running at a lower rate or 
congested?

On 7/21/2010 10:58 AM, Chris Lane wrote:
> All,
>
> I have a 48 port 10/100/1000mb EtherModule      WS-X6148-GE-TX  on a 6509
> running s72033-advipservicesk9_wan-mz.122-33.SXH7.bin
> Interface built as layer3 with a p2p site to site
> experiencing tons of Input queue drops but no other errors on port.
> cr.nyc1.ny#sh int g3/2
> GigabitEthernet3/2 is up, line protocol is up (connected)
>    Hardware is C6k 1000Mb 802.3, address is
>    Description: xxxxxxxxx
>    Internet address is
>    MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
>       reliability 255/255, txload 4/255, rxload 1/255
>    Encapsulation ARPA, loopback not set
>    Keepalive set (10 sec)
>    Full-duplex, 1000Mb/s, media type is 10/100/1000BaseT
>    input flow-control is off, output flow-control is off
>    Clock mode is auto
>    ARP type: ARPA, ARP Timeout 04:00:00
>    Last input 00:00:04, output 00:00:05, output hang never
>    Last clearing of "show interface" counters 00:07:15
> *  Input queue: 0/75/45605/0 (size/max/drops/flushes); Total output drops: 0
> *
>    Queueing strategy: fifo
>    Output queue: 0/40 (size/max)
>    5 minute input rate 5511000 bits/sec, 3615 packets/sec
>    5 minute output rate 19240000 bits/sec, 5080 packets/sec
>    L2 Switched: ucast: 68 pkt, 4484 bytes - mcast: 79854 pkt, 5112676 bytes
>    L3 in Switched: ucast: 1116996 pkt, 233979838 bytes - mcast: 0 pkt, 0
> bytes mcast
>    L3 out Switched: ucast: 2138144 pkt, 982224161 bytes mcast: 0 pkt, 0 bytes
>       1496205 packets input, 261671862 bytes, 0 no buffer
>       Received 358394 broadcasts (0 IP multicasts)
>       0 runts, 0 giants, 2606 throttles
>      * 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored*
>       0 watchdog, 0 multicast, 0 pause input
>       0 input packets with dribble condition detected
>       2158283 packets output, 988796454 bytes, 0 underruns
>       *0 output errors, 0 collisions, 0 interface resets*
>       0 babbles, 0 late collision, 0 deferred
>       0 lost carrier, 0 no carrier, 0 PAUSE output
>       0 output buffer failures, 0 output buffers swapped out
>
> Anybody experience such an odd error?
>
>