Monitor APs from a Wireless Controller

hallo,

do your APs not have individual IPs and support SNMP so that you can monitor them individual?

Hello, I'm interested in such a counter, too. Analysing the MIB-tree, there seems to be no counter-value for the number of access-points currently registered at the controller, but an entry for each with an increasing index. Is is possible to have an (snmp)-sensor to count the number of entries ? Listing looks like and the number of registered APs is 8 :

2025: mib-2.47.1.1.1.1.2.1 (octet string) Cisco Wireless Controller [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.43.6F.6E.74.72.6F.6C.6C.65.72 (hex) Size = 25]
2026: mib-2.47.1.1.1.1.2.2 (octet string) Cisco Wireless Access Point [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.41.63.63.65.73.73.20.50.6F.69.6E.74 (hex) Size = 27]
2027: mib-2.47.1.1.1.1.2.3 (octet string) Cisco Wireless Access Point [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.41.63.63.65.73.73.20.50.6F.69.6E.74 (hex) Size = 27]
2028: mib-2.47.1.1.1.1.2.4 (octet string) Cisco Wireless Access Point [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.41.63.63.65.73.73.20.50.6F.69.6E.74 (hex) Size = 27]
2029: mib-2.47.1.1.1.1.2.5 (octet string) Cisco Wireless Access Point [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.41.63.63.65.73.73.20.50.6F.69.6E.74 (hex) Size = 27]
2030: mib-2.47.1.1.1.1.2.6 (octet string) Cisco Wireless Access Point [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.41.63.63.65.73.73.20.50.6F.69.6E.74 (hex) Size = 27]
2031: mib-2.47.1.1.1.1.2.7 (octet string) Cisco Wireless Access Point [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.41.63.63.65.73.73.20.50.6F.69.6E.74 (hex) Size = 27]
2032: mib-2.47.1.1.1.1.2.8 (octet string) Cisco Wireless Access Point [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.41.63.63.65.73.73.20.50.6F.69.6E.74 (hex) Size = 27]
2033: mib-2.47.1.1.1.1.2.9 (octet string) Cisco Wireless Access Point [43.69.73.63.6F.20.57.69.72.65.6C.65.73.73.20.41.63.63.65.73.73.20.50.6F.69.6E.74 (hex) Size = 27]

Any help would be appreciated Franz Leippert

Aurelio,

We have a similar requirement to monitor number of APs registered with wireless controllers.

However, for large installations it is not feasible to configure a sensor to monitor registration of each AP individually. For example if you have 40 APs registered with a controller, you need to create 40 sensors, one for each AP, rather than 1 sensor to poll the Wireless Controller to get the number of registered AP's.

Also, in most networks, APs are configured for DHCP so it's not possible to configure sensors for each AP based on their IP address as it may change.

Can you advsie please what is the simplest and easiest way to monitor the number of AP's registered to a controller.

I'm afraid that if the APs do not have a DNS name and are flipping through IPs via DHCP, it is not possible to individually discern the same and, as such, the direct monitoring via PRTG is not possible.

Hi @all,

it is now possible to get the Accesspoint information over SNMP requests. Just download the "MIBS_8.1" file from cisco.com ( Cisco Path Downloads Home Products Wireless Wireless LAN Controller Standalone Controllers 5500 Series Wireless Controllers 5508 Wireless Controller Management Information Base (MIB)-8.1

After that, extract all *.my files and convert the "ENTITY-MIB.my" with the "PRTG MIB File Converter". After that import the *.oidlib to your PRTG Server. Now you can add the Sensor "SNMP Libary" and use your generated *.oidlib file.

If you just want to get the count of APs from a Cisco WLC 5508, create a snmpcustomsensor with OID Value = 1.3.6.1.4.1.9.9.618.1.8.4.0 Trigger 'change' notification, to get an error in case one AP disacotiates from the WLC.

For counting the connetcted clients the OID value is: 1.3.6.1.4.1.9.9.618.1.8.12.0

Hi Levix,

that is pretty cool and works fine in the latest release.

Doese anyone have other good OIDs for monitoring the Cisco WLC? I will add them to the Table. I think that is a good idea if we need to install a new version of PRTG.

OID Summary for PRTG

I was already using the aforementioned 2 OIDs for AP count and connected clients. But just for fun, I tried the ENTITY-MIB route. Upon attempting to create that SNMP Library sensor, PRTG begins setup and goes on, and on, and on... It eventually freezes up the entire main probe and a reboot is required to get it going again. OOPS :)

would it be posible to discover the associated APs through WLC ? Like from a server to do a snmp querry to the WLC that returns the names of associated APs ?