Input errors on 6513 and input errors and CRC's on a 3560

[djgizmo250]

One of our departments are complaining about a "slow" network from one device to another.

Can you help me figure out why I'm getting input errors and CRC's?

Here's the interface on the 6513:

6513#sh int g9/26

GigabitEthernet9/26 is up, line protocol is up (connected)

Hardware is C6k 1000Mb 802.3, address is 0014.69d9.9081 (bia 0014.69d9.9081)

Description: PACS.DAS119

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

reliability 254/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s

input flow-control is off, output flow-control is on

Clock mode is auto

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

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

Last clearing of "show interface" counters 00:11:21

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 6000 bits/sec, 8 packets/sec

5 minute output rate 8000 bits/sec, 7 packets/sec

5770 packets input, 547560 bytes, 0 no buffer

Received 0 broadcasts (0 multicasts)

0 runts, 0 giants, 0 throttles

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

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

5312 packets output, 680843 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

6513#

Here's the interface on the 3560:

3560#sh int g0/35

GigabitEthernet0/35 is up, line protocol is up (connected)

Hardware is Gigabit Ethernet, address is 0017.0ea0.b323 (bia 0017.0ea0.b323)

Description: DAS4

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

reliability 246/255, txload 3/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/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 00:10:29

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 543000 bits/sec, 87 packets/sec

5 minute output rate 1428000 bits/sec, 126 packets/sec

55011 packets input, 16326049 bytes, 0 no buffer

Received 5 broadcasts (0 multicast)

0 runts, 0 giants, 0 throttles

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

0 watchdog, 3 multicast, 0 pause input

0 input packets with dribble condition detected

90548 packets output, 120036928 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

3560#

[Mark Yeates · Accepted solution]

Typically the errors you are seeing are related to a bad cable. Please check the cables and make sure they haven't been mangled, or crimped improperly.... etc

Here is a good interface troubleshooting guide.

http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a008015bfd6.shtml

Mark

[djgizmo250]

Wow, great! Thank you. I wish I had this a long time ago!

[glen.grant]

Is there a reason you are restricting 2 gig interfaces to 100 meg ? Can you post a "show run interface g9/26 and sh runn int g0/35 . Myself I would make both sides auto/auto for speed and duplex and let it negotiate 1000 meg. The problem looks to be on output side from the 6513 to the 3560 whether its a patch cable or whatever.

[djgizmo250]

The vendor stated that both interfaces should be set to duplex full and speed 100 in order for their devices to work.

[glen.grant]

To me it looks like the vendor did not do his side like he told you to, like he left his side as auto and you have your side hardcoded. you can test by doing a extended ping across that link and use like 1400 byte packets and see how many pings drop .