At 10:48 AM 4/8/2010, you wrote:
To all
What would you want the probe to monitor? I have not read the MIBs
yet mainly because I have not found any documentation on what each
MIB does so far (granted, I haven't spent much time on it yet).
I personally like to see the number of associations per AP,
bandwidth, and the signal levels of each client, as well as uptimes
(for the AP), etc..
As for the MIBs, Aruba doesn't change TOO much, but a few versions
ago, they did some major changing, taking alot of things out that I
have get another way. I got sick of always looking at the MIBs to
see if things were still there, so I just walk the whole device, feed
it to a text file, and manually look at it and just reverse engineer
it. More fun that way =) Especially using the numeric only OIDs.
Our probe looks in the database as well as just poking a little at
the controller, thus the vitals, and alarms and such still work
fine. We also alert on things found in the tables as well,
overcrowded APs and such. Probing the controller itself for vitals
should report number of APs up/down (at least its in the WebGUI)
When we were evaluating Meru, the probe I wrote just SSH'd into the
controller and grabbed info from "show station". But I never
bothered to integrate into IM, just into my custom monitoring system.
If a probe for Meru appeared, I'm sure someone could mangle it enough
to convert for Aruba if someone wanted. I have not seen anyone
talking about Aruba on here, but I imagine theres others out there..?
I could also go back to the basics, and write up a more simple Aruba
probe, and toss that out there so you at least have a starting
point. But I hate IM's probe language so much that I write my probes
in C or PHP, then use a commandline type probe to run my
scripts. The main problem with this is it cannot update the display
name, so have to rely on DNS for that, plus no "ants". (Feature
requests for these are about 3 years old and counting). Then theres
always the two different probes for the same device option.. ugh..
- - - Jon
(past email reference below)
I'm think of starting off with just basic host resource monitoring,
but I hope that there is an OID that reports number of APs down. I'd
basically look for how the system is doing overall, bandwidth
utilization and if there are any APs down, but only if there is an
OID that has that info. I'm thinking, polling a table would be
useless, since I can't alert on anything in that table.
Any other ideas of what would be interesting to look for without
have 2-4 sec response times?
--------------
Andrey Khomyakov | Senior Network Engineer | +1.617.879.5945
Confidentiality Note: This e-mail, and any attachment to it, is
intended to be confidential and might be legally privileged. It is
intended solely for the use of the addressee. If you are not the
intended recipient, you are hereby notified that reading, copying,
disseminating or distributing this email is strictly prohibited. If
you have received this e-mail in error, please immediately return it
to the sender and delete it from your system. Thank you.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Jon Myers
Sent: Thursday, April 08, 2010 10:31 AM
To: InterMapper Discussion
Subject: Re: [IM-Talk] Meru Wireless Probe? (and Aruba)
We do a similar thing for Aruba, it was getting a little slow poking
the controller for each AP separately. So instead, we do an snmp
walk for a few interesting OIDs every minute to get the details for
everything, and stick them in the database. Then the probe just
looks in the database for the information, and cross references with
our (home-grown) NAC system, and updates the details in the probe to
show connections, usernames, locations, SNR, radio type, etc..
We're relatively small, only 300 APs (well, small compared to
Debbie's > 2000 APs anyway). But still, poking at the controller to
get all the stats I wanted for each AP, with a 1 minute poll interval
seemed to have a long (~2-4 seconds) response time sometimes.
Now that IM has a database you can sort of get to, it might be a bit
easier to integrate the probe. I have not revisited my scripts to
see how to put them into a newer separate-database driven IM.
Just wanted to give some ideas on how it could be done.
- - - Jon Myers
(Top post to leave bottom part for reference only)
At 01:41 PM 4/7/2010, Debbie Fligor wrote:
>We do have Meru and we do monitor it. However, we found that the
>controllers were not very responsive to SNMP, and we wanted to
>summarize by building (we have > 2000 APs in ~ 230 buildings). so
>we run a script on a unix system that talks SNMP to the controller
>and generates a per-building summary (into a database these days,
>IIRC), that has about a 5 minute history built in (to deal with the
>SNMP failures). We also have a daemon listening on a socket that can
>query the database. A simple TCP probe on Intermapper gets
>up/down/warn status by asking for a specific building number and
>getting back the number of down APs and total APs for that building
>number. Since we name our access points wap-####-xx where #### is
>the building number (and xx is sequence number), this isn't too hard to do.
>
>If this complex type of monitoring is of interest, I'll see about
>sharing our scripts, we can usually do that.
>
>On Apr 7, 2010, at 10:44, <[email protected]> wrote:
>
> > Does anyone use InterMapper to poke Meru wireless controllers? I
> would not want to reinvent the wheel. If not, I'll start writing
> one (the probe :), not the wheel) and share it out.
> >
> > Andrey
> >
> >
> > --------------
> > Andrey Khomyakov | Senior Network Engineer | +1.617.879.5945
> >
> >
>
>-----
>-debbie
>Debbie Fligor, n9dn Network Engineer, CITES, Univ. of Il
>email: [email protected] <http://www.uiuc.edu/ph/www/fligor>
> "My turn." -River Tam
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [email protected]
