Router connectivity / QOS Issues

Oct 25, 2005 1 Replies

Hello all, First timer here in these forums. :) I am dealing with an issue that we have been back and forth (again and again) with the service provider



on issues where the end users are disconnected if using a PC or experience latency if on a thin client. Here is some of the interface info - any ideas on where to look? Note the high number of drops / errors / collisions? In my research, I am still thinking it is a dirty line?


Any guidance would be greatly appreciated. :)


#show int Ethernet0 Ethernet0 is up, line protocol is up ... ... ... ... MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 2/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Half-duplex, 10BaseT 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 20:53:20 Input queue: 1/75/45946/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: priority-list 1 Output queue (queue priority: size/max/drops): high: 0/20/0, medium: 0/40/0, normal: 0/60/0, low: 0/80/0 5 minute input rate 103000 bits/sec, 47 packets/sec 5 minute output rate 28000 bits/sec, 18 packets/sec 1367995 packets input, 195319817 bytes, 0 no buffer Received 1221445 broadcasts, 0 runts, 0 giants, 0 throttles 7 input errors, 0 CRC, 0 frame, 4 overrun, 3 ignored 0 input packets with dribble condition detected 147711 packets output, 25307509 bytes, 3 underruns 234 output errors, 262 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



  1. You will have collisions becuase you have a 10/half connection on the interface E0/0. See if you provide can provided 10/full

  1. It looks like priority queuing is configured, you can starve lower priority queues with this queuing mechanism. Consider changing to LLQ or CBWFQ to avoid this.

  2. Determine if the input drops are continuous or a due to traffic spikes. config "load-interval 30" on e 0/0 so you can see traffic rates averages over a shorter interval - the default of 5 minutes is too long.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required