Hello, When i use the command check_snmp_int.pl i get the output as expected and the perfdata
but now i get "0;1000000000" in the perfdata values which i did not ask for. and appear to be Minimum and maximum values in my nagios graphs.
the graph now goes from 0 to 1Gb/s scale. it's too big that i can't even see the values (bandwidth in/out)
$USER1$/check_snmp_int.pl -H x.x.x.x -C community -2 -n eth -f -k -w 0,0 -c 0,0 -B -Y -M
eth0:UP (0.8Mbps/2.8Mbps), eth2:DOWN, eth1:UP (2.8Mbps/0.8Mbps): 1 int NOK : CRITICAL | 'eth0_in_Mbps'=1;;;0;1000000000 'eth0_out_Mbps'=3;;;0;1000000000 'eth1_in_Mbps'=3;;;0;100000000 'eth1_out_Mbps'=1;;;0;100000000
Do someone know a fix ?
Could not find an option in check_snmp_int.pl to get rid of those MIN/MAX values
thanks.
check_snmp_int create MIN/MAX perfdata values in Bits Mode
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_snmp_int create MIN/MAX perfdata values in Bits Mo
This is part of this plugin, it automatically checks the interface speed it is checking to create the min/maxNorshok wrote:Hello, When i use the command check_snmp_int.pl i get the output as expected and the perfdata
but now i get "0;1000000000" in the perfdata values which i did not ask for. and appear to be Minimum and maximum values in my nagios graphs.
the graph now goes from 0 to 1Gb/s scale. it's too big that i can't even see the values (bandwidth in/out)
$USER1$/check_snmp_int.pl -H x.x.x.x -C community -2 -n eth -f -k -w 0,0 -c 0,0 -B -Y -M
eth0:UP (0.8Mbps/2.8Mbps), eth2:DOWN, eth1:UP (2.8Mbps/0.8Mbps): 1 int NOK : CRITICAL | 'eth0_in_Mbps'=1;;;0;1000000000 'eth0_out_Mbps'=3;;;0;1000000000 'eth1_in_Mbps'=3;;;0;100000000 'eth1_out_Mbps'=1;;;0;100000000
Do someone know a fix ?
Could not find an option in check_snmp_int.pl to get rid of those MIN/MAX values
thanks.
Re: check_snmp_int create MIN/MAX perfdata values in Bits Mo
That's right
i checked the OIDs to find out that those values are generated by the device itself :
i guess the solution would be to edit the check_snmp_int.pl Perl script
In order to disable the ckecking of those OIDs.
i checked the OIDs to find out that those values are generated by the device itself :
Code: Select all
iso.3.6.1.2.1.2.2.1.5.2 = Gauge32: 1000000000
iso.3.6.1.2.1.2.2.1.5.3 = Gauge32: 100000000
In order to disable the ckecking of those OIDs.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_snmp_int create MIN/MAX perfdata values in Bits Mo
CorrectNorshok wrote:That's right
i checked the OIDs to find out that those values are generated by the device itself :
i guess the solution would be to edit the check_snmp_int.pl Perl scriptCode: Select all
iso.3.6.1.2.1.2.2.1.5.2 = Gauge32: 1000000000 iso.3.6.1.2.1.2.2.1.5.3 = Gauge32: 100000000
In order to disable the ckecking of those OIDs.