Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Check LPAR Physical CPU Usage
Current Version
0.2
Last Release Date
2015-04-03
Compatible With
- Nagios 3.x
Owner
License
GPL
Hits
33528
Files:
| File | Description |
|---|---|
| check_lpar_physc_cpu.sh | check_lpar_physc_cpu.sh |
Plugin shows physical processor usage on your certain LPAR AIX server.
You have to define your warning and critical thresholds by your own. The most important thing is that you can have chart about usage if you integrate into some Nagios add-on like pnp4nagios and you can later on balance usage between your LPARs on IBM Power machine.
Usage: ./check_lpar_physc_cpu.sh -w warning -c critical
Plugin needs NRPE to be executed remotely. If you decide to define plugin to be executed with arguments over NRPE you have to enable arguments in nrpe.cfg.
nrpe.cfg:
command[check_lpar_physc_cpu]=/usr/local/nagios/libexec/check_lpar_physc_cpu.sh -w $ARG1$ -c $ARG2$
You have to define your warning and critical thresholds by your own. The most important thing is that you can have chart about usage if you integrate into some Nagios add-on like pnp4nagios and you can later on balance usage between your LPARs on IBM Power machine.
Usage: ./check_lpar_physc_cpu.sh -w warning -c critical
Plugin needs NRPE to be executed remotely. If you decide to define plugin to be executed with arguments over NRPE you have to enable arguments in nrpe.cfg.
nrpe.cfg:
command[check_lpar_physc_cpu]=/usr/local/nagios/libexec/check_lpar_physc_cpu.sh -w $ARG1$ -c $ARG2$
Reviews (1)
Has some issues.
One, "requires" a utils.sh script that is not provided (it actually doesn't and can be commented out)
Two, uses shell based test operators that only work on integers and then attempts to evaluate floating point numbers, so behavior will probably not be as you expect. (If you set a critical threshold of "2" it will not show critical until numbers go above 3, for instance.)
One, "requires" a utils.sh script that is not provided (it actually doesn't and can be commented out)
Two, uses shell based test operators that only work on integers and then attempts to evaluate floating point numbers, so behavior will probably not be as you expect. (If you set a critical threshold of "2" it will not show critical until numbers go above 3, for instance.)
Owner's reply
Thanks a lot. I've made correction according to your input. It would be helpful for me if you can test it again.
Reg.B.
