Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
Directory Tree
Check various hardware environmental sensors
0.7
2011-02-21
- Nagios 2.x
- Nagios 3.x
GPL
166177
File | Description |
---|---|
check_snmp_environment.pl | Version 0.7 - February 21 2011 |
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!
Notes
Although some of the checks in this plugin are also in the "check_snmp_env" (version 1.3) from Patrick Proy I strongly suggest using this version as some of the checks in "check_snmp_env" aren't efficient or don't give alarms.
Supports SNMPv1, SNMPv2c(default), SNMPv3 and IPv6. Multiple Cisco checks might function on a single Cisco device! Also support for Cisco ASR platforms.
Supported Checks
Please send me an e-mail with requests, bugs or patches. Leave a reply below if you like the plugin :)
Michiel Timmers
Although some of the checks in this plugin are also in the "check_snmp_env" (version 1.3) from Patrick Proy I strongly suggest using this version as some of the checks in "check_snmp_env" aren't efficient or don't give alarms.
Supports SNMPv1, SNMPv2c(default), SNMPv3 and IPv6. Multiple Cisco checks might function on a single Cisco device! Also support for Cisco ASR platforms.
Supported Checks
cisco _______ | Cisco Systems : Fan, power-supply, voltage, temperature |
ciscoSW ____ | Cisco Systems : Card and module status check |
ciscoNEW __ | Cisco Systems : Sensor check for devices that have the CISCO-ENTITY-SENSOR-MIB |
nokia ______ | Nokia IP : Fan, power-supply |
bc _________ | Blue Coat Systems : Fan, power-supply, voltage, disk |
iron _______ | IronPort : Fan, power-supply, temperature |
foundry ____ | Foundry Network : power supply, temperature |
linux _______ | lm-sensors : Fan, voltage, temperature, misc |
extremeSW _ | Extreme Networks : Slot, power-supply, fan, temperature |
juniper _____ | Juniper Networks : Component status check |
procurve ___ | HP ProCurve : Fan, power-supply, temperature |
netscreen ___ | NetScreen : Slot, fan, power-supply |
citrix _______ | Citrix NetScaler : Fan, , voltage, temperture, HA state, SSL engine |
transmode __ | Transmode Systems : Check alarm table that is not deactivated and not acknowledged |
Please send me an e-mail with requests, bugs or patches. Leave a reply below if you like the plugin :)
Michiel Timmers
Reviews (11)
byjtberge, September 4, 2014
I'm missing performance data and i tried checking a juniper SA2500 cluster on which it doesn't work.
On Cisco equipment it does work though and i give 3 stars for basically doing what it does, i would've given 4 if performance data was generated and 5 if more tresholds could be finetuned.
On Cisco equipment it does work though and i give 3 stars for basically doing what it does, i would've given 4 if performance data was generated and 5 if more tresholds could be finetuned.
Hi!
Good plugin.
I found a little bug. Here is a patch for fixing it:
--- ../check_snmp_environment.pl 2012-05-30 16:16:35.000000000 +0200
+++ ./check_snmp_environment.pl 2014-06-11 09:24:47.919573111 +0200
@@ -723,7 +723,7 @@
my $volt_global=0;
my %volt_status;
-if ($fanexist !=0) {
+if ($voltexist !=0) {
for ($i=0;$i
Good plugin.
I found a little bug. Here is a patch for fixing it:
--- ../check_snmp_environment.pl 2012-05-30 16:16:35.000000000 +0200
+++ ./check_snmp_environment.pl 2014-06-11 09:24:47.919573111 +0200
@@ -723,7 +723,7 @@
my $volt_global=0;
my %volt_status;
-if ($fanexist !=0) {
+if ($voltexist !=0) {
for ($i=0;$i
Excellent script, its huge.
Thanks a lot for sharing and taking your time to make this.
However can you explain to me how i am able to see what the exact temperature is?
Example:./check_snmp_environment -H pgpa0sw1 -C netstat -T cisco -c 10
3 Fan OK, 2 ps OK, 10 temp OK : OK
I only get ok's but would like to know the exact temperature.
Thanks a lot for sharing and taking your time to make this.
However can you explain to me how i am able to see what the exact temperature is?
Example:./check_snmp_environment -H pgpa0sw1 -C netstat -T cisco -c 10
3 Fan OK, 2 ps OK, 10 temp OK : OK
I only get ok's but would like to know the exact temperature.
bya_rudolf, January 28, 2014
I have added support for netscreen internal temperature sensors. Plaese find the patch in your email box.
Thanks a lot for your work!
Thanks a lot for your work!
bypashas, September 23, 2013
I wrote a small patch. Added state PSUs "PowerOff".
--- check_snmp_environment.pl.old 2013-09-20 09:26:47.000000000 +0300
+++ check_snmp_environment.pl 2013-09-20 08:35:49.000000000 +0300
@@ -272,8 +272,8 @@
my @extreme_slot_nagios = (3,0,2,2,2,0,2,3);
my $extreme_ps_table = "1.3.6.1.4.1.1916.1.1.1.27.1";
my $extreme_ps_status = "1.3.6.1.4.1.1916.1.1.1.27.1.2";
-my @extreme_ps_status_text = ("--Invalid--","notPresent","presentOK","presentNotOK");
-my @extreme_ps_nagios = (3,1,0,2);
+my @extreme_ps_status_text = ("--Invalid--","notPresent","presentOK","presentNotOK","presentPowerOff");
+my @extreme_ps_nagios = (3,1,0,2,1);
my $extreme_fan_table = "1.3.6.1.4.1.1916.1.1.1.9.1";
my $extreme_fan_number = "1.3.6.1.4.1.1916.1.1.1.9.1.1";
my $extreme_fan_operational = "1.3.6.1.4.1.1916.1.1.1.9.1.2";
--- check_snmp_environment.pl.old 2013-09-20 09:26:47.000000000 +0300
+++ check_snmp_environment.pl 2013-09-20 08:35:49.000000000 +0300
@@ -272,8 +272,8 @@
my @extreme_slot_nagios = (3,0,2,2,2,0,2,3);
my $extreme_ps_table = "1.3.6.1.4.1.1916.1.1.1.27.1";
my $extreme_ps_status = "1.3.6.1.4.1.1916.1.1.1.27.1.2";
-my @extreme_ps_status_text = ("--Invalid--","notPresent","presentOK","presentNotOK");
-my @extreme_ps_nagios = (3,1,0,2);
+my @extreme_ps_status_text = ("--Invalid--","notPresent","presentOK","presentNotOK","presentPowerOff");
+my @extreme_ps_nagios = (3,1,0,2,1);
my $extreme_fan_table = "1.3.6.1.4.1.1916.1.1.1.9.1";
my $extreme_fan_number = "1.3.6.1.4.1.1916.1.1.1.9.1.1";
my $extreme_fan_operational = "1.3.6.1.4.1.1916.1.1.1.9.1.2";
bybrianhonaker, October 25, 2012
I have loaded the check_snmp_environment plugin and I believe that I have loaded the correct MIB (CISCO-ENVMON-MIB). Currently I get the following error when I test the following service check
Check: check_snmp_env -H $HOSTADDRESS$ -T cisco -l netmanager -x N0GUe5$MD5HPS -X N0GUe5$DESHPS
Error: ERROR opening session: Received usmStatsWrongDigests.0 Report-PDU with value 36 during synchronization.
I'm using SNMP v3.
Check: check_snmp_env -H $HOSTADDRESS$ -T cisco -l netmanager -x N0GUe5$MD5HPS -X N0GUe5$DESHPS
Error: ERROR opening session: Received usmStatsWrongDigests.0 Report-PDU with value 36 during synchronization.
I'm using SNMP v3.
bypws, August 28, 2012
Thanks for sharing this plugin. We're using it to monitor a few dozen Cisco switches. It was very simple to deploy and has accurately identified problems.
bysukanta, October 30, 2011
Very Good!
byfatherosam, May 5, 2011
Very good and comprehensive, love this check.
We did however change the OID for the Extreme_ps_status to the next .1. as we have only 1 power supply connected in the switches it was returning an warning on the second supply.
Around line 273
#my $extreme_ps_status = "1.3.6.1.4.1.1916.1.1.1.27.1.2";
# only want PS one. DA 6/5/2011
my $extreme_ps_status = "1.3.6.1.4.1.1916.1.1.1.27.1.2.1";
I'm sure someone can do a more elegant solution however this works for us ATM.
We did however change the OID for the Extreme_ps_status to the next .1. as we have only 1 power supply connected in the switches it was returning an warning on the second supply.
Around line 273
#my $extreme_ps_status = "1.3.6.1.4.1.1916.1.1.1.27.1.2";
# only want PS one. DA 6/5/2011
my $extreme_ps_status = "1.3.6.1.4.1.1916.1.1.1.27.1.2.1";
I'm sure someone can do a more elegant solution however this works for us ATM.
This plugin enable us to start monitoring the various components of our Juniper devices mostly Juniper MX960.
Setting up the plugin in Nagios Version 3.2.3 is straight forward the only problem i faced was plugin works fine from command line but giving error 'Service check did not exit properly', quick googling reports its something to do with embedded perl. simple fix it to prefixes the command_line with full path to the perl. The command definition look like...
define command{
command_name check_snmp_components
command_line /usr/bin/perl $USER1$/check_snmp_environment.pl -H $HOSTADDRESS$ .....
}
Setting up the plugin in Nagios Version 3.2.3 is straight forward the only problem i faced was plugin works fine from command line but giving error 'Service check did not exit properly', quick googling reports its something to do with embedded perl. simple fix it to prefixes the command_line with full path to the perl. The command definition look like...
define command{
command_name check_snmp_components
command_line /usr/bin/perl $USER1$/check_snmp_environment.pl -H $HOSTADDRESS$ .....
}
Tested using Nagios 3.2.0 running on Ubuntu 10.04LTS checking various Cisco gear (6509, 2940, etc).