(RADIATOR) Monitoring Tools

[Bret Jordan]

Dave, et all,

The tools as a framework is being written to be very flexible, you can 
build groups and have hosts inside the group and then you can define 
values globally, at the group level, or at the host level (where group 
values override the global just for that group and any hosts below it 
and the host values override the global and group values just for that 
host).   You can even do an IdenticalClients directive like in Radiator :)

As Terry said, he submitted a patch that allows you to hook a shell 
script to get the data, so if your equipment does not support SNMP you 
can use a custom shell script and as long as the shell script returns a 
number, the program will take that in and process it.

We have in the documentation the OIDs for Cisco and Proxim AP2000s.  As 
soon as we can figure out the OIDs for the Foundry/HP APs we will add 
that as well to the documentation.  And if anyone knows of another OID 
from vendor X that will give you similar data, let me know and I will 
add it to the documentation.

The next tool, an environmental stats graphing tool, should be done today.

Bret

Terry Simons wrote:

> There is no standard SNMP OID to grab these statistics, so each AP is 
> going to have a different OID.
> 
> Additionally,  some devices do not support any OID that provides this 
> data, so the tools can be used with an external script that will fake 
> the data for you by gathering it via some other means and skipping the 
> SNMP portion of the scripts.
> 
> I have a script that gathers data for Trapeze equipment if anyone is 
> interested, I suppose that we should roll it back into Bret's work. ;-)
> 
> We also have the OID for Cisco 1200 series APs, which should get rolled 
> back into the documentation, if nothing else.  (So, Cisco 1200, AP 2000, 
> Trapeze).  It should be trivial to add others.
> 
> Overall it works quite well thanks Bret.  Three Cheers. ;-)
> 
> - Terry
> 
> On Sep 27, 2004, at 9:26 AM, Dave Kitabjian wrote:
> 
>> Bret, this sounds and looks great.
>>
>> The question I have is, is there anything about this which is particular
>> to WAPs? In other words, wouldn't it (or couldn't it) work with any NAS?
>> Is the OID different?
>>
>> If it could, we'd use it :)
>>
>> Dave
>>
>>> -----Original Message-----
>>> From: Bret Jordan [mailto:bret.jordan at utah.edu]
>>> Sent: Thursday, September 23, 2004 1:11 PM
>>> To: radiator at open.com.au
>>> Subject: (RADIATOR) Monitoring Tools
>>>
>>> All,
>>>
>>> With Hugh's blessing I am making this announcement.
>>>
>>> I have written a tool (that I think will be in the goodies directory
>>> going forward) that will graph the current users associated to your
>>> wireless networks. The tool is called apsessiontracking and is in the
>>> geektools package. This tool will use SNMP to get the value of the
>>> current number of users associated to an AP and then graph that via
>>
>> RRD.
>>
>>> It also has the ability to hook a shell script to get the value if
>>> your AP does not have SNMP or the correct OID for current sessions.
>>>
>>> As I add functionality or tools to the package, I will send it up to
>>> Hugh for the goodies directory. But you will always be able to
>>
>> download
>>
>>> the latest version at http://utahgeeks.sourceforge.net
>>>
>>> Please send bugs and feature requests to me. I have attached a sample
>>> of what the daily graph could look like.
>>>
>>> Some of the tools I will be adding to the package in the next few
>>
>> weeks
>>
>>> are:
>>> 1) A client/server piece so that you can share "totals" with some one
>>> else. Example here at our University every organization runs their
>>
>> own
>>
>>> wireless network and we want to have a central "totals" graph by
>>> organization and we do not really care about sharing the details just
>>> the totals.
>>> 2) Tools for other devices that have environmental sensors like Temp.
>>> 3) One request I have had is to do a log watcher script for Radiator
>>
>> and
>>
>>> I might look into that if I have time.
>>>
>>> Bret
>>>
>>>
>>> -- 
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> Bret Jordan Dean's Office
>>> Director of Networking College of Engineering
>>> 801.585.3765 University of Utah
>>> jordan at coe.utah.edu
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bret Jordan                       Dean's Office
Director of Networking   College of Engineering
801.585.3765                 University of Utah
             jordan at coe.utah.edu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.