Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!pikes!boulder!daemon
From: daly@cisco.com (Tom Daly)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: cisco router 10baset (synoptics)
Message-ID: <26364@boulder.Colorado.EDU>
Date: 17 Sep 90 02:01:02 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 14

One thing that I failed to mention regarding the 'dribble' problem is that
it would be quite repeatable and show up as a failure of hosts to communicate.
Greg's comments regarding misc fragments showing up as framing errors are valid

If repeater equipment is generating dribbles, then you would get symptoms
like host A can't talk to host B through a path that includes a wiring system
and a router.  Since many other things can cause this, an additional symptom
to look for is the framing errors.  Ideally, one would start with something
like A can't talk to B, and on a lightly used net, everytime A tried the 
framing error count would bump. i.e., correlate the inability of hosts to
communicate with the framing errors, as opposed to looking for a background
level of framing errors on the net.

Tom Daly