I have a class c split up into two subnets. Ethernet0/1 (Subnet #1) is also displaying the same kind of errors you see below but we are not experiencing the same kind of packet loss there. It seems to be functioning properly. The second ethernet interface (Subnet #2) below Ethernet1/0, we are seeing 60% packet loss all across the board.
I have seen this before, as far as symptoms anyway. My prior experience>I went onsite to troubleshoot the same symptoms for a client and found that he had the switch crossed over to itself. That obviously was causing the problem, voila easy fix. Not the case here. Doesn't seem like a layer 1 problem. I've tried to rule out the obvious but I could be missing something for sure.
I haven't had a lot of time to dive into this. I know a lot of you are smarter then I and may be able to give me a few ideas as to some things I could try. I will post any further information any of you need in the way of router configuration, network configuration.
Everything on the wan side/serial is clean. No erros. Everything looks good from theirs to ours.
Ethernet1/0 is up, line protocol is up
Hardware is AmdP2, address is xxxx.xxxx.xxxx (bia xxxx.xxxx.xxxx)
Internet address is 6x.xxx.xxx.xxx/25
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 11/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:03, output 00:00:00, output hang never
Last clearing of "show interface" counters 12:20:09
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 3000 bits/sec, 4 packets/sec
5 minute output rate 447000 bits/sec, 461 packets/sec
203956 packets input, 73643721 bytes, 0 no buffer
Received 595 broadcasts, 0 runts, 0 giants, 0 throttles
10013 input errors, 10013 CRC, 5043 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
9460395 packets output, 1225723073 bytes, 0 underruns
94 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
94 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out