Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!ucsd!ucbvax!obelix.twg.com!lefty
From: lefty@obelix.twg.com
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Query - Ethernet collisions
Message-ID: <9005300902.ab00402@Obelix.TWG.COM>
Date: 30 May 90 20:11:29 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26

In <98@fedeva.UUCP>, Bill Daniels 
<usc!jarthur!elroy.jpl.nasa.gov!zardoz.cpd.com!dhw68k!fedeva!bill@ucsd.edu> 
writes:

> We recently acquired an Exelan LANalyzer.  During our first uses of it,
> we noticed that about 40% of the packets on one ethernet segment (which
> is remotely bridged to another) show up as "Collision detected in preamble".
> This segment is not busy necessarily when this happens.  The actual number 
> of collisions reported seems fairly constant even as traffic picks up.  On
> a very quiet net (~ 2 packets / sec.) I see about 20 errors over ~ 30 secs.
> When the segment is a little more active (~ 1000 packets / sec.) the error
> rate is just about the same.  
> 
> I have tried disconnecting the devices that the errors are associated with
> but the collisions just move to the packets associated with other devices.
> 
> Any clues?

My immediate guess would be a marginal terminator somewhere...

|<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>|
|           David N. Schlesinger || "When I have nothing to say,       |
|           The Wollongong Group ||  my lips are sealed;               |
| Internet: Lefty@twg.com        ||  say something once,               |
| POTS:     415/962-7219         ||  why say it again?" -- David Byrne |
|<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>|