Tag Info

Hot answers tagged

2

-w=-85: -c=-80: is the syntax I needed, but check_snmp still converts the output to positive when an error is triggered. Bug report filed.


1

Comments are for humans - by definition they pretty much need to be inserted into the file by hand by (more knowledgeable) humans. If you need to have comments in your files I suggest a template file (with comments and $variable blocks to substitute in appropriate values for things that might change, like subnets and community strings) -- When you make a ...


1

Strange that it isn't passing all the arguments for you. Old version of nagios-plugins, perhaps? Fortunately you can probably re-use something I just put together that solves a different problem. check_snmp doesn't obey your smnp.conf file. I wrote a check_snmp.pl script that behaves similarly to check_snmp, and works with snmp v3, and uses the values in ...


1

as "work around" (even though it really not), one can use -c or -w instead of -r, as -r seems to have some sort of bug. # ./check_snmp --help | grep -E 'critical|warning' -w, --warning=THRESHOLD(s) -c, --critical=THRESHOLD(s) # example: # /usr/lib/nagios/plugins/check_snmp --hostname=X.X.X.X --community=X --protocol=X --oid=ifOperStatus.6 -c1 SNMP ...


1

It's the value of the SNMP variable that you are querying. So, you might set a warning on CPU load above a certain percentage, or disk space below the same. For other variables, it might be some sort of enumerated type. What exactly it is in your case, you'ld have to look at the command definition to see what OID you are querying. When you've found out, ...



Only top voted, non community-wiki answers of a minimum length are eligible