Re: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-04 Thread Scott Reed
: Re: [WISPA] Tracking Signal / Noise / Resends / Etc. I could be mis-remembering this, or confusing things (say, a tower where we replaced a 5800 with a 5830 or vice-versa), and if I'm wrong I'll cop to it. But I truly believe, with religious fervor and zeal, that Trango has

Re: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread rcomroe
There are 2 fundamentally different approaches for monitoring. [1] Poll parameters and strip-chart them displaying some specific duration of history. In this approach data rolls off the end of the strip-chart and is not retained. Only numerical data can be displayed graphically is

RE: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread Paul Hendry
For StarOS we use MRTG and Starutil. You should be able to graph anything that Starutil can provide. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Scrivner Sent: 03 November 2005 17:33 To: wireless@wispa.org Subject: [WISPA] Tracking Signal / Noise

Re: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread Nigel Bruin
At the risk of derailing (sorry, boss), has anyone gotten MRTG or something similar (PRTG, Denika, or whatever) to reliably track *anything* on a Trango? Sure. TrangoLINK-10 integrated with Nagios and MRTG. However, I had to write a wrapper perl script around the Nagios RSSI check_command

RE: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread Paul Hendry
] On Behalf Of David E. Smith Sent: 03 November 2005 20:10 To: WISPA General List Subject: Re: [WISPA] Tracking Signal / Noise / Resends / Etc. rcomroe wrote: There are 2 fundamentally different approaches for monitoring. [ stuff ] For reference, in the network Scriv is describing, there's a nasty

RE: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread Todd Barber
] On Behalf Of David E. Smith Sent: Thursday, November 03, 2005 1:10 PM To: WISPA General List Subject: Re: [WISPA] Tracking Signal / Noise / Resends / Etc. rcomroe wrote: There are 2 fundamentally different approaches for monitoring. [ stuff ] For reference, in the network Scriv is describing

RE: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread Todd Barber
Subject: Re: [WISPA] Tracking Signal / Noise / Resends / Etc. Thank you Paul. This is exactly what I was looking for in regard o customer links. If we take a service call it would be nice to see what a customer's historical data has been in regard to signal levels, bandwidth used, etc. It sounds

Re: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread David E. Smith
rcomroe wrote: Under no circumstances should any manufacturer CHANGE THE DEFINITION OF A PREVIOUSLY DEFINED OID. and yet... Trango's MIBs for the 5800 and 5830 are wildly different. Never mind that they're substantially the same hardware (from the point of view of how you use them in your

Re: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread rcomroe
5:13 PM Subject: Re: [WISPA] Tracking Signal / Noise / Resends / Etc. rcomroe wrote: Under no circumstances should any manufacturer CHANGE THE DEFINITION OF A PREVIOUSLY DEFINED OID. and yet... Trango's MIBs for the 5800 and 5830 are wildly different. Never mind that they're substantially

Re: [WISPA] Tracking Signal / Noise / Resends / Etc.

2005-11-03 Thread David E. Smith
rcomroe wrote: On another part of David's reply he comments on interface.InOctets. And don't even get me started on the fact that they don't use the same Enterprise MIBs that pretty much everyone else on the planet uses for 'interface.InOctets' and so on. The interfaces MIB is a standard part