Hi,

when I run auto-discovery with template on Cisco WLC device (steps described here: How can I monitor a Cisco WLC deployment with PRTG? ), no sensors are discovered. Autodiscovery log (C:\ProgramData\Paessler\PRTG Network Monitor\Logs\debug\):

2019-01-14 09:22:59.710402 INFO TId 2892 CoreAutoDiscovery> Autodiscovery Started; Device ID: 8939 2019-01-14 09:22:59.710402 INFO TId 2892 CoreAutoDiscovery> Device ID: 8939 Name: X.X.X.X Host: X.X.X.X 2019-01-14 09:22:59.710402 INFO TId 2892 CoreAutoDiscovery> Device Templates; Device ID: 8939; Selected: 2 2019-01-14 09:22:59.804153 INFO TId 2892 CoreAutoDiscovery> Template Loaded; Device ID: 8939; Name: Custom Cisco WLC SSID Statistics v0.2 2019-01-14 09:23:00.054153 INFO TId 2892 CoreAutoDiscovery> Template Check; Device ID: 8939; Check ID: ping; FOUND 2019-01-14 09:23:16.054371 INFO TId 2892 CoreAutoDiscovery> Template Check; Device ID: 8939; Check ID: snmp; ERROR: 106ErrorMessage: No Metaresult found 2019-01-14 09:23:16.069997 INFO TId 2892 CoreAutoDiscovery> Template Loaded; Device ID: 8939; Name: Custom Cisco WLC Access Point Status v0.2 2019-01-14 09:23:17.054386 INFO TId 2892 CoreAutoDiscovery> Autodiscovery Finished: Device ID: 8939; Sensor(s): 0; Templates:

I have tried with Cisco WLC model 2504 and model 1830, in both cases I get the same error message. Both WLCs are reachable via ping and have correct SNMP community name. Standard auto-discovery (not with template) discovers following sensors:

Ping SSL Certificate Sensor SSL Security Check HTTPS

Can you please help? :)

Thank you! Lorena

Article Comments

Never configured this cause we have a PRIME appliance that does that way more detailed then any monitoring system ever would be able too, but of what you write - did you ever download the SNMP MIB / OID files and make them available to PRTG?

The link talks about those: SNMP must be enabled and the device must support the AIRESPACE-WIRELESS-MIB and CISCO-LWAPP-SYS-MIB.

I don't see those files by default in my PRTG - might be just me though - but I think you would need to get them from Cisco first.. ?

After asking Google - I found both here: ftp://ftp.cisco.com/pub/mibs/supportlists/wlc/wlc-supportlist.html

Regards

Florian Rossmark

www.it-admins.com


Jan, 2019 - Permalink

Hello Lorena,

Check also the post you've referenced, last section "SNMP Data". There it is explained how to create a scan script to use with SNMP tester to manually check if the device delivers the data or responds to SNMP at all. Most likely something's not right with the SNMP settings, meaning the device does not respond, so the discovery will not create sensors for it.

Kind regards,

Erhard


Jan, 2019 - Permalink

Thank you Florian and Erhard!

@Florian

I already saved AIRESPACE-WIRELESS-MIB and CISCO-LWAPP-SYS-MIB to

C:\Program Files (x86)\PRTG Network Monitor\MIB

if this is what you meant by "making them available to PRTG"? Sorry I'm a rookie with PRTG :)

@Erhard

You are right - when I run this script, I get 2003 error. I really can't find the cause of this problem, but I will look into it. All my other Cisco devices work fine, and also Fortinet devices with imported MIBs.


Jan, 2019 - Permalink

At this point you want to use the SNMP tester - select the MIB/OID files and execute it directly from the PRTG probe you are using - so you test with the same IP towards the target device.

This needs to work - otherwise you would have an issue with the configuration of SNMP - at least as of now it looks like that.

Keep us posted - pretty sure we get it fixed :-)

Florian


Jan, 2019 - Permalink

I finally found the cause of this problem!

Access mode on SNMP community on my Cisco WLC was Read Only. When I changed it to Read-Write, it still did not work, but then I created new SNMP community with Read-Write access mode and now it works! :)

I can see Controller statistics (number of connected APs and clients), SSID statistics (admin status, broadcast enabled/disabled, connected stations) and associated Access Points with their hostnames and serial numbers.

Thank you for your help! :)

Best,

Lorena


Jan, 2019 - Permalink

Hello Lorena,

Good to hear you got it working. Usually "Read" access should suffice as PRTG only pulls data and does not try to write data into the device by SNMP, but hey, it's working now :)

Kind regards,

Erhard


Jan, 2019 - Permalink