ZenPacks : VMware ESXi : Comments

RE: VMware ESXi

community@zenoss.org — Wed, 17 Mar 2010 08:25:23 GMT

Works with ESXi 4.0

But dont with oldest 32bit 3.5 :/ Any idea how to add it?

RE: VMware ESXi

community@zenoss.org — Sat, 17 Apr 2010 17:05:50 GMT

I tried to set this up with two ESXi 4 servers and I believe I'm getting denied access or have something setup wrong.I'm a bit new to Zenoss and zenpacks. I have updated the zCommandUsername with my user of root and also the zCommandPassword with my password. When I testCheckESXi Hardware this is what I get.

Executing command

/home/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://192.168.200.48:5989 root (mypassword)

against 192.168.200.48

/bin/sh: /home/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py: Permission denied

DONE in 0 seconds

Any help would be greatly appreciated.

RE: VMware ESXi

community@zenoss.org — Tue, 18 May 2010 14:31:59 GMT

I am having the same issue.

Cmd: /home/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://xxxxxxx:5989 root (my correct password) - Code: 126 - Msg: Command invoked cannot execute, permissions problem or command is not an executable

Any ideas? These are ESXi 3.5 builds

RE: VMware ESXi

community@zenoss.org — Tue, 18 May 2010 20:21:49 GMT

I found that this permissions problem was accessing the python script (/home/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py). Once I opened up the directory security to this folder it started working properly.

RE: VMware ESXi

community@zenoss.org — Tue, 18 May 2010 20:33:33 GMT

Noob here, how do I do that? I really appreciate the fast response.

RE: VMware ESXi

community@zenoss.org — Fri, 21 May 2010 13:34:54 GMT

Any word or direction to be pointed? It would be really nice to get this working.

EDIT: I changed the permissions to allow zenoss zenoss 777 and I can run the template against the devices and the command shows OK. However, now the event log is saying that the CMD is timing out. Any ideas?

RE: VMware ESXi

community@zenoss.org — Tue, 25 May 2010 23:06:59 GMT

I'm not a noob and I'm having the same issue :-). Any ideas?

RE: VMware ESXi

community@zenoss.org — Tue, 15 Jun 2010 07:49:44 GMT

For me plugin returns only OK. No data from plugin, no data in zenoss. What I did wrong?

[root@zenoss ~]# /opt/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://SERVER:5989 root PASSWORD
OK

RE: VMware ESXi

community@zenoss.org — Tue, 15 Jun 2010 13:25:38 GMT

You're running as root there, does the 'zenoss' user have permission to run that script?

Thanks,

Matt Ray

Zenoss Community Manager

community.zenoss.org

mray@zenoss.com

RE: VMware ESXi

community@zenoss.org — Tue, 15 Jun 2010 18:30:27 GMT

Yes. I ran it as zenoss. The result is the same.

[zenoss@zenoss ~]$ /opt/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://SERVER:5989 root PASSWORD
OK
[zenoss@zenoss ~]$

RE: VMware ESXi

community@zenoss.org — Tue, 15 Jun 2010 19:29:23 GMT

Can You help me with trace this? I dont know python so well. I use last stable zenoss from RPM on centos.

[zenoss@zenoss ~]$ python -m trace --trace /opt/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://SERVER:5989 root PASSWORD
--- modulename: threading, funcname: settrace
threading.py(70):     _trace_hook = func
--- modulename: trace, funcname: ?
<string>(1):   --- modulename: trace, funcname: ?
check_esx_wbmem.py(24): import sys,os
check_esx_wbmem.py(25): sys.path.append(os.path.join(os.path.dirname(__file__), "lib"))
--- modulename: posixpath, funcname: dirname
posixpath.py(119):     return split(p)[0]
--- modulename: posixpath, funcname: split
posixpath.py(77):     i = p.rfind('/') + 1
posixpath.py(78):     head, tail = p[:i], p[i:]
posixpath.py(79):     if head and head != '/'*len(head):
posixpath.py(80):         head = head.rstrip('/')
posixpath.py(81):     return head, tail
--- modulename: posixpath, funcname: join
posixpath.py(58):     path = a
posixpath.py(59):     for b in p:
posixpath.py(60):         if b.startswith('/'):
posixpath.py(62):         elif path == '' or path.endswith('/'):
posixpath.py(65):             path += '/' + b
posixpath.py(59):     for b in p:
posixpath.py(66):     return path
check_esx_wbmem.py(27): import time
check_esx_wbmem.py(28): import pywbem
Traceback (most recent call last):
File "/opt/zenoss/lib/python2.4/trace.py", line 788, in ?
    main()
File "/opt/zenoss/lib/python2.4/trace.py", line 776, in main
    t.run('execfile(%r)' % (progname,))
File "/opt/zenoss/lib/python2.4/trace.py", line 483, in run
    exec cmd in dict, dict
File "<string>", line 1, in ?
File "/opt/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py", line 28, in ?
    import pywbem
ImportError: No module named pywbem
[zenoss@zenoss ~]$

RE: VMware ESXi

community@zenoss.org — Wed, 16 Jun 2010 00:30:37 GMT

I'm seeing this too:

[zenoss@zenoss VMwareESXi]$ /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://<system IP>:5989 <admin user> <admin pw>
OK

It seemed like I might need the WBEM zenpack installed, which I just did, but I still get the "OK" without any data. These are the zenpack versions I'm using:

ZenPacks.dnalley.VMwareESXi

dnalley

David Nalley

1.0

Yes

ZenPacks.community.WBEMDataSource

community

Egor Puzanov

2.5

Yes

One thing I noticed when I ran the trace on my system was that I also got the error "ImportError: No module named pywbem"

Should this come standard with the Zenoss python package?

Thanks!

RE: VMware ESXi

community@zenoss.org — Wed, 16 Jun 2010 21:17:47 GMT

The username and password fields really should be quoted in the command line for the check_esx_webmem.py script. Not everyone uses alpha-numeric usernames and passwords.

RE: VMware ESXi

community@zenoss.org — Wed, 16 Jun 2010 23:39:50 GMT

I've tried it again as the zenoss user with the username and password fields quoted, but I'm still seeing just the "OK" message:

/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://10.57.132.14:5989 '$AdminUser' '$AdminPw'

I then tried tracing the command with the quoted credentials, but I don't thin it went over well:

python -m trace --trace /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://10.57.132.14:5989 '$AdminUser' '$AdminPw' | wc -l

4811210

not sure I should be getting almost 5 million lines in trace ;p

What *is* the expected output from running this (w/o trace) from the command line?

RE: VMware ESXi

community@zenoss.org — Thu, 17 Jun 2010 14:16:50 GMT

Hi Riodutchie, my comment was actually aimed at the maintainer of the package, rather than you specifically.

But for you andsome of the other people posting here, I think the package is actually operating as it's supposed to. It only monitors the ESXi machine for hardware failures. If there are no failures it returns "Ok" which is passed to the automatic parser and results in nothing being done. If it sees a real error it returns a different message like "Critical : IPMI SEL" which one of my blades is actually returning.

It not supposed to do any graphs or datapoints yet.

RE: VMware ESXi

community@zenoss.org — Fri, 18 Jun 2010 02:27:48 GMT

Can this check adaptec RAID status ?..... please advise

RE: VMware ESXi

community@zenoss.org — Fri, 18 Jun 2010 13:22:40 GMT

According to this user guide Adaptec Raid 2405 will forward warning and error events to the System Event Log which should be read by this ZenPack. The error example I used above indicated that my IPMI System Event Log was full. So I would expect the events to show up. The best methodology though would be to figure out a way to articially trigger a warning or error in the Raid system and verify that it gets detected and recorded.

So it won't check the RAID status directly, but it should check the System Event Log and the RAID system should send its messages to the System Event Log.

RE: VMware ESXi

community@zenoss.org — Sun, 05 Sep 2010 09:19:00 GMT

Install under Zenoss 3.0.

Installing under Zenoss 3.0 seems don't works. I tried to rename ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg to ZenPacks.dnalley.VMwareESXi-1.0.egg but won't install.

Do you plan to release a Zenoss 3 version? Have you an installation workaround.

Thanks

RE: VMware ESXi

community@zenoss.org — Tue, 07 Sep 2010 16:19:34 GMT

You can download a Python 2.6 version from here: http://dev.zenoss.org/zenpacks/

RE: VMware ESXi

community@zenoss.org — Wed, 08 Sep 2010 13:44:22 GMT

The script frequently returns 'command timed out'. Most of the time this will happen 2-3 times and then it will run properly and return OK. Most of the servers are ESXi v4.0 and are located at remote sites Is anyone else seeing this and do you know if this is a timeout setting in Zenoss or on the ESXi server? It would be great if this timeout setting could be increased to 60 seconds.

Thanks

Executing command

/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://10.0.25.19:5989 root password

against CMSESXi2

Command timed out

DONE in 31 seconds

RE: VMware ESXi

community@zenoss.org — Fri, 08 Oct 2010 00:13:34 GMT

Am running into the following error with Zenoss v3.0.2 installed on Ubuntu 10.4.

Preparing Command...

Executing command /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.6.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://10.0.0.19:22 root PASSWORD against 10.0.0.19

Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.6.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py", line 78, in

instance_list = wbemclient.EnumerateInstances(classe)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.6.egg/ZenPacks/dnalley/VMwareESXi/lib/pywbem/cim_operations.py", line 404, in EnumerateInstances

**params)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.6.egg/ZenPacks/dnalley/VMwareESXi/lib/pywbem/cim_operations.py", line 173, in imethodcall

raise CIMError(0, str(arg))

pywbem.cim_operations

CIMError

(0, 'Socket error: [Errno 1] _ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol')

DONE in 0 seconds

Any ideas?

RE: VMware ESXi

community@zenoss.org — Wed, 27 Oct 2010 18:36:36 GMT

We have just upgraded from Zenoss 2.5.1 to 2.5.2 and found that this ZenPack broke. The command in the performance template fails to run - basically because it cannot find the right Python. I have fixed the problem by editing the first line of the ZenPack's check_esx_wbmem.py script from:

#!/usr/bin/env python

#!/usr/bin/env /usr/local/zenoss/python/bin/python

Which seems to work for us.

I don't think this is specific to this ZenPack though - any command template that runs a Python script in the same way is going to run into the same issue.

Has anyone else found this / solved it??

Cheers,

Jane

RE: VMware ESXi

community@zenoss.org — Wed, 27 Oct 2010 19:14:33 GMT

Hi Jane:

I don't think that will be a fix that can be pushed to the ZenPack - as not all install are in /usr/local/zenoss.

It strikes me that it's likely a enviroment variable that was stripped in 2.5.2, but I haven't looked to confirm that. I'd guess that setting

Cheers,

David

RE: VMware ESXi

community@zenoss.org — Thu, 04 Nov 2010 11:12:25 GMT

This turned out to be a known issue with Debian systems upgraded from Zenoss 2.5.1 to 2.5.2 see http://community.zenoss.org/message/46604#46604 . Effectively lots of things driven from the GUI lost PATH.

Cheers,

Jane

RE: VMware ESXi

community@zenoss.org — Tue, 23 Nov 2010 04:11:16 GMT

It would be great if the version is released for 3.0. Looking forward to the new version.

Thanks,

Gavin

RE: VMware ESXi

community@zenoss.org — Thu, 25 Nov 2010 16:39:36 GMT

Hi, i'm trying to monitor the hardware health in a esxi 4.0 and in a esxi4.1 with your zenpack.

i had import your zenpack with no problem but when i try to add a server to zenoss (version 2.4.2) this is the result.....

Discover Devices

Time	Level	Module	Message
2010-11-25 16:35:56	INFO	zen.Device	device name 'sgmesxi03.mp.sgmd.local' for ip ''
2010-11-25 16:35:57	INFO	zen.Device	setting group ['/Esxi']
2010-11-25 16:35:57	INFO	zen.Device	setting performance monitor to localhost
2010-11-25 16:35:57	INFO	zen.Utils	Executing command: /home/zenoss/bin/zendisc run --now -d sgmesxi03.mp.sgmd.local --monitor localhost --deviceclass /Server/VMware/ESXi --weblog
2010-11-25 16:36:03	INFO	zen.ZenDisc	Connecting to localhost:8789
2010-11-25 16:36:03	INFO	zen.ZenDisc	Connected to ZenHub
2010-11-25 16:36:03	INFO	zen.ZenDisc	Looking for sgmesxi03.mp.sgmd.local
2010-11-25 16:36:11	INFO	zen.ZenDisc	Result: Discovered device sgmesxi03.mp.sgmd.local.
2010-11-25 16:36:11	INFO	zen.ZenDisc	No WMI plugins found for sgmesxi03.mp.sgmd.local
2010-11-25 16:36:11	INFO	zen.ZenDisc	No Python plugins found for sgmesxi03.mp.sgmd.local
2010-11-25 16:36:11	INFO	zen.ZenDisc	No command plugins found for sgmesxi03.mp.sgmd.local
2010-11-25 16:36:11	INFO	zen.ZenDisc	SNMP collection device sgmesxi03.mp.sgmd.local
2010-11-25 16:36:11	INFO	zen.ZenDisc	plugins: zenoss.snmp.NewDeviceMap, zenoss.snmp.DeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap, zenoss.snmp.IpServiceMap, zenoss.snmp.HRFileSystemMap, zenoss.snmp.HRSWInstalledMap, zenoss.snmp.HRSWRunMap, zenoss.snmp.CpuMap
2010-11-25 16:36:11	INFO	zen.ZenDisc	No portscan plugins found for sgmesxi03.mp.sgmd.local
2010-11-25 16:36:19	INFO	zen.SnmpClient	Device timed out: SNMP info for sgmesxi03.mp.sgmd.local at 172.16.20.13:161 timeout: 2.5 tries: 2 version: v1 community: sgm
2010-11-25 16:36:19	INFO	zen.SnmpClient	snmp client finished collection for sgmesxi03.mp.sgmd.local
2010-11-25 16:36:19	WARNING	zen.SnmpClient	Device sgmesxi03.mp.sgmd.local timed out: are your SNMP settings correct?
2010-11-25 16:36:19	INFO	zen.ZenDisc	No change in configuration detected
2010-11-25 16:36:19	INFO	zen.ZenDisc	Scan time: 8.18 seconds
2010-11-25 16:36:19	INFO	zen.ZenDisc	Daemon ZenDisc shutting down
2010-11-25 16:36:20	INFO	zen.ZenDisc	zendisc shutting down
2010-11-25 16:36:20	INFO	zen.DeviceLoader	Device sgmesxi03.mp.sgmd.local loaded!

open the esxi host with vsphere i can see all the hardware health.

Can you gime some help to resolve this problem?

Thank

Stefano

RE: VMware ESXi

community@zenoss.org — Mon, 24 Jan 2011 18:42:45 GMT

Can you do an snmpwalk to that server? IF you can't then you have an SNMP configuration problem. Either the server is not setup right, or you have the wrong values in your zProperties for SNMP.

RE: VMware ESXi

community@zenoss.org — Tue, 01 May 2012 08:44:08 GMT

I keep on getting summary CRITICAL : IPMI SEL on some blades with no other information. What does this mean?

RE: VMware ESXi

community@zenoss.org — Fri, 19 Jul 2013 16:29:40 GMT

Hello, this script didn't return anyinformation about NICs, and HBAs (fibrechannel for example) connected to the server.

Are there any work arround this?

I want to replace HP SIM (and its hardware monitoring of hp servers with vmware). In HP SIM I can see a warning on a disconnected nic, but I do not find the way to do this with zenoss (esxi 5.1 + offline bundle)