The wireless monitoring in NPM collects a significant amount of data. for example:
Aruba Wireless Controllers
| Polled Information | OID Name | OID Value |
| Discovery | wlsxSysExtModelName | 1.3.6.1.4.1.14823.2.2.1.2.1.3 |
| Controller | Model | 1.3.6.1.4.1.14823.2.2.1.2.1.3 |
| Thin AP | IPAddressNameStatus | 1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.21.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.31.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.19 |
| Thin AP Interface Link | ClientsCount | 1.3.6.1.4.1.14823.2.2.1.5.2.1.7.1.12 |
| Thin AP Interface | SSIDCurrentChannelRadioType | 1.3.6.1.4.1.14823.2.2.1.1.3.3.1.21.3.6.1.4.1.14823.2.2.1.1.3.3.1.81.3.6.1.4.1.14823.2.2.1.1.3.3.1.6 |
| Rogue | SSIDCurrentChannel | 1.3.6.1.4.1.14823.2.2.1.6.7.1.1.1.41.3.6.1.4.1.14823.2.2.1.6.7.1.1.1.2 |
| Client | InDataRateOutDataRateInTotalBytesOutTotalBytesInTotalPacketsOutTotalPackets | 1.3.6.1.4.1.14823.2.2.1.1.2.2.1.91.3.6.1.4.1.14823.2.2.1.1.2.2.1.81.3.6.1.4.1.14823.2.2.1.1.2.3.1.41.3.6.1.4.1.14823.2.2.1.1.2.3.1.21.3.6.1.4.1.14823.2.2.1.1.2.3.1.31.3.6.1.4.1.14823.2.2.1.1.2.3.1.1 |
| Client Name | Name | 1.3.6.1.4.1.14823.2.2.1.4.1.2.1.3 |
| Client Signal Strength | SignalStrength | 1.3.6.1.4.1.14823.2.2.1.5.2.2.1.1.14 |
It can be seen from this that there is information about the thinAP, Rogues, and Clients
1/ the ThinAP information is useful.
2/ the Rogue information is not useful (just outside the campus proper most of the buildings are surrounded by business offering free WiFi; collecting rogue information is not useful.
3/ Students, on average have about 2.5 wireless devices each (staff have slightly fewer ~2.0) -- we peak at around 187,000; this is too much data to collect and I would like to turn it off.
I would like to be able to control which sections of data are collected from the controller -- right now a full poll takes well over 30 minutes; collecting the AP status information takes less than 20 seconds
Please modularize the AP polling and give us control over which sets of statistics are gathered.
