Nagios plug-in

LPAR2RRD
STOR2RRD

LPAR2RRD can be integrated with Nagios monitoring via standard nrpe plug-in.

How it works?
You have to configure LPAR2RRD alerting. Once LPAR2RRD issues an alarm then it is kept into separate directory which is being regularly checked via Nagios nrpe. When appears there a file with an alarm then it is picked up to Nagios and an alarm is raised in Nagios.
Nagios has to be configured to pick up alarms of particular servers and their pools or lpars. Each server and pool or lpar must have separated configuration in Nagios server to be able to distinguish between them and to be able to sort alarms and their related services in Nagios UI.

Installation

Configure standard LPAR2RRD alerting, here is description: alerting install
Enable Nagios support in lpar2rrd.cfg in etc/alert.cfg
```
NAGIOS=1
```
Install Nagios NRPE modul on LPAR2RRD servers. It must be compiled with option "--enable-command-args". Note this is not the default option!
You might download nrpe 2.13 from www.lpar2rrd.com AIX binnary compiled with this option
Change this in nrpe.cfg to allow argument passing:
```
dont_blame_nrpe=1
```

Let use LPAR2RRD script for picking up alerts via nrpe. Add to nrpe.cfg:

command[lpar2rrd]=/home/lpar2rrd/lpar2rrd/bin/check_lpar2rrd $ARG1$ $ARG2$ $ARG3

Restart nrpe and test whether it works:
```
$ /opt/nagios/bin/check_nrpe -H localhost -c lpar2rrd  -a LPAR p710 nim
OK
```
No matter about 3 parameters at the end, place there whatever, it should return always "ok". When not then most probably nrpe does not have argument support enabled or is not compiled with that option.

Nagios server configuration example of 3 configured alerts:

# LPAR2RRD
define service {			# LPAR named nim on server p710
        use                             generic-service
        host_name                       lpar2rrd-host
        service_description             lpar2rrd-nim-CPU-LPAR
        check_command                   check_lpar2rrd!lpar2rrd!LPAR!p710!nim
}
define service {			# CPU pool named demo on server p710
        use                             generic-service
        host_name                       lpar2rrd-host
        service_description             lpar2rrd-demo-CPU-POOL
        check_command                   check_lpar2rrd!lpar2rrd!POOL!p710!demo
}
define service {			# CPU pool on server p710 
        use                             generic-service
        host_name                       lpar2rrd-host
        service_description             lpar2rrd-nim-pool-CPU
        check_command                   check_lpar2rrd!lpar2rrd!POOL!p710!all_pools
}


define command{
        command_name    check_lpar2rrd
        command_line    /opt/nagios/bin/check_nrpe -H $HOSTADDRESS$ -c lpar2rrd -a $ARG2$ $ARG3$ $ARG4$
}

Note that naturally same alerts must be defined in LPAR2RRD alerting (alert.cfg)

Restart Nagios server

You can even find the same module on Nagios Exchange

STOR2RRD can be integrated with Nagios monitoring via standard nrpe plug-in.

How it works?
You have to configure STOR2RRD alerting. Once STOR2RRD issues an alarm then it is kept into separate directory which is being regularly checked via Nagios nrpe. When appears there a file with an alarm then it is picked up to Nagios and an alarm is raised in Nagios.
Nagios has to be configured to pick up alarms of particular storage and ther volumes. Each storage and volume must have separated configuration in Nagios server to be able to distinguish between them and to be abe to sort alarms and their related services in Nagios UI.

Installation

Configure standard STOR2RRD alerting, here is description: aleting install
Enable Nagios support in the alerting UI (options -> nagios alerting = 1)
Install Nagios NRPE modul on STOR2RRD server. It must be compiled with option "--enable-command-args". Note this is not the default option!
You might download nrpe 2.13 from www.stor2rrd.com AIX binnary compiled with this option
Change this in nrpe.cfg to allow argument passing:
```
dont_blame_nrpe=1
```

Let use STOR2RRD script for picking up alerts via nrpe. Add to nrpe.cfg:

command[stor2rrd]=/home/stor2rrd/stor2rrd/bin/check_stor2rrd $ARG1$ $ARG2$ $ARG3

Restart nrpe and test whether it works:
```
$ /opt/nagios/bin/check_nrpe -H localhost -c stor2rrd  -a storage01 volume_name01 io
OK
```
No matter about 3 parameters at the end, place there whatever, it should returns always "ok". When not then most probably nrpe does not have argument support enabled or is not compiled with that option.

Nagios server configuration example of 3 configured alerts:

# STOR2RRD
define service {			# Volume named volume_name01 on storage storage01 for IO rate 
        use                             generic-service
        host_name                       stor2rrd-host
        service_description             stor2rrd-storage01-volume_name01-io
        check_command                   check_stor2rrd!stor2rrd!storage01!volume_name01!io
}

define command{
        command_name    check_stor2rrd
        command_line    /opt/nagios/bin/check_nrpe -H $HOSTADDRESS$ -c stor2rrd -a $ARG2$ $ARG3$ $ARG4$
}

Note that same alerts must be defined in STOR2RRD alerting

Restart Nagios server

You can even find the same module on Nagios Exchange