cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1120
Views
0
Helpful
10
Replies

Lots of runt errors

jspen222
Level 1
Level 1

I have a 3560G switch and I have a lot of runts on the interface that connects to my home router. I also have a desktop connected to it and there are no runts on that interface. Is this a problem with my isp or a poorly configured interface? I’ve replaced the cable and cleared counters and they still come back 

 


GigabitEthernet0/24 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 04fe.7f3c.9598 (bia 04fe.7f3c.9598)
Description: To Verizon Port 2
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 239/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is on, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:06, output hang never
Last clearing of "show interface" counters 4d06h
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 9000 bits/sec, 8 packets/sec
5 minute output rate 1000 bits/sec, 2 packets/sec
117778518 packets input, 169269044787 bytes, 0 no buffer
Received 2038670 broadcasts (829232 multicasts)
184068 runts, 0 giants, 0 throttles
184068 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 829232 multicast, 0 pause input
0 input packets with dribble condition detected
45898211 packets output, 14869660541 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred

 

GigabitEthernet0/1 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 04fe.7f3c.9581 (bia 04fe.7f3c.9581)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters 4d06h
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 0 bits/sec, 0 packets/sec
5 minute output rate 6000 bits/sec, 5 packets/sec
45810990 packets input, 14858144340 bytes, 0 no buffer
Received 3031 broadcasts (4218 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 4218 multicast, 0 pause input
0 input packets with dribble condition detected
117160521 packets output, 169103071030 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 PAUSE output
0 output buffer failures, 0 output buffers swapped out

 

10 Replies 10

Leo Laohoo
Hall of Fame
Hall of Fame

@jspen222 wrote:

reliability 239/255​

Layer 1 issue.

I am wondering about the possibility of a duplex mismatch. Does the interface configuration specify duplex or does the interface negotiate duplex? Perhaps posting the interface configuration might be helpful? Or maybe try setting the interface to half duplex and see if the behavior changes.

HTH

Rick

184068 runts, 0 giants, 0 throttles
184068 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

The value of the "runts" and FCS errors are exactly the same.

This is not a question about the runts but rather the cable fault is causing FCS and the switch is counting the data flowing through as runts.  

I just checked again today and the reliability is 255/255, dropped to 249 after a few tries.  I have also ran a new temporary cable to switch, reset counters and the runts still occur before starting this thread.  Could this be an ISP issue or maybe the ethernet cable coming from the ONT into the back of my home router ?

This is a "classic" 3560G.  This means, if the switch is loaded with the correct IOS version, there is a built-in cable tester (called TDR).  

How to use Time-Domain Reflectometer (TDR)

57ede86c4a88ad56f99b6b458667d79c.png

TDR result looks good.  Keep an eye out on the line errors.

should I even worry about the runts


@jspen222 wrote:

should I even worry about the runts


For the time being, my priority of concern are the line errors.  If the FCS/CRC counters do not increment, the runts should stop.

what are the line errors ?

Review Cisco Networking for a $25 gift card