Devmon and SNMP show a lot of promise, but the lack of documentation on ESX OIDs is making life difficult. I was working on this a while ago, but we had a "critical situation" develop here at work, I had to drop everything and I haven't had time to work on this for over 2 weeks now. :-(

Anybody else trying to monitor VMWare ESX with Devmon? Might be time to pool our efforts.

Here's what I have so far. (untar and move to Templates directory) Not much, but it's a start.

I have been trying to figure it all out from the output of snmpwalk and what I could find here. http://www.mibdepot.com/cgi-bin/vendor_index.cgi?r=vmware

Maybe somebody else has something to add? Even some better documentation could help.

Cheers V

From: mario andre [mailto:rower.master at gmail.com] Sent: Wednesday, 15 April 2009 10:58 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Hobbit testing for VMWare ESX system

Hi,

Another important thing is #esxcfg-firewall --openPort 1984,tcp,out,hobbituser

On Wed, Apr 15, 2009 at 6:26 AM, Dominique Frise <dominique.frise at unil.ch> wrote: rdeal wrote: Has anyone worked up a nice test for VMWare ESX server. I would like to get stats on the physical host. I have been testing and porting a script from deadcat : http://www.deadcat.net/viewfile.php?fileid=1048

I have it putting the memory and disk info into a format that Xymon will graph and it lists the VMs running. But no cpu info is given. Is everyone just using hobbit client locally on the ESX server configured to use esxtop?

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk<mailto:hobbit-unsubscribe at hswn.dk>

This is how we monitor our ESX3 servers: http://www.hswn.dk/hobbiton/2007/07/msg00036.html

Dominique

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk<mailto:hobbit-unsubscribe at hswn.dk>

NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.