At 10:25 AM 1/18/01, Tony van Ree wrote:
>Hi,
>
>Late collisions will often occur when you have one end at full duplex the
>other at half duplex. The full duplex will keep sending even after the
>poor little half duplex has started to transmit. This interupts the half
>duplex well into its transmission and whammo a late collision. This also
>often occurs when autonegotiate is set on a switch and all appears to be
>fine. I have found that to configure both ends manually is best.
Why does anyone use autonegotiate?! Does it EVER work? &;-) Just wondering.....
Priscilla
>Just a thought
>
>Teunis,
>Hobart, Tasmania
>Australia
>
>
>On Wednesday, January 17, 2001 at 02:48:50 PM, Jim Healis wrote:
>
> > From CCO:
> >
> > Error Message
> > %AMDP2_FE-5-LATECOLL: AMDP2/FE([dec]/[dec]), Late collision
> >
> > Explanation Late collisions occurred on the Ethernet/Fast Ethernet
> > interface.
> >
> > Recommended Action If the interface is Fast Ethernet, verify that both
> > peers are in the same duplex mode. For regular Ethernet, the system
> > should recover. No action is required.
> >
> >
> >
> > Kelly D Griffin wrote:
> >
> > > Does anyone know what causes this error message?
> > >
> > > Jan 17 16:32:35 CDT: %AMDP2_FE-5-LATECOLL: Ethernet0/1 transmit error
> > >
> > > Kelly D Griffin, CCNA
> > > Network Engineer
> > > Kg2 Network Design
> > > http://www.kg2.com
> > >
________________________
Priscilla Oppenheimer
http://www.priscilla.com
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
