Trying to monitor number of connected clients

I'm trying to monitor our Aerohive APs using SolarWinds NPM, specifically the number of connected clients. Natively SolarWinds doesn't get this info from the APs. The vendor said Aerohive has OIDs I can put into SolarWinds to get this data. Does anyone have this?

Adam,
I see you found the ah_interface_mib.txt file. Click on it and scroll down about a fifth of the way to see the definition of ahAssociationTable, which is comprised of multiple AhAssociationEntry.

Adam,
It's been ages and ages since I last played with the Solarwinds tools. I *think* they offer a method for you to inport your own enterprise-specific MIBs into their database, but I don't recall how or how successful it is. I do vaguely recall they use a proprietary format instead of old-school MOSY compatible files.

Normally for importing our MIBs into an SNMP management tool I would only suggest the SMI file and the MIB file(s) of interest, but in this case I suggest you download all of the MIB files we supply and send them as a single bundle to your Solarwinds support contacts. Hopefully they will be able to compile them into a bundle they could send back to you for easy import.

I'll just send the entire text file to them and hopefully they can pull out what they need, I'm not a MIB expert by any means. Thanks for your help, I'll post back with results and and/or if I have issues.

Well this is SolarWinds' reply. Kind of starting to give me the runaround...

"Adding the Aerohive MIBs into our MIB database will not change the way NPM poll for the active wireless clients. Even if we include those MIBs into NPM MIB database, NPM will still poll for OID 1.3.6.1.4.1.9.9.273.1.1.2.1.1 (cDot11ActiveWirelessClients) to get the active wireless clients (for generic wireless information). Aerohive is using a different OID to poll for active wireless clients (it is not using the OID 1.3.6.1.4.1.9.9.273.1.1.2.1.1 as this was not found when we ran SNMP Walk against the Aerohive), this is the reason why we offer to create custom poller for that OID and poll for the active wireless clients.

We can have that Aerohive MIBs added in NPM database, but then again, it will not change the way NPM poll for the active wireless clients. By default (from this KB http://knowledgebase.solarwinds.com/k...), Orion NPM 10.3 and above polls the wireless-related OIDs for Aruba, Cisco, HP, Meru, and Orinoco wireless controllers and access points."

Urk. My apologies that you are in this situation, Adam. Let me try to break it down for you.

From my recollection, OID 1.3.6.1.4.1 is the root of the vendor-specific extensions. Anything that starts with that pattern is not an industry-standard MIB, it is unique to a specific vendor. Specifically, 1.3.6.1.4.1.9.9.273.1.1.2.1.1 belongs to Cisco.

It sounds to me as if they are telling you that they hard-coded support for Cisco in the past, and recently added Aruba, HP, Meru, and Orinoco vendor-specific MIBs but not ours.

The last sentence in their first paragraph is the key one - they offered to create a custom poller that queries the Aerohive vendor-specific MIB. Obviously the big question is how much they want to do this for you, and whether it will roll into future general releases of their product.

This won't help you right now, but I will talk to my own business development people and see if we can do anything from our end to get our MIBs supported by Solarwinds out-of-the-box, including comparable polling and reporting as they offer for competing wireless access points and controllers.

Yeah I mean they basically said they don't support Aerohive and they will create a custom poller (which won't show up on a 'connected clients' report which defeats the purpose.) They also submitted a feature request to app dev to add Aerohive as a supported vendor, but obviously they can't even promise support or that app dev will even consider it. Kind of stuck.

Yes, I think so. We have a built-in report for Max Concurrent Clients. On my HMOL 6.1r2 instance it's under Reports, Additional Reports. You can run it one time, or schedule it to re-run periodically. You have some control over the report period, from the last day to the last 2 months.

I suggest the first thing you do is clone the predefined report and save the clone, then you can edit the time period, reoccurance, etc. Or, if you only will care about the last day's data then the built-in report with our defaults may be all you need.

I am new to this conversation but thanks to Mike, I think I can be of some assistance. I am member of our BD technical team and handle partner relationships such as an Aerohive/SolarWinds relationship. I will give them a call and see where it takes us.

Sorry this is so painful. I hope this will help.

My email is bhubbert@aerohive.com, please email the contacts you have made there and I will take it from there.

Actually, just found a Hivemanager report, under Reports -> Additional Reports -> Wi-Fi Devices. Clone the "unique-client-count..." report, make sure "Old report version" is checked, and run it against a single AP or a set of APs, from a day to two months. Though by default the data is not saved that far back.

If you go in "List Resources" under Management of AP330, you could see two options Aerohive HiveAP by SolarWinds, and Wireless Access Point by SolarWinds at Wireless Access Point checkbox. It should be in Aerohive option and once you submit that, click on rediscover and will change to Aerohive WAPs.

Thanks for sharing Patience. I was concerned that we were the only ones seeing this problem. I have a ticket with Solarwinds on this, so if they provide a solution I will be sure to share. If I had to guess, this is an Aerohive issue and not a Solarwinds.

????? What makes you think that? All AP330's running the same version of code will respond to the same OIDs.

If your management platform displays certain options for one managed-element (an AP330) but different options for an identical managed-element running the same software, I would tend to focus my attention on the management platform itself, not the managed elements.

I did a test with OID 1.3.6.1.4.1.26928.1.1.1.2.1.2.1.3 within Solarwinds by creating a universal device poller. I selected multiple Aerohive access points and hit Test on it. Some of the access points came back with "This OID is not supported". I then did an snmp walk on an access point that returned info from my poller and .on an access point that did not return info. I did a search for OID 1.3.6.1.4.1.26928.1.1.1.2.1.2.1.3 on both of these access points, and for the one that did not return results, this OID is not present on it.

All of our access points are running the same version of code and are the same model.