Mar 9, 2010 6:22 PM
New VMware ESXi ZenPack
-
Like (0)
Thanks to Zenoss Master David Nalley for providing his VMware ESXi ZenPack. Currently this ZenPack provides monitoring for host hardware of VMware ESXi. This works on supported host platforms, and monitors fans, temperature, RAID arrays, controllers, individual drives, raid card batteries, power supplies, and storage.
The WBEM Classes that it checks are:
CIM_ComputerSystem
CIM_NumericSensor
CIM_Memory
CIM_Processor
CIM_RecordLog
OMC_DiscreteSensor
OMC_Fan
OMC_PowerSupply
VMware_StorageExtent
VMware_Controller
VMware_StorageVolume
VMware_Battery
VMware_SASSATAPort
Currently it checks - and if ok, reports OK, if there is a problem, it creates an event listing the specific component and problem.(ie which DIMM Slot a problem is occurring with and what the problem is)
Thanks David!
bombs out with
File "./check_esx_wbmem.py", line 78, in ?
instance_list = wbemclient.EnumerateInstances(classe)
File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/lib/pywbem/cim_operations.py", line 403, in EnumerateInstances
ClassName = CIMClassName(ClassName),
File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/lib/pywbem/cim_operations.py", line 219, in imethodcall
raise CIMError(code, tt[1]['DESCRIPTION'])
pywbem.cim_operations.CIMError: (6, u'The requested object could not be found')
on 2.5.0. I have verified correct username and password.
upgraded to 2.5.2 , same error. Also seems to crash zenmodeler, but that could be unrelated.
Traceback (most recent call last):
File "./check_esx_wbmem.py", line 78, in ?
instance_list = wbemclient.EnumerateInstances(classe)
File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/lib/pywbem/cim_operations.py", line 403, in EnumerateInstances
ClassName = CIMClassName(ClassName),
File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/lib/pywbem/cim_operations.py", line 219, in imethodcall
raise CIMError(code, tt[1]['DESCRIPTION'])
pywbem.cim_operations.CIMError: (6, u'The requested object could not be found')
Great - thanks! I've been waiting for this one.
But where (in zProperties? "zCommandUsername"?) do I set the login and password to the HTTPS-server? All I get now are error-events...
Cmd: /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://192.168.x.y:5989 user - Code: 1 - Msg: General error
Update:
I found out it has to be "zCommandUsername" and "zCommandpassword":
../ZenPacks/dnalley/VMwareESXi# grep -r zComm *
objects/objects.xml:${here/ZenPackManager/packs/ZenPacks.dnalley.VMwareESXi/path}/check_esx_wbmem.py https://${dev/manageIp}:5989 ${dev/zCommandUsername} ${dev/zCommandPassword}
Right, the password is there too now, but still a general error:
Cmd: /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://192.168.x.y:5989 user password - Code: 1 - Msg: General error
Running the above command on the CLI on the Zenoss-host does work however.
Update 2:
Using the test-option in the template reveals even more issues:
Executing command |
/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://192.168.x.y:5989 user password |
against 192.168.x.y |
'import site' failed; use -v for traceback |
Traceback (most recent call last): |
File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py", line 24, in <module> |
import sys,os |
ImportError: No module named os |
DONE in 0 seconds |
Message was edited by: hbokh
I had the same error, but running zenoss restart as the zenoss user fixed it....
I get the exact same error as fearthepenguin, fresh VMware image, 2.5.2
I had the same error, but running zenoss restart as the zenoss user fixed it....
That's somewhat of a fix indeed. I get some events now.
Weird... because restarting the zenoss_stack from /etc/init.d/ as root (Ubuntu Linux 9.10 x86_64) won't!
I was having th esame issue as hbokh. Turns out the script does not like the complex password that I had set for my root account. Started and ended with a #
Once I changed it to somethign simple (temporarily I hope) it worked.
Hopefuly this can be corrected
everything seems to work ok but there is no Data collected.
2010-03-26 02:02:41 | INFO | zen.Utils | Executing command: /usr/local/zenoss/zenoss/bin/zenmodeler run --now --monitor localhost -F -d 192.168.x.x --weblog |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | Connecting to localhost:8789 |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | Connected to ZenHub |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | Collecting for device 192.168.x.x |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | No WMI plugins found for 192.168.x.x |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | No Python plugins found for 192.168.x.x |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | No command plugins found for 192.168.x.x |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | SNMP monitoring off for 192.168.x.x |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | No portscan plugins found for 192.168.x.x |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | Scan time: 0.17 seconds |
2010-03-26 02:02:43 | INFO | zen.ZenModeler | Daemon ZenModeler shutting down |
2010-03-26 02:02:45 | INFO | zen.PerformanceConf | configuration collected |
Executing command |
/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://192.168.x.x:5989 root ****** |
against 192.168.x.x |
OK |
DONE in 3 seconds |
But after all this there is no data in the Tabs (Hardware,status,OS,Perf)!!!!!!
please help!
I don’t think this ZenPack actually shows any info. Just warns if there is a problem. Correct me if I'm wrong
the first post said:
"Currently it checks - and if ok, reports OK, if there is a problem, it creates an event listing the specific component and problem.(ie which DIMM Slot a problem is occurring with and what the problem is)"
Can someone help with this?
someone installed it already and it is working?
can you tell me what should i see in the Zenoss?
Well, nothing really - you bind it to the class you want to have your
ESXi hosts in, and then it goes... Nothing happens unless there is a
problem, in which case an event is created. It doesn't claim to do
graphs for instance.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
maayanay wrote, On 3/29/2010 2:05 PM:
Can someone help with this?
someone installed it already and it is working?
can you tell me what should i see in the Zenoss?
>
it si not suppose to show something like
Processor: OK
Storage: OK
Fans: OK
like in the ESXi GUI?!?
do i have some way to make sure that zenoss is really able to monitor it correctly without taking out a DISK.
I ask this because all of my Zenoss tabs for this device are totaly empty i even don't have the OS MODEL, OS version, SYSTEM UP TIME
nothing... is this ok?
I can't say, I didn't write the zenpack, nor do I use it - that's just
what the documentation says. Of course, feel free to improve the zenpack
and submit updates. I'm sure the community would benefit.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
maayanay wrote, On 3/30/2010 4:41 PM:
it si not suppose to show something like
Processor: OK
Storage: OK
Fans: OK
like in the ESXi GUI?!?
do i have some way to make sure that zenoss is really able to monitor it correctly without taking out a DISK.
I ask this because all of my Zenoss tabs for this device are totaly empty i even don't have the OS MODEL, OS version, SYSTEM UP TIME
nothing... is this ok?
>
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||