01-22-2014 07:02 PM - edited 03-04-2019 10:08 PM
Dear All,
Just a quick one, i've 380 CRC errors incremented on the interface between me and the ISP (in a period of 3hours)
Last clearing of "show interface" counters 03:18:41
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 527000 bits/sec, 201 packets/sec
5 minute output rate 445000 bits/sec, 199 packets/sec
1622419 packets input, 533479907 bytes
Received 276 broadcasts, 84 runts, 0 giants, 0 throttles
384 input errors, 384 CRC, 0 frame, 0 overrun, 0 ignored
Is that normal or should be checked.
Thanks,
Fady
01-22-2014 07:09 PM
It needs to be checked. You can try replacing the cable first to see if it helps. What type of connection is this? Serial? Ethernet?
HTH,
John
*** Please rate all useful posts ***
01-22-2014 07:18 PM
thanks John, this is an Ethernet connection.
Will try to change the cable and see.
Thanks again.
01-22-2014 07:19 PM
Can you post your "show int
HTH,
John
*** Please rate all useful posts ***
01-22-2014 07:21 PM
FastEthernet0/0 is up, line protocol is up
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 03:33:37
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 517000 bits/sec, 201 packets/sec
5 minute output rate 457000 bits/sec, 199 packets/sec
1804975 packets input, 591659825 bytes
Received 292 broadcasts, 90 runts, 0 giants, 0 throttles
424 input errors, 424 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
1802931 packets output, 517603366 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
01-22-2014 07:27 PM
Thanks for posting this. Speed/duplex is correct. Usually, CRC errors are from mismatched duplex settings. How do you have your interface configured? Auto or hardcoded? If it's auto, you may try to change it to 100/full hardcoded. If it's hardcoded, you may try to change it to auto for speed/duplex. The provider could have their side at auto and you have yours hard coded. If that's the case, the other end could see half duplex and it could cause your crc errors.
HTH,
John
*** Please rate all useful posts ***
01-22-2014 07:48 PM
Hi John,
thanks for the useful info, honestly i don't know how it is configured as it was implemented back in the days before me.
Will try to check this and as well reach out to the provider and see what's on their side.
Thanks,
Fady
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide