Multiples output errors and collisons on interface

Answered Question
Oct 1st, 2008

Could someone kindly advise me on this problem ? I am having lots of errors on all interfaces of a 7204VXR ...

Find below the output of sh int command:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

FastEthernet0/0 is up, line protocol is up

Hardware is DEC21140A, address is 0005.0199.1000 (bia 0005.0199.1000)

Internet address is XXX.XX.96.254/24

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

reliability 253/255, txload 18/255, rxload 5/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 100Mb/s, 100BaseTX/FX

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 1d03h

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 2005000 bits/sec, 920 packets/sec

5 minute output rate 7410000 bits/sec, 1072 packets/sec

78317884 packets input, 3255578153 bytes

Received 26145 broadcasts, 0 runts, 0 giants, 14 throttles

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

0 watchdog

0 input packets with dribble condition detected

89002269 packets output, 342461943 bytes, 0 underruns

1926997 output errors, 1499022 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

FastEthernet1/0 is up, line protocol is up

Hardware is DEC21140A, address is 0005.0199.101c (bia 0005.0199.101c)

Internet address is XX.XXX.50.1/29

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

reliability 255/255, txload 2/255, rxload 10/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 100Mb/s, 100BaseTX/FX

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

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

Last clearing of "show interface" counters 1d03h

Input queue: 0/75/12/671 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 4291000 bits/sec, 558 packets/sec

5 minute output rate 879000 bits/sec, 445 packets/sec

46697566 packets input, 219771889 bytes

Received 1673 broadcasts, 0 runts, 0 giants, 12 throttles

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

0 watchdog

0 input packets with dribble condition detected

37216066 packets output, 1019476118 bytes, 0 underruns

289192 output errors, 173430 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

FastEthernet2/0 is up, line protocol is up

Hardware is DEC21140A, address is 0005.0199.1038 (bia 0005.0199.1038)

Internet address is XX.XXX.50.9/29

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

reliability 255/255, txload 2/255, rxload 7/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 100Mb/s, 100BaseTX/FX

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

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

Last clearing of "show interface" counters 1d03h

Input queue: 0/75/9/285 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 2963000 bits/sec, 473 packets/sec

5 minute output rate 904000 bits/sec, 433 packets/sec

39618408 packets input, 3194572215 bytes

Received 1675 broadcasts, 0 runts, 0 giants, 10 throttles

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

0 watchdog

0 input packets with dribble condition detected

38314724 packets output, 918804943 bytes, 0 underruns

242931 output errors, 139419 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thanks !

I have this problem too.
0 votes
Correct Answer by Jon Marshall about 8 years 2 months ago

Your interface is running at half duplex. What is this interface connecting into ?.

Try setting the interface to full-duplex and see if the errors/collisions stop. You also need to check what speed the port that this interface connects into at the other end is running at and make sure they match.

Edit - be aware that collisions are normal if you intend to run this interface at half duplex. You do not have any late collisions which is usuallu indicative of duplex mismatches.

Jon

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Jon Marshall Wed, 10/01/2008 - 12:28

Your interface is running at half duplex. What is this interface connecting into ?.

Try setting the interface to full-duplex and see if the errors/collisions stop. You also need to check what speed the port that this interface connects into at the other end is running at and make sure they match.

Edit - be aware that collisions are normal if you intend to run this interface at half duplex. You do not have any late collisions which is usuallu indicative of duplex mismatches.

Jon

gondarmonn Wed, 10/01/2008 - 12:39

Thanks Jon for your quick reply...

The 7204VXR connects to a 3Com 4400 switch. Although the router was set to full duplex, the switch was reporting a duplex mismatch and the router was generating errors, so we thought switching the router to half duplex would make everyone happy and lessen the errors, but that is obviously not happening ...

John Blakley Wed, 10/01/2008 - 12:51

I would set full on both sides. You never want to run half if given the choice. Can you set the switchport on the 3com to full?

--John

gondarmonn Wed, 10/01/2008 - 13:33

Thank you so much for your input ...

I did change the settings on the router, which stops the output errors and collisions, but generates input errors on the interface(CRC).... Forcing the switch to go full duplex, locks the port .... The switch sees the router ports as half whether they are set to full or not ...

I will try bypassing the switch and see how it goes ...

Just realized that the reliability of f0/0 is constantly 253/255 .... Does that mean a hardware problem ?

gondarmonn Thu, 10/02/2008 - 09:45

Despite what one of the techs told me (port locks up in FD), I changed the settings on the switch (f0/0) to full duplex, bypassed the switch on f1/0 and f2/0 (cross-over to two other routers), matched duplex and speed settings on the routers .... It is all clean now !!! Thanks a lot

Actions

This Discussion