I have a wireless LAN controller. I want to monitor connected APs. I have the OIDs and I could probably just enter all of them manually, but is there an easier way, maybe like auto discovery plugin?
For example, I have 11 APs, after .19.n.n.n.n.n.n
[root@montest libexec]# snmpwalk -v2c -c public wlc 1.3.6.1.4.1.14179.2.2.1.1.19
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.16.5.202.244.24.80 = IpAddress: 133.40.148.211
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.80.135.137.162.96.112 = IpAddress: 133.40.148.217
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.136.240.49.195.135.112 = IpAddress: 133.40.148.214
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.136.240.49.198.87.240 = IpAddress: 133.40.148.213
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.136.240.49.198.91.160 = IpAddress: 133.40.148.215
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.136.240.49.230.194.96 = IpAddress: 133.40.148.218
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.136.240.49.234.5.16 = IpAddress: 133.40.148.220
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.136.240.49.234.8.64 = IpAddress: 133.40.148.212
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.136.240.49.234.13.48 = IpAddress: 133.40.148.219
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.136.240.49.239.212.208 = IpAddress: 133.40.148.210
SNMPv2-SMI::enterprises.14179.2.2.1.1.19.244.15.27.64.187.128 = IpAddress: 133.40.148.216
Plugin auto discovery?
Plugin auto discovery?
Last edited by sartecat on Tue Jul 25, 2017 4:26 pm, edited 1 time in total.
Re: Plugin auto discovery?
Check this plugin out:
https://github.com/jpajicek/puppet/blob ... _cisco_wlc
In it's current form it should allow you to check the numeric count of connected APs as well as whether or not a particular AP OperStatus is associated (based on its name). So if you know the list of names of APs you would expect to be "associated", you could set them up as service checks under a common host object.
Not exactly what you're looking for, but might be a good starting point if you wanted to script something out.
https://github.com/jpajicek/puppet/blob ... _cisco_wlc
In it's current form it should allow you to check the numeric count of connected APs as well as whether or not a particular AP OperStatus is associated (based on its name). So if you know the list of names of APs you would expect to be "associated", you could set them up as service checks under a common host object.
Not exactly what you're looking for, but might be a good starting point if you wanted to script something out.
Former Nagios employee
https://www.mcapra.com/
https://www.mcapra.com/
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Plugin auto discovery?
In case it's not clear, @Derick Wasswa asked because this is built in to XI. Currently, this is not built in to Core. Feel free to add a feature request to https://github.com/NagiosEnterprises/na ... issues/new
Re: Plugin auto discovery?
Just Nagios CoreDerick Wasswa wrote:Are you using Nagios XI?
Re: Plugin auto discovery?
I'm doing this for an internship that ends next month, and was just wondering if there is a plugin available out there that could do this. Thank you!
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Plugin auto discovery?
They will all require some work, but you could take a look at https://exchange.nagios.org//directory/ ... DDiscovery and see if you like any of them. If you're able to do some coding, they are at least a starting spot.