Lan-to-Lan Error

[damianpablo]

hello, everybody

I have next one stage. I connect recently Lan-to-Lan, its everything ok but i can see that error in my router.

%PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision

I modified my interface Half and Full Duplex also speed modify auto to 100.

This error occur  in my interface Lan-to-Lan. 

thanks.

Damian

[Georg Pauwen]

Hello,

which device is this on ? Post the output of 'show version'...

[damianpablo]

Hi 

sorry but update information.

Show version

Cisco IOS Software, C890 Software (C890-UNIVERSALK9-M), Version 15.0(1)M4, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 29-Oct-10 00:19 by prod_rel_team

ROM: System Bootstrap, Version 12.4(22r)YB3, RELEASE SOFTWARE (fc1)

[Richard Burts]

There are several things that can cause late collisions. One of them is a duplex mismatch where your devie is operating as half duplex and the connected device is full duplex. Can you post the output of show interface for your interface that is having this message?

HTH

Rick

[damianpablo]

interface FastEthernet8
description Lan-to-Lan
no ip address
ip flow ingress
ip flow egress
duplex full
speed 100
!
!
interface FastEthernet8.423
encapsulation dot1Q 423
ip address 1.1.1.1 255.255.255.248

Error

*Mar 13 13:28:33.447: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision
*Mar 13 13:28:33.467: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision
*Mar 13 13:28:33.487: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision
*Mar 13 13:28:33.523: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision
*Mar 13 13:28:33.543: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision
*Mar 13 13:28:34.067: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision
*Mar 13 13:28:34.103: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision

[Georg Pauwen]

Hello,

post the output of:

show interfaces FastEthernet8

[damianpablo]

this is error.

*Mar 21 13:26:13.231: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision
*Mar 21 13:26:13.255: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision
*Mar 21 13:26:13.303: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision8
FastEthernet8 is up, line protocol is up
Hardware is PQII_PRO_UEC, address is 503d.e5d9.05b3 (bia 503d.e5d9.05b3)
Description: Lan-to-Lan
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 254/255, txload 2/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., 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 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 113000 bits/sec, 60 packets/sec
5 minute output rate 1037000 bits/sec, 100 packets/sec
110474 packets input, 23494518 bytes
Received 2 broadcasts, 0 runts, 0 giants, 0 throttles
2 input errors, 0 CRC, 0 frame, 0 overrun, 2 ignored
0 watchdog
0 input packets with dribble condition detected
139370 packets output, 162032001 bytes, 0 underruns
3378 output errors, 156 collisions, 17 interface resets
0 unknown protocol drops
0 babbles, 2813 late collision, 565 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

[Richard Burts]

Thank you for the output of show interface. This makes it clear that the interface is operating at half duplex and that leads to the situation with late collision.

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

HTH

Rick

[damianpablo]

Richard What do you say? interfaces my ISP is Half-Duplex?

thanks

[Joseph W. Doherty]

As Rick notes, a late collision can happen when running half duplex, but it really indicates a network issue (such as when he noted interacting with another interface running full duplex), i.e. you shouldn't normally see these type of collisions even when running half duplex.

[damianpablo]

ok, I set my interface fastethernet 8 in manual half duplex. but that intnerface fastethernet 8 continue with a problem.

mi interface fastethernet 8 is connect to WAN

my interface giga 0 connect to my LAN

when i shut down my interface lan the problem is solved.

my question is  why the problem is fastethernet 8? 

i am calling to my ISP i comment that need force your interface in auto duplex.

[Richard Burts · Accepted solution]

You ask why I say that the interface is half duplex. Here is your output

FastEthernet8 is up, line protocol is up
Hardware is PQII_PRO_UEC, address is 503d.e5d9.05b3 (bia 503d.e5d9.05b3)
Description: Lan-to-Lan
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 254/255, txload 2/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s, 100BaseTX/FX

You also ask why the issue is FastEther8. That is pointed out in the error message

Mar 21 13:26:13.231: %PQII_PRO_FE-5-LATECOLL: PQII_PRO/FE(8), Late collision

You say that if you shut down the LAN that the errors stop and ask why. I am guessing that when the LAN is down there is little or nothing that you are sending to the WAN and little or nothing that the WAN is sending to you. With little or nothing going through the interface then there would not be collisions.

It would be good to find out why the WA interface is operating at half duplex. Hopefully the provider can help you work out something that will have both sides operating the same way, either both half duplex or both full duplex (which would be preferable).

HTH

Rick

[damianpablo]

thanks you Richard

I am understanding all right now.

[Richard Burts]

I am glad that you understand it now and that our explanations have been helpful. Thank you for marking this question as solved. This will help other readers in the forum to find discussions that have helpful information. These forums are excellent places to ask questions and to learn about networking. I hope to see you continue to be active in the forum.

HTH

Rick

[Georg Pauwen]

Hello,

this could be a bug...can you upgrade your IOS to e.g. 15.1 ?