<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VI: VMware ESXi™ 3.5 : Monitoring ESXi with Python script : Comments</title>
    <link>http://communities.vmware.com/docs/DOC-7170#comments</link>
    <description>Comments on : Monitoring ESXi with Python script</description>
    <language>en</language>
    <pubDate>Sat, 10 Jan 2009 20:34:49 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-01-10T20:34:49Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-10404</link>
      <description>Works great, thanks! I just set it up on Fedora using the python-pywbem package linked here: &lt;a class="jive-link-external" href="https://bugzilla.redhat.com/245688"&gt;https://bugzilla.redhat.com/245688&lt;/a&gt; (should be in Fedora soon). My next step will be building python-pywbem on RHEL5 and trying it there.</description>
      <pubDate>Sat, 10 Jan 2009 20:34:49 GMT</pubDate>
      <author>joshuadf</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-10404</guid>
      <dc:date>2009-01-10T20:34:49Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-10510</link>
      <description>i love the script, i use it from windows with whatsup. I wrote a whatsup wrapper to use it.&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.stephenjc.com/2009/01/whatsup-vmware-esxi-monitor-these.html"&gt;http://www.stephenjc.com/2009/01/whatsup-vmware-esxi-monitor-these.html&lt;/a&gt;</description>
      <pubDate>Sun, 18 Jan 2009 19:53:47 GMT</pubDate>
      <author>stephen_c01</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-10510</guid>
      <dc:date>2009-01-18T19:53:47Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-10501</link>
      <description>your script works great from the command line, but i ran into problems when trying to define the check command for nagios. would you mind sharing how you got it to work?&lt;br /&gt;
&lt;br /&gt;
edit: i keep getting a (null) return &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/sad.gif" alt=":(" /&gt;&lt;br /&gt;
&lt;br /&gt;
Thanks</description>
      <pubDate>Wed, 21 Jan 2009 22:59:07 GMT</pubDate>
      <author>themali</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-10501</guid>
      <dc:date>2009-01-21T22:59:07Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-10634</link>
      <description>Awesome work! Works great from a linux box. I did receive this error from a windows box:&lt;br /&gt;
C:\Python26\lib\site-packages\pywbem\cim_types.py:164: DeprecationWarning: object.__init__() takes no parameters&lt;br /&gt;
  int.__init__(self, arg, base)&lt;br /&gt;
&lt;br /&gt;
However the command appears to have completed successfully regardless.</description>
      <pubDate>Mon, 02 Feb 2009 20:15:07 GMT</pubDate>
      <author>ipman</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-10634</guid>
      <dc:date>2009-02-02T20:15:07Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-10761</link>
      <description>Works in Zenoss too:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://linuxtrek1.blogspot.com/2009/02/zenoss-monitor-free-esxi-version.html"&gt;http://linuxtrek1.blogspot.com/2009/02/zenoss-monitor-free-esxi-version.html&lt;/a&gt;</description>
      <pubDate>Wed, 18 Feb 2009 08:00:53 GMT</pubDate>
      <author>moot</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-10761</guid>
      <dc:date>2009-02-18T08:00:53Z</dc:date>
      <clearspace:dateToText>1 year, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-10794</link>
      <description>It works great on Red Hat EL5 with the rpm above, or even on the ancient EL4 if you install the older pywbem-0.5 for python-2.3. &lt;br /&gt;
&lt;br /&gt;
I also made a small improvement (full script available at &lt;a class="jive-link-external" href="http://staff.washington.edu/joshuadf/esxi/"&gt;http://staff.washington.edu/joshuadf/esxi/&lt;/a&gt; ) to catch problems with EnumerateInstances. This catches AuthError for wrong password and should also work for the CIM_Memory problem described at &lt;a class="jive-link-external" href="http://communities.vmware.com/message/1069795"&gt;http://communities.vmware.com/message/1069795&lt;/a&gt; and &lt;a class="jive-link-external" href="http://communities.vmware.com/thread/163730"&gt;http://communities.vmware.com/thread/163730&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
+	try:&lt;br /&gt;
 	instance_list = wbemclient.EnumerateInstances(classe)&lt;br /&gt;
+	except pywbem.cim_operations.CIMError,args:&lt;br /&gt;
+		verboseoutput("Unknown CIM Error: %s" % args, verbose)&lt;br /&gt;
+	except pywbem.cim_http.AuthError,arg: &lt;br /&gt;
+		verboseoutput("GLobal exit set to CRITICAL", verbose)&lt;br /&gt;
+		GlobalStatus = ExitCritical&lt;br /&gt;
+		ExitMsg += "CRITICAL : AuthError: %s&lt;br&gt;" % arg&lt;br /&gt;
+	else:	&lt;br /&gt;
&lt;p /&gt;
By the way at least on my Dell PowerEdge 2950s you can also get these:&lt;br /&gt;
'OMC_Fan',&lt;br /&gt;
'OMC_PowerSupply',</description>
      <pubDate>Fri, 20 Feb 2009 00:50:12 GMT</pubDate>
      <author>joshuadf</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-10794</guid>
      <dc:date>2009-02-20T00:50:12Z</dc:date>
      <clearspace:dateToText>1 year, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-11550</link>
      <description>fix it!&lt;br /&gt;
Download the pywbem 0.7 (pywbem-0.7.0.tar.gz), open the file cim_types.py, copy the "# CIM integer types" section and replace it in your 0.6 "C:\Python26\Lib\site-packages\pywbem\cim_types.py"&lt;br /&gt;
The error doesn't come out anymore.&lt;br /&gt;
&lt;br /&gt;
=========================================================================&lt;br /&gt;
&lt;br /&gt;
Max</description>
      <pubDate>Wed, 17 Jun 2009 10:04:42 GMT</pubDate>
      <author>maxzam</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-11550</guid>
      <dc:date>2009-06-17T10:04:42Z</dc:date>
      <clearspace:dateToText>9 months, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-11653</link>
      <description>I'm having the same result via Nagios, (null), but from the command line I get OK, or in verbose mode see all of the checks.&lt;br /&gt;
&lt;br /&gt;
Here's how I have the command defined in commands.cfg:&lt;br /&gt;
&lt;br /&gt;
define command{&lt;br /&gt;
        command_name    check_esx_wbem&lt;br /&gt;
        command_line    $USER1$/check_esx_wbem.py &lt;a class="jive-link-external" href="https://$HOSTADDRESS:5989"&gt;https://$HOSTADDRESS:5989&lt;/a&gt; $ARG2$ $ARG3$&lt;br /&gt;
        }&lt;br /&gt;
&lt;br /&gt;
And the check as defined for one of my ESXi servers&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;username and password masked&lt;/li&gt;
&lt;/ol&gt;
define service{&lt;br /&gt;
        use                     linux-critical-server-service&lt;br /&gt;
        host_name               esx01&lt;br /&gt;
        service_description     ESXi Hardware Monitor&lt;br /&gt;
        check_command           check_esx_wbem!readonlyuser!somepassword&lt;br /&gt;
        }</description>
      <pubDate>Fri, 26 Jun 2009 21:33:45 GMT</pubDate>
      <author>mhanby</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-11653</guid>
      <dc:date>2009-06-26T21:33:45Z</dc:date>
      <clearspace:dateToText>8 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-11654</link>
      <description>I modified the script by adding the try catch block and now it works through nagios, strange in that I didn't change any of the nagios configurations.&lt;br /&gt;
&lt;br /&gt;
Thanks to Joshua:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://staff.washington.edu/joshuadf/esxi/check_esx_wbem.py"&gt;http://staff.washington.edu/joshuadf/esxi/check_esx_wbem.py&lt;/a&gt;</description>
      <pubDate>Fri, 26 Jun 2009 21:50:25 GMT</pubDate>
      <author>mhanby</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-11654</guid>
      <dc:date>2009-06-26T21:50:25Z</dc:date>
      <clearspace:dateToText>8 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-11671</link>
      <description>Wow, I just discovered this and all I can say is thank you.&lt;br /&gt;
&lt;br /&gt;
A tip for users of distros without python-wbem (like Ubuntu):&lt;br /&gt;
Get it from &lt;a class="jive-link-external" href="http://sourceforge.net/project/showfiles.php?group_id=133883"&gt;http://sourceforge.net/project/showfiles.php?group_id=133883&lt;/a&gt;&lt;br /&gt;
and install it with `python setup.py install`</description>
      <pubDate>Wed, 01 Jul 2009 14:16:52 GMT</pubDate>
      <author>voro</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-11671</guid>
      <dc:date>2009-07-01T14:16:52Z</dc:date>
      <clearspace:dateToText>8 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-11822</link>
      <description>I just saw this script. I have a few newbie questions:&lt;br /&gt;
&lt;br /&gt;
1. Where on my ESXi host do I store this script?&lt;br /&gt;
&lt;br /&gt;
2. Can I setup a cron job so that it runs the script at a certain time and then send an email?&lt;br /&gt;
&lt;br /&gt;
Thanks</description>
      <pubDate>Sun, 26 Jul 2009 19:50:36 GMT</pubDate>
      <author>cookieme</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-11822</guid>
      <dc:date>2009-07-26T19:50:36Z</dc:date>
      <clearspace:dateToText>7 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-11863</link>
      <description>After ESXi have been updated with this pachege from HP: hp-esxi4.0uX-bundle-1.1.zip (google the file name if you want to find it)extra classes has to been added to the script: &lt;a class="jive-link-external" href="http://www.intellipool.se/forum/lofiversion/index.php/t1548.html"&gt;http://www.intellipool.se/forum/lofiversion/index.php/t1548.html&lt;/a&gt; to alså check the new features. (Storage)&lt;br /&gt;
&lt;br /&gt;
After this update ESXi is aware of HP Storage adapers and disks. &lt;br /&gt;
One of our servers now shows a warning in vSpehere Client regarding storage (maybe faulty battery or something), but shows OK using this script. &lt;br /&gt;
&lt;br /&gt;
Any ideas anyone?</description>
      <pubDate>Thu, 30 Jul 2009 11:41:27 GMT</pubDate>
      <author>larvel</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-11863</guid>
      <dc:date>2009-07-30T11:41:27Z</dc:date>
      <clearspace:dateToText>7 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-13954</link>
      <description>Hi,&lt;br /&gt;
&lt;br /&gt;
running the current HP VMware ESXi 4.0.0 build-208167, and tried to to force a storage error by drawing one disk of a mirror, and pulling a plug from one power supply. &lt;br /&gt;
&lt;br /&gt;
Unfortunately only the power plug is shown as an CRITICAL error, but not the drawn disk. It is noticed, but not flagged as CRITICAL:&lt;br /&gt;
(output excerpt of check_esx_wbem.py verbose)&lt;br /&gt;
20091222 15:16:19 Check classe VMware_StorageExtent&lt;br /&gt;
20091222 15:16:20 Element Name = Disk 1 on HPSA1 : Port 1I Box 1 Bay 1 : 419GB : Data Disk&lt;br /&gt;
20091222 15:16:20 Element Name = Disk 2 on HPSA1 : Port 1I Box 1 Bay 2 : 419GB : Data Disk&lt;br /&gt;
20091222 15:16:20 Element Name = Disk 3 on HPSA1 : Port 1I Box 1 Bay 3 : 0GB : Data Disk : Disk Error&lt;br /&gt;
20091222 15:16:20 Element Name = Disk 4 on HPSA1 : Port 1I Box 1 Bay 4 : 931GB : Data Disk&lt;br /&gt;
20091222 15:16:20 Element Name = Disk 5 on HPSA1 : Port 2I Box 1 Bay 5 : 931GB : Data Disk&lt;br /&gt;
20091222 15:16:20 Element Name = Disk 6 on HPSA1 : Port 2I Box 1 Bay 6 : 931GB : Data Disk&lt;br /&gt;
20091222 15:16:20 Check classe VMware_Controller&lt;br /&gt;
20091222 15:16:20 Element Name = HP Smart Array P410i Controller : HPSA1&lt;br /&gt;
20091222 15:16:20 Check classe VMware_StorageVolume&lt;br /&gt;
20091222 15:16:20 Element Name = Logical Volume 1 on HPSA1 : RAID 1 : 419GB : Disk 1,2&lt;br /&gt;
20091222 15:16:20 Element Name = Logical Volume 2 on HPSA1 : RAID 1 : 931GB : Disk 3,4 : Interim Recovery&lt;br /&gt;
20091222 15:16:20 Element Name = Logical Volume 3 on HPSA1 : RAID 1 : 931GB : Disk 5,6&lt;br /&gt;
CRITICAL : Power Supply 1 Power Supply 1: Failure detected&lt;br&gt;CRITICAL : Power Supply 1&lt;br&gt;
&lt;br /&gt;
Does somebody already have a solution for this?&lt;br /&gt;
&lt;br /&gt;
Cheers,&lt;br /&gt;
-Matthias</description>
      <pubDate>Tue, 22 Dec 2009 15:24:59 GMT</pubDate>
      <author>mflacke</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-13954</guid>
      <dc:date>2009-12-22T15:24:59Z</dc:date>
      <clearspace:dateToText>2 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-13976</link>
      <description>It's that because HP agents reports disk failure in the label instead of in the classe status... Actually I own Dell servers which make me lazy for modifying the script... May be someone that owns HP servers can help to modify it</description>
      <pubDate>Tue, 22 Dec 2009 15:44:14 GMT</pubDate>
      <author>couak</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-13976</guid>
      <dc:date>2009-12-22T15:44:14Z</dc:date>
      <clearspace:dateToText>2 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-13955</link>
      <description>It`s that I have 4 other esxi servers running on HP that confuses me. It`s just on this server that the warning shows.</description>
      <pubDate>Tue, 22 Dec 2009 15:49:28 GMT</pubDate>
      <author>larvel</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-13955</guid>
      <dc:date>2009-12-22T15:49:28Z</dc:date>
      <clearspace:dateToText>2 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: Monitoring ESXi with Python script</title>
      <link>http://communities.vmware.com/docs/DOC-7170#comments-14579</link>
      <description>Branden modified the original script in order to monitor HP's servers.&lt;br /&gt;
Check it out at following URL : &lt;a class="jive-link-external" href="http://snednarb.wordpress.com/2010/02/02/get-hp-array-health-from-esxi-4-0/"&gt;http://snednarb.wordpress.com/2010/02/02/get-hp-array-health-from-esxi-4-0/&lt;/a&gt;</description>
      <pubDate>Mon, 22 Feb 2010 19:55:02 GMT</pubDate>
      <author>couak</author>
      <guid>http://communities.vmware.com/docs/DOC-7170#comments-14579</guid>
      <dc:date>2010-02-22T19:55:02Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
    </item>
  </channel>
</rss>

