HighQueueDropRate

Unanswered Question
Aug 5th, 2008

What could be the cause of this problem:

EVENT ID = 0000A18

ALERT ID = 000014I

TIME = Tue 05-Aug-2008 05:26:34 MSD

STATUS = Active

SEVERITY = Critical

MANAGED OBJECT = Bijsk-R1

MANAGED OBJECT TYPE = Routers

EVENT DESCRIPTION = HighQueueDropRate::Component=IF-Bijsk-R1/5 [Fa4] [10.xx.xxx.xx] [WAN];ComponentClass=Interface;ComponentEventCode=1053;Type=ETHERNETCSMACD;OutputPacketQueueDropPct=0.0 %;MaxSpeed=100000000;OutputPacketQueueDropRate=0.0 PPS;OutputPacketNoErrorRate=1.5892116 PPS;QueueDropThreshold=1;InputPacketQueueDropPct=3.2241354 %;InputPacketNoErrorRate=1.8672199 PPS;DuplexMode=FULLDUPLEX;InputPacketQueueDropRate=0.062240664 PPS;

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
4rmorris Tue, 08/05/2008 - 06:30

Can you post a "show interface" of this port? I'd bet it's a duplex mismatch with your service provider CPE (most likely), or a bad cable or sending port on the far side sending you malformed frames.

R.

m.sobolev Tue, 08/05/2008 - 07:57

Here it is:

FastEthernet4 is up, line protocol is up

Hardware is PQUICC_FEC, address is 001e.1366.46f9 (bia 001e.1366.46f9)

Description: WAN

Internet address is 10.xx.xx.xx/30

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

reliability 255/255, txload 1/255, rxload 1/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 never

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 2000 bits/sec, 2 packets/sec

5 minute output rate 3000 bits/sec, 2 packets/sec

1346614 packets input, 584867227 bytes

Received 3154 broadcasts, 0 runts, 0 giants, 36 throttles

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

0 watchdog

0 input packets with dribble condition detected

1291396 packets output, 379908345 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

It is directly connected to provider's 2801, we have about ~70 similar installations and only 2 of them have this issue.

Pravin Phadte Tue, 08/05/2008 - 09:18

Hi,

I dont see any problem with the interface.

Is it possible for you use the below command and paste the same output after 1 hr. to see if there are any errors.

#clear counters

Regards,

Pravin

m.sobolev Tue, 08/05/2008 - 21:08

Not actually an hour :)

FastEthernet4 is up, line protocol is up

Hardware is PQUICC_FEC, address is 001e.1366.46f9 (bia 001e.1366.46f9)

Description: WAN

Internet address is 10.xx.xx.xx/30

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

reliability 255/255, txload 1/255, rxload 1/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 11:48:12

Input queue: 0/75/127/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 31000 bits/sec, 23 packets/sec

5 minute output rate 53000 bits/sec, 35 packets/sec

151322 packets input, 65333051 bytes

Received 708 broadcasts, 0 runts, 0 giants, 13 throttles

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

0 watchdog

0 input packets with dribble condition detected

150556 packets output, 39241738 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

Pravin Phadte Wed, 08/06/2008 - 01:11

Hi,

As morris has siad below makes perfect sense.

You do not need to worry much about the errors since its just 1 i/p error and 1 crc errors. If these errors are casueing problem then you might need to check in.

It can be just a input packet drop which might case this small amout of errors.

Let us know if these errors are casueing any problem in the network.Or You may just ignore this errors.

Regrads,

Pravin

4rmorris Tue, 08/05/2008 - 09:20

3 errors out of 1346614 packets... that's only 0.0002%. Less than 1% is acceptable (although not desirable). If the errors don't count up regularly, it could be leftover from when the cable was connected (sometimes when you connect a cable spurious errors are generated).

Maybe your thresholds are set too low in DFM (that was DFM output in your other email, right?). You could ratchet them up to over 1% of packets and it would reduce your alerts.

If the input errors count up regularly, check/replace the cable just to be safe. Also ask the SP to provide you with similar output to see if they see errors on their side. This may point to the cable or something generated by your router that you can't see (i.e. bad network card).

BTW, is there any performance degradation across this link? I wouldn't expect any problems with so few errors.

Regards,

Ryan

Actions

This Discussion