Monitoring VMware Tools

From OpenNMS

Detecting with Capsd

First configure $OPENNMS_HOME/etc/capsd-configuration.xml to detect the services on your Windows machines. The setup use the integrated Win32ServicePlugin:

 
  <!-- VMware Tools Windows und Unix -->
  <protocol-plugin protocol="MS-VMware-Physical-Disk-Helper"
    class-name="org.opennms.netmgt.capsd.plugins.Win32ServicePlugin"
    scan="on" user-defined="false">
      <property key="timeout" value="3000" />
      <property key="retry" value="1" />
      <property key="service-name" value="VMware Physical Disk Helper Service" />
  </protocol-plugin>
  <protocol-plugin protocol="MS-VMware-Tools"
    class-name="org.opennms.netmgt.capsd.plugins.Win32ServicePlugin"
    scan="on" user-defined="false">
      <property key="timeout" value="3000" />
      <property key="retry" value="1" />
      <property key="service-name" value="VMware Tools-Dienst" />
  </protocol-plugin>
  <protocol-plugin protocol="Proc-VMware-guestd"
    class-name="org.opennms.netmgt.capsd.plugins.HostResourceSwRunPlugin"
    scan="on" user-defined="false">
      <property key="timeout" value="2000" />
      <property key="retry" value="1" />
      <property key="service-name" value="vmware-guestd" />
  </protocol-plugin>
  <protocol-plugin protocol="Proc-VMware-vmmemctl"
    class-name="org.opennms.netmgt.capsd.plugins.HostResourceSwRunPlugin"
    scan="on" user-defined="false">
      <property key="timeout" value="2000" />
      <property key="retry" value="1" />
      <property key="service-name" value="vmmemctl" />
  </protocol-plugin>
  

Monitoring the services

 
  <!-- VMware Tools Windows Unix -->
  <service name="MS-VMware-Physical-Disk-Helper" interval="300000" user-defined="false" scan="on">
      <parameter key="timeout" value="4950" />
      <parameter key="retry" value="6" />
      <parameter key="service-name" value="VMware Physical Disk Helper Service" />
  </service>
  <service name="MS-VMware-Tools" interval="300000" user-defined="false" scan="on">
      <parameter key="timeout" value="4950" />
      <parameter key="retry" value="6" />
      <parameter key="service-name" value="VMware Tools-Dienst" />
  </service>
  <service name="Proc-VMware-guestd" interval="300000" user-defined="false" status="on">
      <parameter key="retry" value="6"/>
      <parameter key="timeout" value="4950"/>
      <parameter key="service-name" value="vmware-guestd"/>
  </service>
  <service name="Proc-VMware-vmmemctl" interval="300000" user-defined="false" status="on">
      <parameter key="retry" value="6"/>
      <parameter key="timeout" value="4950"/>
      <parameter key="service-name" value="vmmemctl"/>
  </service>

  <!-- VMware Tools Windows Unix -->
  <monitor service="MS-VMware-Physical-Disk-Helper" class-name="org.opennms.netmgt.poller.monitors.Win32ServiceMonitor" />
  <monitor service="MS-VMware-Tools" class-name="org.opennms.netmgt.poller.monitors.Win32ServiceMonitor" />
  <monitor service="Proc-VMware-guestd" class-name="org.opennms.netmgt.poller.monitors.HostResourceSwRunMonitor"/>
  <monitor service="Proc-VMware-vmmemctl" class-name="org.opennms.netmgt.poller.monitors.HostResourceSwRunMonitor"/>
  

Change your timeouts and retry settings to your needs, I have some heavy load machines and on with higher timeouts and more retries I have a lot less 30 second outages.

Personal tools
DevJam 2008 Sponsors
DevJam 2008 Sponsor: Google
DevJam 2008 Sponsor: Netregistry
DevJam 2008 Sponsor: Papa John's
NewEdge Networks
OpenNMS takes home the gold award!
Join the Free Software Foundation
Support This Project Commercial OpenNMS Support OpenNMS Italia Get OpenNMS at SourceForge.net. Fast, secure and Free Open Source software downloads Our Network Simulator Our Java Profiler