<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000099" bgcolor="#ffffff"> Thanks much for the info. Curious... you mention ESX and VSphere. Do you know if your check_vmware test also works against VMWare Server 2.x (free edition). We are running ESX internally, but have a single external server running VMWare Server 2.x with three VMs in it. Hence why I ask...<br> <pre class="moz-signature" cols="72"> A. Davis Email: <a class="moz-txt-link-abbreviated" href="mailto:nccomp@gmail.com">nccomp@gmail.com</a> "There is no limit to what a man can accomplish if he doesn't care who gets the credit." - Ronald Reagan </pre> <br> On 1/26/10 3:03 AM, Steve Shipway wrote: <blockquote cite="mid:6B587E8C999646469B54486AF21958460CE66C8670@UXCHANGE7-1.UoA.auckland.ac.nz" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta name="GENERATOR" content="MSHTML 8.00.6001.18876"> <style title="owaParaStyle"></style> <div dir="ltr"><font face="Tahoma" size="2" color="#000000">This is the way we do it, with Parents (not host dependencies).</font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">First we create a virtual object for the VMWare farm. This has a status of UP if any of the farm servers are up (using check_summary). This virtual 'host' has several services, using the v0.9 check_vmware, relating to the farm's alarms, storage volumes, etc. These services have service dependencies on the VirtualCentre service running on the Virtual Centre host.</font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">The Farm object has ALL of the ESX Servers as Parents.</font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">All the VMs in the farm have the Farm object as a parent. Some of them also use check_esx3 to alert on Alarms, CPU, and Memory usage within VMWare.</font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">This might seem a bit complex if you've only the one server, but as soon as oyu have multiple servers in the farm, and use DRS, you have to use a farm object for parents/dependencies.</font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">It might make more sense for these relationships to be host dependencies rather than parents i nmost cases, but we have a SAN mirrored environment to a seocnd ESX farm so that the VMs can be brought up ther ein the event of a complete farm outage, hence the use of Parents rather than dependencies.</font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">If you have VSphere4 (ESX4.0) with a SNMP-enabled Cisco virtual switch in the farm, you could probably make the virtual switch the parent device rather than having to use a farm object.</font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">The VMWare monitoring plugin we're using is v0.9 of check_vmware, from here: <a moz-do-not-send="true" href="http://www.steveshipway.org/forum/viewtopic.php?f=28&t=1648">http://www.steveshipway.org/forum/viewtopic.php?f=28&t=1648</a></font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">check_summary is available from nagiosexchange.org (as is check_esx3 which is the forerunner of check_vmware)</font></div> <div dir="ltr"> </div> <div dir="ltr"><font face="tahoma" size="2">Steve</font></div> <div dir="ltr"> </div> <div style="direction: ltr;" id="divRpF855849"> <hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b> Andrew Davis [<a class="moz-txt-link-abbreviated" href="mailto:nccomp@gmail.com">nccomp@gmail.com</a>]<br> <b>Sent:</b> Tuesday, 26 January 2010 9:14 a.m.<br> <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net</a><br> <b>Subject:</b> [Nagios-users] Virtual Machines - define as parent or as host dependency...<br> </font><br> </div> <div>I'm trying to figure out the best way to do this, yet keep things as simple as possible.<br> <br> Say I have a server called Saturn running VMWare. I'm monitoring this server with Nagios.<br> I also have three VM's on Saturn: Jupiter, Mars, and Pluto<br> <br> I want to suppress all host and service alerts on Jupiter, Mars, & Pluto if the host Saturn is down (unreachable). I do NOT want to suppress host or service alerts from Jupiter, Mars, and Pluto if the VMWare processes (services) are down on Saturn. Basically, if my VM server is completely unreachable, don't bother me about its client VM's.<br> <br> Am I better off doing this with a host dependency? Something like:<br> <br> <pre><strong><font color="red">define hostdependency { host_name Host B dependent_host_name Host C notification_failure_criteria d,u } </font></strong></pre> Or am I better off defining Saturn as the parent of the VM's in the host config? Something like:<br> <br> <pre><b><font color="#ff0000">define host { host_name jupiter use VMs alias jupiter address 172.26.251.60 parents saturn, tpdmzsw1 }</font></b></pre> I've successfully used the "parents" directive to define network topology, so I would think this would work. What might be the risks of defining both?<br> <pre class="moz-signature" cols="72">-- A. Davis Email: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:nccomp@gmail.com">nccomp@gmail.com</a> "There is no limit to what a man can accomplish if he doesn't care who gets the credit." - Ronald Reagan </pre> </div> </blockquote> </body> </html>