runts error

Answered Question
Jun 17th, 2008
User Badges:

Hi,


I've connected an INTIP card from an alcatel PABX to a switch (3548XL) and I have lot of runts input error in the interface :


sh int fa0/47

FastEthernet0/47 is up, line protocol is up

Hardware is Fast Ethernet, address is 0007.50c2.862f (bia 0007.50c2.862f)

Description: PABX-CARTE_INTIP prise 21

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

reliability 222/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive not set

Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX

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

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

Last clearing of "show interface" counters 00:03:55

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 181000 bits/sec, 109 packets/sec

5 minute output rate 174000 bits/sec, 112 packets/sec

31458 packets input, 7048796 bytes

Received 0 broadcasts, 1350 runts, 0 giants, 0 throttles

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

0 watchdog, 0 multicast

0 input packets with dribble condition detected

33013 packets output, 6953859 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


What does it mean ? How to solve that ? I try to force the duplex and the speed in the intip card and in the interface of the switch with no success... The VLAN 1 is native and the VLAN 100 is in access on the interface.

Correct Answer by Pravin Phadte about 9 years 1 month ago

Hi,


At any point of time the reliability should be 255/255. If this falls down then you will notice the errors on the interface.


Its not that switch needs to have 255. But its how the interface is deisgned to notify if there is any problem with the harware inetrface or cable by dropping the reliability down from 255. If there is any other interface working clean with low reliability would be supriseing.


Regards,


Pravin

Correct Answer by ata@nmc-m.dtag.de about 9 years 1 month ago

Hi,


try to change the wire (cable) or the NIC, because the quality of the link is also not the best "reliability 222/255", i think it is a cable problem.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.3 (3 ratings)
Loading.
Pravin Phadte Tue, 06/17/2008 - 03:35
User Badges:
  • Silver, 250 points or more

Runt packets are packets that are less than the minimum packet size (64 bytes for Ethernet). They often occur due to collisions on the line. On switches the cause is usually a mis-matched duplex problem (full on one end and half on the other) caused by bad autodetection of a device. Try "hard coding" the duplex to either full or half on one or both ends and see if the problem goes away. We have had lots of issues with bad NIC cards and/or drivers that cause this. Sometimes upgrading the NIC driver helps.


Hope this helps solve your problem.


Regrads,


Pravin



mathieu.ploton Tue, 06/17/2008 - 04:10
User Badges:

It's weird because as you can see, there is no collision on the link. I try to force duplex and speed but that doesn't work. At the other hand, it's not a computer but an INT-IP Card of an Alcatel PABX.

Pravin Phadte Tue, 06/17/2008 - 04:16
User Badges:
  • Silver, 250 points or more

Hi,


i would suggest to once change it to full maunaully and check.


Also there are lot of input errors: 1350 input errors


Regards,


Pravin

mathieu.ploton Tue, 06/17/2008 - 04:28
User Badges:

I've done that, it's not working.


the number of input error = the number of runts error


Thank you again

Kevin Dorrell Tue, 06/17/2008 - 04:50
User Badges:
  • Green, 3000 points or more

Mathieu, that is precisely the point. This side is full duplex, so it does not detect collisions. Where you have a duplex mismatch, the full duplex side counts runts, while the half duplex side counts collisions.


If auto did not get rid of the problem, try forcing half duplex, just to try it.


Kevin Dorrell

Luxembourg


mathieu.ploton Tue, 06/17/2008 - 04:57
User Badges:

The INTIP side is in auto,


The switch side, i try to force in full, i still have runts, i try to force in half duplex, and it's the same.


As far as i can tell, the link is working (i can call), i'm just worried about this counter...

Correct Answer
ata@nmc-m.dtag.de Tue, 06/17/2008 - 04:47
User Badges:

Hi,


try to change the wire (cable) or the NIC, because the quality of the link is also not the best "reliability 222/255", i think it is a cable problem.

mathieu.ploton Tue, 06/17/2008 - 05:05
User Badges:

Just a think, it's a 3548XL. With a 3560G, the reliability is so much worst (193/255) with the same cable and link. How can we explain that ? The newer switch require more reliability ?

Correct Answer
Pravin Phadte Tue, 06/17/2008 - 05:11
User Badges:
  • Silver, 250 points or more

Hi,


At any point of time the reliability should be 255/255. If this falls down then you will notice the errors on the interface.


Its not that switch needs to have 255. But its how the interface is deisgned to notify if there is any problem with the harware inetrface or cable by dropping the reliability down from 255. If there is any other interface working clean with low reliability would be supriseing.


Regards,


Pravin

mathieu.ploton Tue, 06/17/2008 - 05:19
User Badges:

To speak frankly, the problem is this one :


I've been experiencing errors on this interface of the 3548 but the link is still working (it's a voice port and the calls are quite good).


I try to replace it by a 3560G, same runts errors but now the reliability of the interface is lower and the calls aren't working.

mathieu.ploton Tue, 06/17/2008 - 05:14
User Badges:

Is reliability really connected to the cable quality ? I just read that it's just number of errors / number of total frames, as errors are runts errors, i'm still facing my problem. But it could probably be the cable as the change of duplex and speed doesn't solve my problem...

ata@nmc-m.dtag.de Tue, 06/17/2008 - 05:19
User Badges:

believe me it is a Hardware (Cable/or defect port) Error. the word quality i have use only to explain the Value of relia...

mathieu.ploton Tue, 06/17/2008 - 05:20
User Badges:

It can't be a defect port, i try another one. Ok for the cable, thanks !


Just wanna know why it's working on my 3548XL, not in my 3560G, same place, same port, same conf, same runts errors...

Actions

This Discussion