Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
BigIP Pool and Virtual Server checks
Owner
Hits
115769
Files:
| File | Description |
|---|---|
| check_bigip_pool | check_bigip_pool v2.00 |
| check_bigip_vs | check_bigip_vs v2.00 |
| check_bigip_pool_201 | check_bigip_pool v2.01 |
| check_bigip_vs_202 | check_bigip_vs v2.02 |
These two Perl checks use Nagios::Plugins 0.15
----------------------------------------------------------------------
check_bigip_pool:
Check the number of available nodes in a BigIP Pool
Usage: check_bigip_pool -H hostname -C Community -S SW_Version -P Pool Name [ -w warning_percent ] [ -c critical_percent ]
Use -h for a full help message.
Take note of the special meaning of this plugin thresholds:
-w, --warning=
Will return a WARNING state when there is LESS THAN this percentage of alive nodes. Floats are accepted. The default is 90
-c, --critical=
Will return a CRITICAL state when there is LESS THAN this percentage of alive nodes. Floats are accepted. The default is 50
----------------------------------------------------------------------
check_bigip_vs
Usage: check_bigip_vs -H hostname -C Community -S SW_Version -I VS_Name/IP_Address [ -p VS_Port ]
Use -h for a full help message.
----------------------------------------------------------------------
Changelogs:
check_bigip_pool
v. 2.01
Don't compile the MIBs anymore (not required and cpu-intensive)
v. 2.00
Original version
check_bigip_vs
v. 2.02
LTM v.9.3 support both ways of getting VS status, I now use the newer method (like for LTM v.9.4)
Updated the output for all LTM 9.x versions so that it is less confusing
v. 2.01
Add support for v.9.4 LTM
Don't compile the MIBs anymore (not required and cpu-intensive)
v. 2.00
Original version
----------------------------------------------------------------------
check_bigip_pool:
Check the number of available nodes in a BigIP Pool
Usage: check_bigip_pool -H hostname -C Community -S SW_Version -P Pool Name [ -w warning_percent ] [ -c critical_percent ]
Use -h for a full help message.
Take note of the special meaning of this plugin thresholds:
-w, --warning=
Will return a WARNING state when there is LESS THAN this percentage of alive nodes. Floats are accepted. The default is 90
-c, --critical=
Will return a CRITICAL state when there is LESS THAN this percentage of alive nodes. Floats are accepted. The default is 50
----------------------------------------------------------------------
check_bigip_vs
Usage: check_bigip_vs -H hostname -C Community -S SW_Version -I VS_Name/IP_Address [ -p VS_Port ]
Use -h for a full help message.
----------------------------------------------------------------------
Changelogs:
check_bigip_pool
v. 2.01
Don't compile the MIBs anymore (not required and cpu-intensive)
v. 2.00
Original version
check_bigip_vs
v. 2.02
LTM v.9.3 support both ways of getting VS status, I now use the newer method (like for LTM v.9.4)
Updated the output for all LTM 9.x versions so that it is less confusing
v. 2.01
Add support for v.9.4 LTM
Don't compile the MIBs anymore (not required and cpu-intensive)
v. 2.00
Original version
Reviews (6)
byrsingh, October 28, 2015
The script is modified to work with version 12
https://github.com/tfaadmin/F5-V12/blob/master/check_bigip.pl
https://github.com/tfaadmin/F5-V12/blob/master/check_bigip.pl
by72mm, April 24, 2013
Needs just some minor updating to get it to work with BIG-IP v11.
Partitions must be included in order to work.
Not the cleanest way, but if you only use the default "common" partition, changes below:
Original:
$oidPoolName =~ s/(.)/sprintf('.%u', ord($1))/eg;
$oidPoolName = length($PoolName) . $oidPoolName;
Updated so it still supports older versions:
if ($software eq '4.5' || $software eq '9' || $software || '10') {
$oidPoolName =~ s/(.)/sprintf('.%u', ord($1))/eg;
$oidPoolName = length($PoolName) . $oidPoolName;
}
if ($software eq '11') {
$oidPoolName = "/Common/" . $PoolName;
my $v11PoolName = $oidPoolName;
$oidPoolName =~ s/(.)/sprintf('.%u', ord($1))/eg;
$oidPoolName = length($v11PoolName) . $oidPoolName;
print "v11 " . $oidPoolName . "\n";
}
Partitions must be included in order to work.
Not the cleanest way, but if you only use the default "common" partition, changes below:
Original:
$oidPoolName =~ s/(.)/sprintf('.%u', ord($1))/eg;
$oidPoolName = length($PoolName) . $oidPoolName;
Updated so it still supports older versions:
if ($software eq '4.5' || $software eq '9' || $software || '10') {
$oidPoolName =~ s/(.)/sprintf('.%u', ord($1))/eg;
$oidPoolName = length($PoolName) . $oidPoolName;
}
if ($software eq '11') {
$oidPoolName = "/Common/" . $PoolName;
my $v11PoolName = $oidPoolName;
$oidPoolName =~ s/(.)/sprintf('.%u', ord($1))/eg;
$oidPoolName = length($v11PoolName) . $oidPoolName;
print "v11 " . $oidPoolName . "\n";
}
bygcaracuel, February 20, 2013
I have made minor changes to this great scripts to support our F5's with 10.x software version installed.
I've shared it in github: https://github.com/gcaracuel/check_f5_vs-pool
Cheers!
I've shared it in github: https://github.com/gcaracuel/check_f5_vs-pool
Cheers!
byamprantino, October 31, 2012
check_bigip_pool is 0 bytes (corrupted).
Any alternative links?
Any alternative links?
byinfinitiguy, July 16, 2012
Hi,
We used to use this check to monitor pool status when we were on 9.x. We upgraded to 11.0 and these checks no longer work. I was wondering if there's any plans to update to support 11.x? I'm trying to fix the current plugin to work - so if I manange to get it I can submit it for review - otherwise if it's something that's being worked on that'd be great news to hear.
We used to use this check to monitor pool status when we were on 9.x. We upgraded to 11.0 and these checks no longer work. I was wondering if there's any plans to update to support 11.x? I'm trying to fix the current plugin to work - so if I manange to get it I can submit it for review - otherwise if it's something that's being worked on that'd be great news to hear.
bybillrydernz, February 6, 2012
I tried the other 4 and this is by far the most useful. You can set critical and warning thresholds for the named pool, name virtual server etc.
At this point (without exhaustively testing it) I would suggest that the ' Could not interpret information from the BigIP' should be an UNKNOWN not a CRITICAL.
At this point (without exhaustively testing it) I would suggest that the ' Could not interpret information from the BigIP' should be an UNKNOWN not a CRITICAL.
