Re: [nsp] REG: Cisco 2610 problems

From: Brian (bri@sonicboom.org)
Date: Fri Feb 09 2001 - 13:19:48 EST


Max ether cable length is 100 meters I believe, that's quite a run..

                        Bri

----- Original Message -----
From: "Kent Yu" <yux@lucent.com>
To: <cisco-nsp@puck.nether.net>
Sent: Friday, February 09, 2001 10:14 AM
Subject: Re: [nsp] REG: Cisco 2610 problems

> I think if the cable is longer than the ethernet specification, you will
> also get this message.
>
> Kent
> ----- Original Message -----
> From: "ken lindahl" <lindahl@ack.Berkeley.EDU>
> To: <cisco-nsp@puck.nether.net>
> Sent: Friday, February 09, 2001 11:51 AM
> Subject: Re: [nsp] REG: Cisco 2610 problems
>
>
> > i've not seen an answer to this question:
> >
> > On Fri, 9 Feb 2001, "Vinod Anthony Joseph Cherunni" <vac@dsqworld.com>
> wrote:
> > >I seem to getting this message in my router log continously, Is this an
> > >indication of a network with high collissions, or else does it indicate
> > >any fault in the router ethernet port.
> > >
> > >"Feb 9 19:35:50.577 IST: %AMDP2_FE-5-LATECOLL: Ethernet0/0 transmit
> error
> > >"
> >
> > it indicates a late collision, which means that a collision occurred
after
> > the period during which a collision should occur on a correctly
> functioning
> > net. it does not necessarily indicate high collisions; rather it
indicates
> > that some device(s) is malfunctioning; it is transmitting after the time
> > where it should have detected a collision and backed off. i think you
> > cannot infer from the message whether the problem lies with the router
> > interface or with another device.
> >
> > the system error message doc
>
(http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121sup/121s
> ems/index.htm) says:
> >
> > Error Message
> >
> > %AMDP2_FE-5-LATECOLL: AMDP2/FE 0/0/[dec], Late collision
> >
> > Explanation Late collisions occurred on the Ethernet or 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.
> >
> > (yes, the error message has different text; i could not find one with
the
> > exact text you listed.)
> >
> > cheers,
> > ken
>



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:28 EDT