This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Aruba Controller - How it works

menz over 14 years ago

Now that the Wireless functionality is in 9.5 we're going to use it for our Aruba wireless monitoring.

How do you get the ap's etc into NPM? Do you just put the controllers in and everthing else gets put

in?

Does anyone have any screenshots of it working as the Demo isn't working?

thanks

sam

0 bshopp over 14 years ago

Yes, you need to put the controller in and we will poll that to get the connected thin AP's and clients. Are you not seeing this? What other questions do you have?
Cancel
Vote Up 0 Vote Down

Cancel
0 bechtj over 14 years ago in reply to bshopp

I added SNMP to my Aruba Controller's(4 of them) and Solarwinds 9.5 does see all the Controllers. However, it see's only maybe HALF the AP's that are on those Controllers in the Wireless Section and is reporting back incorrect data as to how many users are on those Ap's. Also, when I try to add a AP as a Node to be monitored through Solarwinds, I cannot use SNMP 1, 2, or 3 to see it. It just times out. Any ideas?
Cancel
Vote Up 0 Vote Down

Cancel

0 bshopp over 14 years ago in reply to bechtj

So first, please make sure you are on the latest Service Pack for 9.5.

So the thin AP's are not SNMP managable, you can only monitor up/down status if you want to add them to Orion via ICMP. We gather all the thin AP stats and client details directly from the controller.

You might want to walk these OID's to see what the device responds back with, this is what we poll to get the Thin AP's and clients associated.

Aruba Controller

OID = ModelName	1.3.6.1.4.1.14823.2.2.1.2.1.3
OID = IPAddress	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.5
OID = HostName	1.3.6.1.4.1.14823.2.2.1.2.1.2
OID = Clients	1.3.6.1.4.1.14823.2.2.1.5.2.1.7.1.12
OID = TotalBytesTx	1.3.6.1.4.1.14823.2.2.1.1.3.5.1.9
OID = TotalBytesRx	1.3.6.1.4.1.14823.2.2.1.1.3.5.1.11
OID = Client_Name	1.3.6.1.4.1.14823.2.2.1.1.2.2.1.3
OID = Client_Role	1.3.6.1.4.1.14823.2.2.1.1.2.2.1.4
OID = Client_TotalBytesTx	1.3.6.1.4.1.14823.2.2.1.1.2.3.1.2
OID = Client_TotalBytesRx	1.3.6.1.4.1.14823.2.2.1.1.2.3.1.4
OID = Client_TxRate	1.3.6.1.4.1.14823.2.2.1.1.2.2.1.8
OID = Client_RxRate	1.3.6.1.4.1.14823.2.2.1.1.2.2.1.9
OID = RadioType	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.6
OID = Type	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.7
OID = TotalTime	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.10
OID = TxRate	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.15
OID = RxRate	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.16
OID = InactiveTime	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.11
OID = SNR	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.14
OID = Noise	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.13
OID = Client_AssociationID	1.3.6.1.4.1.14823.2.2.1.1.2.2.1.5
OID = Client_ESSID	1.3.6.1.4.1.14823.2.2.1.1.2.2.1.6
OID = Client_SNR	1.3.6.1.4.1.14823.2.2.1.1.2.2.1.7
OID = Client_TotalPacketsTx	1.3.6.1.4.1.14823.2.2.1.1.2.3.1.1
OID = Client_TotalPacketsRx	1.3.6.1.4.1.14823.2.2.1.1.2.3.1.3
OID = TotalPacketsTx	1.3.6.1.4.1.14823.2.2.1.1.3.5.1.8
OID = TotalPacketsRx	1.3.6.1.4.1.14823.2.2.1.1.3.5.1.10
OID = Role	1.3.6.1.4.1.14823.2.2.1.1.1.4
OID = Client_IPAddress	1.3.6.1.4.1.14823.2.2.1.4.1.2.1.9
OID = Rogue_CurrentChannel	1.3.6.1.4.1.14823.2.2.1.6.7.1.1.1.2
OID = Rogue_Classification	1.3.6.1.4.1.14823.2.2.1.6.7.1.1.1.3
OID = Rogue_SSID	1.3.6.1.4.1.14823.2.2.1.6.7.1.1.1.4
OID = Rogue_PhyType	1.3.6.1.4.1.14823.2.2.1.6.7.1.1.1.1
OID = CurrentChannel	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.8
OID = SSID	1.3.6.1.4.1.14823.2.2.1.1.3.3.1.2
OID = Rogue_SignalStrength	1.3.6.1.4.1.14823.2.2.1.6.7.1.1.1.5
OID = Rogue_Status	1.3.6.1.4.1.14823.2.2.1.6.7.1.1.1.10

0 bechtj over 14 years ago in reply to bshopp

I have Service Pack 4 installed already. According to the Aruba Controller and Aruba Guide, I can enable SNMP on the AP's and they can be monitored using SNMP version 2 or 3. Also, all the thin Ap's are using the same Config, so I enable the SNMP on the Config, but still can't monitor them.
Cancel
Vote Up 0 Vote Down

Cancel
0 bshopp over 14 years ago in reply to bechtj

So when you try to validate the SNMP string what happens in Orion? I would recommend opening a support ticket with us to look into
Cancel
Vote Up 0 Vote Down

Cancel
0 RichardLetts over 9 years ago in reply to bshopp

Is there a way to turn off pulling the aruba client stats (globally)?
I know some people make use of this, but it's a lot of data, and I think it's causing some of the polling problems we're seeing.
Cancel
Vote Up 0 Vote Down

Cancel
0 ice over 9 years ago in reply to RichardLetts

I do think there is Richard Letts
Orion polls in bulk information via SNMP. You may try the Manage Pollers on Orion web and see if your Aruba shows up on the pollers there.
Cancel
Vote Up 0 Vote Down

Cancel
0 RichardLetts over 9 years ago in reply to ice

No, there only appears to be one poller associated with the wireless information: N.WirelessController.SNMP.Aruba
this includes too much information: controller, thinAP, rogue, and client polling all in one package
Idea to modularize this: https://thwack.solarwinds.com/ideas/4946
anyone know if there are internal switches I can use to control the poller?
Cancel
Vote Up 0 Vote Down

Cancel
0 ice over 9 years ago in reply to RichardLetts

That OID are embedded on the MIB database and the core polls it to that database to request the SNMP information, I believe it can't. The way that I see it is either all or nothing (to poll SNMP). If you think this information still is not correct, you may open a support ticket and check if that will be possible.
Cancel
Vote Up 0 Vote Down

Cancel