07-16-2008 07:12 AM - edited 03-06-2019 12:13 AM
Half-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 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:32:32
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 0 bits/sec, 0 packets/sec
7694 packets input, 1060476 bytes, 0 no buffer
Received 0 broadcasts (424 IP multicasts)
0 runts, 0 giants, 0 throttles
39 input errors, 39 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 460 multicast, 0 pause input
0 input packets with dribble condition detected
8377 packets output, 1194833 bytes, 0 underruns
0 output errors, 27 collisions, 0 interface resets
0 babbles, 10 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
Gi0/20 0 40 0 40 0 0
Port Single-Col Multi-Col Late-Col Excess-Col Carri-Sen Runts Giants
Gi0/20 17 14 13 0 0 0 0
this is connected to a 10mb ethernet link. so it is common to see collision errors or late collsion but not sure about the input errors or CRC.
both sides are setup to auto negotiate on the duplex and speed. is it best to hardcode the speed to 100full and duplex half?
3560 is connected to a 6509.
07-16-2008 07:51 AM
CRC errors are mainly caused by duplex mismatch, bad cables, faulty switch ports, or NIC software/hardware issues. You should definitively start by hardcoding (downtime to avoid problems) and if problem persist, try to use a different cable and afterwards a different port.
07-16-2008 08:08 AM
you should be able to hardcode the speed/duplex to the maximum that both support.
at least 100/full should be supported on both.
07-16-2008 08:30 AM
the circuit is only 10mb ethernet. and on the 6500 the interface is gig and also the 3560 interface is gig. the port settings on both sides is auto/auto but are negotiating on 10mb/half duplex.
when i hardcode the interfaces to 100MB / full duplex, port appears down!
are CRC's error normal when receiving late collision?
07-16-2008 10:46 AM
As you mentioned the circuit is 10mb ethernet. Is it half-duplex or full, if it is full-duplex try to config 3560 or 6500 interface to 10mb full-duplex.
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