01-24-2006 03:43 AM - edited 03-05-2019 11:45 AM
The stats below show a large amount of input errors on an interface. Cisco's definition below is not very specific and most of the defined causes can be discounted as they have 0 counts in the stats. To help track this down please could you advise on what constitutes an 'abort' and what 'Other input-related errors' could be?
Cisco's definition of Input Errors:
"Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts."
Interface Stats:
abcc5-cat6513-wc-02#sh int g13/41
GigabitEthernet13/41 is up, line protocol is up (connected)
Hardware is C6k 1000Mb 802.3, address is 0012.d9fb.a6e0 (bia 0012.d9fb.a6e0)
Description: ABCC5-AX250-SD02
MTU 1500 bytes, BW 10000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Half-duplex, 10Mb/s
input flow-control is off, output flow-control is desired
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:42, output hang never
Last clearing of "show interface" counters 20:50:44
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 30000 bits/sec, 47 packets/sec
5 minute output rate 63000 bits/sec, 7 packets/sec
3139886 packets input, 253192361 bytes, 0 no buffer
Received 63 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
11960 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
493845 packets output, 226340305 bytes, 0 underruns
1 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
abcc5-cat6513-wc-02#
01-24-2006 03:59 AM
Hi
Try changing the speed and duplex to Full and 100Mbps with respective of the settings on the other end of the device which is connected to the port.
regds
01-24-2006 04:39 AM
Many thanks for your prompt response. The attached device is only capable of 10Meg Half-Duplex
01-24-2006 09:47 PM
Hi
(1)Is the link in operation or not?
(2)Have you given "clear counters" and monitor the link and still the errors are comming?
(3)Have you tried changing the port and still the errors are comming in the changed port?
Regards
JD
01-24-2006 10:06 PM
Hi JD
1) Yes, the link is operational.
2) Yes, counters have been cleared and still seeing errors
3) Yes, port has been changed and still seeing errors.
Regards
Steve
01-24-2006 10:08 PM
JD,
4) Equipment connected to port has been changed and still seeing errors.
5) Cable has been changed and still seeing errors.
Regards
Steve
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