to get a more accurate measure of the traffic currently flowing through the interface you could reduce the time interval to 30 seconds. You may be better able to see bursts of traffic corresponding to the output drops. conf t int s0 load-interval 30 You could also try making the output queue larger, hold-queue 4096 out unless they are causing problems for traffic & users are complaining I generally don't worry about the output drops as they are unavoidable when a larger bandwidth LAN interface feeds into a smaller WAN link as others have stated in this thread. You really want to avoid getting input drops (according to Cisco) which you don't appear to be having. You might also check how the router interface is switching the packets (process vs. fast) with "sh int switching" & "sh int stats" and make sure it is fast switching by turning on "ip route-cache" on the interface or "ip cef" on the router I hope this helps you out, as I have spent many hours on this issue. Brad
""Nate"" wrote in message news:[EMAIL PROTECTED] > guys, for some reason, our monitoring software is showing a bunch of > discards on the serial WAN circuit. The trend of discards seems to follow > the traffic stream. Here's the config for the interface: > > (CISCO3725) > Serial0/0 is up, line protocol is up > Hardware is QUICC Serial > Internet address is x.x.x.2/24 > MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 23/255 > Encapsulation HDLC, loopback not set, keepalive set (10 sec) > Last input 00:00:03, output 00:00:00, output hang never > Last clearing of "show interface" counters 06:29:38 > Queueing strategy: fifo > Output queue 0/40, 22454 drops; input queue 0/75, 0 drops > 5 minute input rate 1000 bits/sec, 0 packets/sec > 5 minute output rate 141000 bits/sec, 50 packets/sec > 9576 packets input, 722935 bytes, 0 no buffer > Received 3124 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 1605454 packets output, 336655812 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 carrier transitions > DCD=up DSR=up DTR=up RTS=up CTS=up > > Here's the config for the other end: > > (CISCO3725) > Serial1/1 is up, line protocol is up > Hardware is DSCC4 Serial > Internet address is x.x.x.1/24 > MTU 1500 bytes, BW 1544 Kbit, DLY 2000 usec, > reliability 255/255, txload 1/255, rxload 19/255 > Encapsulation HDLC, loopback not set > Keepalive set (10 sec) > DTR is pulsed for 1672712 seconds on reset, Restart-Delay is 1672712 secs > Last input 00:00:01, output 00:00:02, output hang never > Last clearing of "show interface" counters 02:59:32 > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 > Queueing strategy: fifo > Output queue: 0/40 (size/max) > 5 minute input rate 120000 bits/sec, 53 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 966133 packets input, 216228857 bytes, 0 no buffer > Received 1256 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 4380 packets output, 331039 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 carrier transitions > DCD=up DSR=up DTR=up RTS=up CTS=up > > If anyone could help me figure out why this is happening, I'd appreciate it. > Thanks. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=70793&t=70752 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
