Xref: utzoo comp.dcom.lans:1113 comp.protocols.tcp-ip:2721
Path: utzoo!mnetor!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: ethernet monitor needed?
Message-ID: <3447@cbmvax.UUCP>
Date: 9 Mar 88 18:45:46 GMT
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 27

We have a single modest ethernet with a fair assortment of equipment
spread around the building.  So far, network mangagment has been on
a plug-it-in-and-see-if-it-works-good basis.  I'd like to be able to
so some monitoring with the following goals:

1) define ethernet loading and identify transceiver/interface level
   malfunctions.

2) investigate problems with systems that won't talk to each other or
   interfere with other conversations.

3) support development/debugging of in-house ethernet related hardware
   software projects.

I've seen an ad for an Excelan 5100/5300 unit that seems to fit the
bill, but they want maybe $5K for it, which seems pretty expensive for
the amount of use it would get.  I'd appreciate any comments about
this unit, good, bad or something else is better.

Also, is there any software, either 4.3 BSD or Sun related that could
be used to support this monitoring funciton, instead of going with a
piece of specialized equipment?

-- 
George Robbins - now working for,	uucp: {uunet|ihnp4|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)