Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
Directory Tree
F5 BIG-IP Nagios plugins
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-F5-Failover.pl Check-F5-PoolMbrs.pl Check-F5-VirtualAddresses.pl F5-BIGIP-COMMON-MIB F5-BIGIP-SYSTEM-MIB
Check-F5-Platform.pl Check-F5-Pools.pl Check-F5-VirtualServers.pl F5-BIGIP-LOCAL-MIB
[root@localhost F5-Nagios-Plugins]# ./Check-F5-Pools.pl
ERROR: Community not defined.
Can you please help and advise the next steps?
CPU-1 39?C, CPU-2 38?C, FAN-1 ok, FAN-2 ok, FAN-3 ok, POWER-SUPPLY-1 ok, POWER-SUPPLY-2 ok, Chassis-Temperature-1 28?C, Chassis-Temperature-2 32?C, Chassis-Temperature-3 33?C, Chassis-Temperature-4 30?C
On 3.5.0 it's cut off after "CPU-1 39". I removed those special chars from the script and Nagios now displays the output properly.
I agree with you bostonsean. It is an annoying charset encoding bug. As far as I know "Degree Symbol" for temperatures or "Masculine Ordinal Indicator" character codification may depend on your locales, encoding charset and/or keyboard layout for your system language and/or browser URL encodings. A nightmare indeed. Notice that Nagios only shows first line from plugin output. Removing the problematic char is a straightforward workaround, but I'm afraid I submitted my local codification for that char from my machine text editor, so that in your system it gets coded in some buggy way making it to not show correctly on your Nagios console. I suggest to edit the perl script and replace the "ยบ" char (Degree Symbol) with the proper codification supported by your servers and test the new modified script from both Nagios installations.
Let me know if that works! Thanks in advanced.
There seems to be no way to check for a specific pool member - just all of them, same for virtual servers.
There's no thresholds for critical or warning.
However the code does what it sets out to do it seems.
For the sake of simplicity we decided to consider CRITICAL any object UNAVAILABLE when ENABLED to urge admins to disable it or recover it as soon as posible. How can we define WARNING for a variable pool member count ranging from ONE to N members? With percentage UNAVAILABILITY for the members count? Too much arguments and mesh around.