late collision on all interfaces 0/0 and 0/1

[kaseykelley1993]

Hello everyone,

I am having a problem with a lot of late collision of my cisco 3825 router. Duplex has been hard coded and i am still getting a lot of them. When i clear counters and then check right after there is non but in about 5 mins there are over 100 of them... But now we got it hard coded so when we reboot the router and then check the interface there are 400000 late collision.

Here is the out put

GigabitEthernet0/0 is up, line protocol is up
Hardware is BCM1125 Internal MAC, address is 0021.55e6.8fe0 (bia 0021.55e6.8fe
0)
Description: (data vlan)
Internet address is 172.16.10.1/24
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive set (10 sec)
Full Duplex, 100Mbps, media type is RJ45
output flow-control is XON, input flow-control is XON
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:09, output 00:00:03, output hang never
Last clearing of "show interface" counters never
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
11 packets input, 4326 bytes, 0 no buffer
Received 11 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 3102370667 multicast, 0 pause input
14 packets output, 2537 bytes, 0 underruns
0 output errors, 3216499476 collisions, 3 interface resets
2 unknown protocol drops
0 babbles, 4293913741 late collision, 0 deferred
3 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

GigabitEthernet0/0.20 is up, line protocol is up
Hardware is BCM1125 Internal MAC, address is 0021.55e6.8fe0 (bia 0021.55e6.8fe
0)
Description: (voice vlan 20)
Internet address is 172.16.20.1/24
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 20.
ARP type: ARPA, ARP Timeout 04:00:00
Keepalive set (10 sec)
Last clearing of "show interface" counters never

GigabitEthernet0/1 is up, line protocol is up
Hardware is BCM1125 Internal MAC, address is 0021.55e6.8fe1 (bia 0021.55e6.8fe
1)
Description: Wan (ISP)
Internet address is 63.888.888.888/29
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 100Mbps, media type is RJ45
output flow-control is XON, input flow-control is XON
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 never
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 3000 bits/sec, 4 packets/sec
5 minute output rate 3000 bits/sec, 4 packets/sec
133 packets input, 13419 bytes, 0 no buffer
Received 38 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 3153607898 multicast, 0 pause input
92 packets output, 10991 bytes, 0 underruns
0 output errors, 2496646871 collisions, 3 interface resets
3 unknown protocol drops
0 babbles, 2147439323 late collision, 0 deferred
2 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
NVI0 is up, line protocol is up
Hardware is NVI
Interface is unnumbered. Using address of GigabitEthernet0/0 (172.16.10.1)
MTU 1514 bytes, BW 56 Kbit/sec, DLY 5000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation UNKNOWN, loopback not set
Keepalive set (10 sec)
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

You shouldn't be getting any kinds of collisions on a full duplex port.

This a physical p2p manually configured on both sides to 100/full?

Why are your hard coding duplex?

[kaseykelley1993]

Beucase of the 2147439323 late collision and that still did not fix the problem. Its on both interfaces. The WAN and the LAN interface. Cisco tech support had us do that and it did not fix the problem how do i know if it is a bad wic?

[Richard Burts]

I find this part of the output interesting and puzzling

92 packets output, 10991 bytes, 0 underruns
0 output errors, 2496646871 collisions,

so how are there 92 packets output and 2496646871 late collisions?

It sure looks like you have used the clear command but it does not reset the counter for late collisions. Which makes me wonder how many of those late collisions happened before you changed the interface configuration? I would look for some way to reset the counter for late collisions (perhaps a reload of the device) and then see what is happening with late collisions.

HTH

Rick

[kaseykelley1993]

That is with the clear command. After that i did a reboot and thats what you are seeing right now

[Masoud Pourshabanian]

Hello,

How about other side? Check other side to see if it is full duplex. It will cause problem if one side is full and other is half. You router does not sense the link and sends at any time causing collision. If you do not have access to otherside, try to use half duplex instead and check the result.

Masoud

[kaseykelley1993]

Here is the other end. I had done everything that you said todo before and still get the same problem..

Here is the sw

FastEthernet0/24 is up, line protocol is up (connected)
  Hardware is Fast Ethernet, address is 0017.e0fd.949a (bia 0017.e0fd.949a)
  Description: truck
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s, media type is 10/100BaseTX
  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 1d01h
  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 37000 bits/sec, 12 packets/sec
  5 minute output rate 31000 bits/sec, 14 packets/sec
     6768831 packets input, 8958464918 bytes, 0 no buffer
     Received 2112 broadcasts (1872 multicasts)
     0 runts, 0 giants, 0 throttles
     118 input errors, 64 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 1872 multicast, 0 pause input
     0 input packets with dribble condition detected
     3998931 packets output, 427206242 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

[Masoud Pourshabanian]

You have also error in your switch.

118 input errors, 64 CRC

Is there any device between the switch and router?

What is the link between them?

[kaseykelley1993]

Nope

[Masoud Pourshabanian]

Try to change the cable between them. Your signals may have interference on each others ond router recognizes them as collision.

Masoud