[Nagiosplug-help] Can't locate Net/SNMP.pm in @INC SOLVED!!!!

Jim Avery jim at jimavery.me.uk
Wed Sep 29 10:21:01 CEST 2010

On 28 September 2010 20:08, Leandro Roggerone
<leandro_roggerone at dmcwireless.com> wrote:
>  Hi everyone, I solve my problem running nagios pearl based plugins:
> I installed the plugins using the install.sh script and the worked ok ,
> I would like to get some info about the following plugins:
> check_bgp
> check_env
> check_snmp_process
> check_snmp_int
> I have been looking for info in manubulon.com and other nagios related
> sites but not succed,
> I can not configure correctly those plugins but I know they are working
> al least.
> It would be great to have some configuration examples to try,

define command{
        command_name    check_snmp_int
        command_line    $USER1$/check_snmp_int.pl -H $HOSTADDRESS$ $ARG1$
define service{
  use                   generic-service
  host_name             an-ethernet-switch01
  service_description   Unit02-Port02
  check_command         check_snmp_int!-C $USER4$ -2 -n "ACME Switch
- Unit 2 Port 2  " -fY -kqB -g -w 600000,600000,100,100,100000,10 -c
800000,800000,200,200,200000,20 -d 300
  notes                 Just one interface on a switch.

Note the "-2" option.   That's important so you get the 64-bit counters.

To find the name of the interfaces on the switch (or host), do something like:

/usr/local/nagios/libexec/check_snmp_int.pl -H an-ethernet-switch01 -C
community -n any -v

And beware, I've found on some switch types there are always two
spaces at the end of the interface description (see example above).

Note that $USER4$ refers to a variable in your resources.cfg file
which contains the community string.

The plugin must run at regular intervals (set normal_interval and
retry_check_interval to the same number) and will only return valid
output from the 2nd invocation onwards.  Beware permissions on the
temporary files which it creates.

This next one is easy by comparison:

define command {
  command_name  check_snmp_process
  command_line  $USER1$/check_snmp_process.pl -H $HOSTADDRESS$ $ARG1$

define service{
  use                   generic-service
  host_name             localhost
  service_description   process-snmptt
  check_command         check_snmp_process!-C $USER4$ -n snmptt -w 1 -c 0
  notes                 Alerts if the snmptt process is stopped.  The
snmptt process receives incoming traps and forwards them to the Nagios
trap handler.

I haven't tried check_env or check_bgp myself.



More information about the Help mailing list