Input Errors

adagost · ‎01-29-2003

Below is a quick screenshot of a port on my Cisco Catalyst 3548 switch.

I am interested in the Input Errors and what this typically indicates????

What do the collsions indicate????

What does deferred mean???

Also what is the likely effect on anything that is attached to that port due to any of these error????

Thank you very much

Here is the port output;

FastEthernet0/17 is up, line protocol is up

Hardware is Fast Ethernet, address is 0006.536c.4891 (bia 0006.536c.4891)

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 248/255, txload 198/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive not set

Auto-duplex (Half), Auto Speed (10), 100BaseTX/FX

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

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

Last clearing of "show interface" counters never

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 21000 bits/sec, 11 packets/sec

5 minute output rate 9252000 bits/sec, 795 packets/sec

21248677 packets input, 178820627 bytes

Received 13151 broadcasts, 417960 runts, 0 giants, 0 throttles

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

0 watchdog, 0 multicast

0 input packets with dribble condition detected

25764983 packets output, 3235434404 bytes, 0 underruns

0 output errors, 640538 collisions, 1 interface resets

0 babbles, 0 late collision, 213249 deferred

0 lost carrier, 0 no carrier

0 babbles, 0 late collision, 213249 deferred

0 lost carrier, 0 no carrier

14115 output buffer failures, 0 output buffers swapped out

a.manosca · ‎01-29-2003

Hi, here are some info:

Input errors

Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.

About collisions, spare time reading this very informative link:

http://www.cisco.com/en/US/tech/tk389/tk214/technologies_tech_note09186a008009446d.shtml

From the show output that you have posted, this port was

configured for auto-negotiation of duplex and speed,

and it was able to negotiate at HALF-DUPLEX with 10Mbps

link speed. Collisions occur on half-duplex configurations

because of CSMA/CD. It is recommended that if the device

connected to this port supports full-duplex and 100Mbps,

fix the speed setting on this port.

Hope this helps.