Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!apple!bridge2!mas
From: mas@bridge2.ESD.3Com.COM (Mike Smith)
Newsgroups: comp.dcom.lans
Subject: Re: Network monitors.  What do you want?
Keywords: network,monitors
Message-ID: <1093@bridge2.ESD.3Com.COM>
Date: 10 Nov 89 19:48:22 GMT
References: <25303@pprg.unm.edu>
Reply-To: mas@bridge2.3Com.com (Mike Smith)
Organization: 3Com Corp., Mt. View, CA
Lines: 16

In article <25303@pprg.unm.edu> cyrus@pprg.unm.edu (Tait Cyrus) writes:
>
>There were many different network monitors/analyzers shown at INTEROP 89
>each doing a little something different. . . .
> . . .  I would like to conduct a very
>informal survey in the hope that maybe the results could be used to
>show vendors what tools are 'really' needed.

I would want a diagnostic that tells me what is "wrong" with the network.
That would include all levels of all protocols for all sessions.  Nothing
I saw at InterOp '89 operated above the MAC/LLC.  However, there is some work
going on a Stanford and MIT to look for sick TCP/IP, some using AI.

Something that looks at higher layers and does more analysis of actual
traffic against published specs should be coming out in the next year or
two.  Expect to need a 20 MIPS machine or to wait all night.