Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!hplabs!hpl-opus!hpccc!doerfler
From: doerfler@hpccc.HP.COM (Mike Doerfler)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Interfaces statics don't jibe with Sniffer's
Message-ID: <14050007@hpccc.HP.COM>
Date: 4 Sep 90 21:47:09 GMT
References: <25514@boulder.Colorado.EDU>
Organization: HP Corp Computing & Services
Lines: 24


>My experience with the Sniffer is that it is a good protocol analyzer, but a
>so-so network analyzer. I also use an HP analyzer and it shows far more errors
>and such than the Sniffer. Because the Sniffer uses a more or less standard
>interface, it can't seem to see some types of errors. The HP has a fully custom
>interface and seem to catch EVERYTHING. (But it's not much of a protocol
>analyzer.)

We did some investigation into the very same situation.  What we found out
is that the cisco's can increment multiple error counters on one error.  Take
collisions for instence, collisions can result in multiple increments of
runts, collisions etc.  

As far as the HP4972, it is a very good product but does not catch everything.
There are some runt filters that when activated can fillter out information   
that you may what to see.  My recommendation is read through the manual and
deactivate the runt filtering capabilities and take a closer look.  

As far as the HP4972 not being a very good protocol analyzer, you need to 
puchase the approprate software to run on the analyzer to get better results.
Contact HP for ordering information.

Mike,
HP