Solved!
Go to SolutionDH
daniel.hecht
6 Posts
0
185368
January 18th, 2012 08:00
Monitoring ESXi 5 Hardware
Hi,
I would like to monitor my ESXi 5 Hardware. Therefore I need to get the information via WBEM as SNMP is not supported anymore.
How can that be done with vFoglight (6.6)?
I did a few searches on google and looked through the discussions on this community and was not able to find anything helpful.
Thanks,
Daniel
daniel.hecht
6 Posts
500
0
Posted February 13th, 2012 06:00
Bump.
Sorry for that, but does really noone have some information about that?
daniel.hecht
6 Posts
501
0
Posted February 14th, 2012 12:00
Thats what we do either. But I found no information on how to get the information on the hardwarestatus of the ESXi 5 server.
daniel.hecht
6 Posts
501
0
Posted February 16th, 2012 06:00
In the vSphere Client under Hardwarestatus of an ESX(i) Server you can get information of all available sensors on that specific ESX(i) Host.
This is the information I would like to have in a dashboard, most important would be the power drawn by this system.
At the moment I you PRTG for that (uses WBEM to get this information) but it is an eval and I like to have this information in one system: vfoglight.
daniel.hecht
6 Posts
501
0
Posted February 20th, 2012 06:00
Thank you for that information Prasad.
daniel.hecht
6 Posts
501
0
Posted February 20th, 2012 10:00
Is it possible to get that information from the vCenter server with vFoglight with any kind of protocol?
Would just the alarms from vCenter on the HW status be sufficient or would you want the actual CIM data? You can get the CIM data, but it's not easily available via PowerCLI + Custom agent, so it's really more VMware CIM SDK programming and a custom agent. The alarms would be much simpler to have fire based on the ones in vCenter already.
DELL-Thomas B
171 Posts
390
0
Posted June 25th, 2013 21:00
I've been plugging away on this lately and made some progress on IPMI/CIM data. I'd really like to pull it from vCenter directly, but their API is turning out to be quite a pain in how they gather from each vendor. In the end I will most likely write a custom agent that gets what I need directly from each host on a periodic basis from each host directly. In the end I think this will work out better since I can then use it for any host, running VMware or not.