Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

increasing input queue drop

we have three 7200s that are used as LNS. we have observed that input queue is increasing and also the number of throttles. ip cef is enabled for all three routers. is this okay?

FastEthernet0/1 is up, line protocol is up

Hardware is i82543 (Livengood), address is 000b.60df.f406 (bia 000b.60df.f406)

Internet address is

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 26/255, rxload 25/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 01:05:13

Input queue: 6/75/376/18316 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue :0/40 (size/max)

5 minute input rate 10015000 bits/sec, 4209 packets/sec

5 minute output rate 10404000 bits/sec, 4412 packets/sec

16524825 packets input, 628602083 bytes

Received 0 broadcasts, 0 runts, 0 giants, 351 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

17319386 packets output, 810962401 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 output buffer failures, 0 output buffers swapped out

  • Other Network Infrastructure Subjects

Re: increasing input queue drop

A throttle happens when the Tx on device connected to this interface is sending traffic faster that the Rx on this device faster than it can handle so the interface sends a message to the processor to throttle back. You can try to increase the size of the inout queue by using the ' hold-queue xx in ' command or you can investigate the connected device to try to determine what is causing this interface to be overrun with traffic.

A lot of the time this is caused by bursty traffic i.e. broadcasts being sent ever 30 seconds for example IPX SAPs.

Is this IP only over this interface ,