Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!uc!uh!tjs
From: tjs@uh.msc.umn.edu (Tim Salo)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Network Analyzers
Message-ID: <2213@uc.msc.umn.edu>
Date: 24 Jul 90 04:03:38 GMT
References: <23847@boulder.Colorado.EDU>
Sender: news@uc.msc.umn.edu
Reply-To: tjs@uh.UUCP (Tim Salo)
Organization: Minnesota Supercomputer Center, Minneapolis, MN
Lines: 24

In article <23847@boulder.Colorado.EDU> ron@ctios2.ctio.noao.edu (ron lambert x238) writes:
>We are looking for
>an analyzer that has the option to be able to monitor/troubleshoot on
>both sides of the Cisco, i.e. ethernet and T1.

Generally, an ethernet LAN anaylzer and a protocol analyzer for serial lines
are different boxes.  I haven't seen any combined boxes, at least not any which
did either job real well.  I recommend you spend a lot of money on a good
LAN analyzer, and spend as little as you can for a serial line protocol
analyzer.

You will use the LAN analyzer all the time, and sometimes for hard problems.
On the other hand, you probably won't use the protocol analyzer nearly as much.
Furthermore, you probably won't rely upon the protocol analyzer as often.  I
don't have a cisco manual in front of me, but there may be enough traces
in the cisco to obviate the need for a high-power protocol analyzer.  I do,
however, like to see what is happening on the line, at least to the extent
of seeing flags and perhaps watching the cisco's try to bring the line up.


Timothy J. Salo                    tjs@msc.umn.edu
Minnesota Supercomputer Center     (612) 626-0347
1200 Washington Avenue South       Secretary, MRNet
Minneapolis, MN 55415              (MN Regional Network)