Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Check Ruckus ZoneDirector - Number of APs
Current Version
0.1
Last Release Date
2012-09-29
Compatible With
- Nagios 1.x
- Nagios 2.x
- Nagios 3.x
- Nagios XI
- Nagios Fusion
Owner
License
GPL
Hits
58205
Files:
| File | Description |
|---|---|
| check_snmp_ruckuszd_numberofaps.pl | Version 0.1 - September 29 2012 |
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Check for Ruckus ZoneDirector to monitor the number of AP's associated with the ZoneDirector based on SNMP. By specifying the warning and critical thresholds an alarm will be raised if the number associated with the ZoneDirector is lower.
Example
./check_snmp_ruckuszd_numberofaps.pl -H 192.168.0.2 -C public -w 90 -c 80
Number of associated Access Points: 95 : OK
Example
./check_snmp_ruckuszd_numberofaps.pl -H 192.168.0.2 -C public -w 90 -c 80
Number of associated Access Points: 95 : OK
Reviews (2)
byaditigupta128, March 17, 2014
Hi the script is very good.
this script gives the total number of APs.
I want to know the uptime, no of conections by each AP and active/disconecetd state.
I have respective OID s with me.
Can someone pls help me to get the required info.
this script gives the total number of APs.
I want to know the uptime, no of conections by each AP and active/disconecetd state.
I have respective OID s with me.
Can someone pls help me to get the required info.
Thanks for this plugin!
A few things:
1) It does not appear to work with ePN.
2) The logic near line 400 to determine warning and critical uses >= when I think it should just be >
If you put the exact number of expected APs in the critical check, it still alarms with >=.
Other than that, it works great. Thanks!
A few things:
1) It does not appear to work with ePN.
2) The logic near line 400 to determine warning and critical uses >= when I think it should just be >
If you put the exact number of expected APs in the critical check, it still alarms with >=.
Other than that, it works great. Thanks!
