Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

Remember Me

Directory Tree

check_ovm3

Current Version
0.2
Last Release Date
2013-02-01
Compatible With
  • Nagios 3.x
Owner
License
GPL
Hits
54388
Files:
FileDescription
check_ovm3check_ovm3
Nagios CSP

Meet The New Nagios Core Services Platform

Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.

Monitoring Made Magically Better

  • Nagios Core on Overdrive
  • Powerful Monitoring Dashboards
  • Time-Saving Configuration Wizards
  • Open Source Powered Monitoring On Steroids
  • And So Much More!
I stopped the development of this Plugin in 2015 due to move from Nagios to Check_MK.


This Nagios plugin was created to check OracleVM state.

What could be checked?
Currently there are 3 Checks implemented:

- filesystem
Checks used space in the filesystem and returns a Warning or Critical

- server
Checks the state of the server. Result is CRITICAL when server is not in 'Running'-Mode
WARNING when Server is in Maintenance-Mode

- vm
Checks the state of the virtual machine. Result is CRITICAL when VM is not in 'Running'-Mode
There is some statistical data for the virtual machine like RAM and CPUs.
The data in '()' are the allowd maximum values while running the vm.
This Nagios plugin was created to check OracleVM state.

What could be checked?
Currently there are 3 Checks implemented:

- filesystem
Checks used space in the filesystem and returns a Warning or Critical
Example:
check_ovm3 -p secret -a filesystem -n fs_Samsung_750GB -w 51 -c 75 -H localhost
OK - Filesystem Used Space 40% in fs_Samsung_750GB warn(51) crit(75) |pctused=40; Total=698; Used=281

- server
Checks the state of the server. Result is CRITICAL when server is not in 'Running'-Mode
WARNING when Server is in Maintenance-Mode
Example:
check_ovm3 -p secret -a server -n ovm3server -H localhost
OK - ovm3server is Running ovs-release 3.2.1-494 Processors 3 OVM-Server-IP 192.168.100.200 Maintenance Mode=Off Memory=16.0 emory Dom0=0.82 CPU-Type=AMD Phenom(tm) II X3 705e Processor CPU-Speed=2.494557

- vm
Checks the state of the virtual machine. Result is CRITICAL when VM is not in 'Running'-Mode
There is some statistical data for the virtual machine like RAM and CPUs.
The data in '()' are the allowd maximum values while running the vm.
Example:
check_ovm3 -p secret -a vm -n rac1 -H localhost
OK - rac1 is Running on ovm3server Repository=Samsung_750GB HA-Mode=No CPUs 3(3) RAM 1500(3000) OS=Oracle Linux 6 Dom-Type=Xen PVM


Requirements:
- OracleVM 3.1.1 or newer
This plugin only works with OVM3.1.1 or newer. Older versions doesn't have the
new SSHCLI
Some Details are missing when running under Version 3.1.1.

- expect
this plugin needs expect on the machine where the plugin is started
http://expect.sourceforge.net/
The executable for expect must be at /usr/bin/expect
- expect for OracleLunux5
wget http://mirror.centos.org/centos/5/os/x86_64/CentOS/expect-5.43.0-8.el5.x86_64.rpm
yum install -y --nogpgcheck expect-5.43.0-8.el5.x86_64.rpm

- SSH-Connection to OVM-Manager on Port 10000
The informations are gathered with the new OVMCLI. The connection is done
over Port 10000 (Default Port from OVM-Manager for SSHCLI)

- Password for admin is required
The connection is done with password to the SSHCLI. There is a stupid restriction
in OVM-Manager that makes public key authentication in monitoring impossible.
The password is visible when executing the script on the process list!

- ssh-hostkeys are not stored
this is needed because some NRPE-Servers are unable to write the known_hosts
=> Connections are imposibble. :-(

Reviews (3)
bytirano, January 24, 2019
Can you please advise?

./check_ovm: line 457: [: =: unary operator expected
bybanditbbs, October 6, 2014
Great little plugin. I needed more option(checking repository) and the code was written very well so I could easily hack at it and add the additional check!
We are just switching to OVM 3 so your timing couldn't be more perfect. When testing it out, I noticed that it won't properly read filesystems if the name has spaces in it. I've tried wrapping it in quotes to no avail. I'm trying to modify it to accept the UUID of the filesystem instead, at least until my bash is good enough to get around what I'm guessing is a variable substitution issue.