Thanks Priscilla!
I'll look at this tomorrow. Off hand though I didn't see any of those
indications so far however - maybe I wasn't looking closely enough.
thanks again!
Kevin
----- Original Message -----
From: "Priscilla Oppenheimer" <[EMAIL PROTECTED]>
To: "cisco" <[EMAIL PROTECTED]>
Sent: Thursday, 22 February, 2001 18:38
Subject: Re: OT: Sniffing
> Late collisions can often be identified with a Sniffer. You'll see lots of
> packets that are longer than 64 bytes but have a CRC error and/or
alignment
> error. Sometimes you can see another station's preamble blasting into the
> packet. At the end you'll see AA AA AA, etc.
>
> In addition to an oversized topology or cable, late collisions can also be
> caused by malfunctioning hardware or a full-duplex/half-duplex mismatch
> (the most likely cause).
>
> Good luck! Let us know what you find out. Thanks.
>
> Priscilla
>
>
>
> At 05:49 PM 2/22/01, Kevin Wigle wrote:
> >Group,
> >
> >There are a few sniffer users on the list and I got a question.
> >
> >I'm using Net Xray, Sniffer Pro is available (but not installed yet).
> >
> >We have a problem of out of order packets and just recently I've noticed
on
> >the router console that we're getting late collisions.
> >
> >Now I always thought that late collisions were a product of a cable that
is
> >too long. In this case however, it's fibre from the basement up to a lab
to
> >a foirl and then a patch cord length of 10BaseT from the foirl to the
> >router.
> >
> >I'm looking at the sniffer output and I don't know what to look for to
> >identify late collisions. I don't even know if you can see them or the
> >symptoms with a sniffer.
> >
> >Can anyone (even if you watch other lists.... :-) ) comment if the
> >sniffer is even a viable tool to troubleshoot this?
> >
> >I've been going at it with our ISP for some time now and I need some
> >ammunition to get them to do something.
> >
> >Kevin Wigle
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]