Years ago ('98 time frame), I demoed a device from the local Fluke 
offices.  This device would plug into your network anywhere, and map the 
network nodes, and monitor the traffic going to/from them.  (Of course, 
this was before switches were reasonably priced, so we were using hubs.) 
  A nice report telling you what protocols were in use, the percentage 
of the traffic load, etc.  As well as telling you the distance to the 
break in your line.

The next model up could supposedly do the same, but from a remote 
location.  But these weren't cheap then ($5k - $25K), and probably 
aren't now.  However you might be able to demo a device to see if it 
meets your needs.

Failing some magic device, grunt level troubleshooting has always been 
the best tool for me.  Isolating nodes, proving they are or are not the 
cause of the problem, etc.  Maybe traffic sniffing ala 
tcpdump/wireshark/(insert your favorite sniffer) might help.  But that's 
a time consuming process, so I tend to try to find my bugs before I get 
there.. :)

HTH

Shawn

Martin Glazer wrote:
> Hi,
> 
> I'm experiencing some network issues and I'm trying to track them down 
> -  have run tcpdump and been checking logs, but to no avail. I suspect 
> that there could be something now physically wrong with the network. The 
> issues are intermittent.
> 
> Does anyone know how I can go about testing the lower levels - what 
> equipment do I need, can I rent it, is there a company in Calgary that 
> does this?
> 
> I know this is not directly related to Linux, we are running on a Linux 
> network.
> 
> Thanks
> 
> Martin
> 
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to