Cheshire Cat Computing

Morning...
I have ran check_esx3 -N -H $HOSTADDRESS$ -C "$ARG1$" -V "$ARG2$" -l STATE

but the result is:

CRITICAL: VHosts: 0/12 up: SRV24PD(DOWN), SRV50PD(DOWN), SRV42PD (Sde%2fM(DOWN), SRV17PD (Proc.Ca(DOWN), SRV19PD (Provvig(DOWN), SELEWIN (Contr.T(DOWN), SRV21PD (Server (DOWN), SRV47PD (Diapaso(DOWN), SRV28PD (Hyperio(DOWN), CDF8DB (Database(DOWN), SRV15PD (Server (DOWN), SRV41PD (Spooler(DOWN)|allvms_up_ct=0;;;0;12 allvms_up_pc=0%;;;0;100

but it is not possible... all hosts are up and running!
Wich is the mistake?
Thank you for your help...

Bye

Davide.

Let me guess - you have esx 3.5? They changed the APIs (again) and the host up checks are all failing to work in the new version.
The latest version of check_esx3 has this fixed but has not been released yet due to other errors. Since we're so much at the mercy of the constantly changing and unpublished APIs the next plan was to change the vmware-stats script to use a different method of data collection.
At the moment there's no generally available fix for this becaue I've not been able to work on it for many months - work and family pressures (new baby). I'll try to get back into it before too long, I hope...

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

No, I haven't....
I'm running ESX 3.0.2.....

Looks like the latest verson of ESX now says 'poweredOn' instead of 'running' in the SNMP. I'll fix this so that both are considered valid. Thanks for this...

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

hello steve,

please be aware that beside of the text the OID changed too.
its now .8 instead of .6

thanks in advance,

birger

_________________
[size=85]
NagiosWiki http://www.nagioswiki.org
[color=#FF4000]NETWAYS GmbH http://www.netways.de
NETWAYS Blog http://blog.netways.de[/color][/size]

hello steve,

i put on a wiki page on http://www.NagiosWiki.org.

it would be nice if you link there if you update the http://www.NagiosExchange.org page for check_esx.

find it over here: http://www.nagioswiki.org/wiki/Plugin:check_esx

greetings,

birger

_________________
[size=85]
NagiosWiki http://www.nagioswiki.org
[color=#FF4000]NETWAYS GmbH http://www.netways.de
NETWAYS Blog http://blog.netways.de[/color][/size]

I'm currently at a performance monitoring course for vmware 3.5.

The new APIs for the VC make me think I should completely rewrite check_esx to instead query the VC and get stats out via the API, which will allow much easier monitoring of farms (which is better than monitoring individual ESX hosts) and guests. This would be the VMWare recommended way of doing it, too. However, it would mean a complete change to the check_esx program parameters and so on.

Also, providing a generic 'any CPU problems?' check is rather difficult as there are so many indicators and no real thresholds that generally work.

VMWare monitoring is only getting harder

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

I am having a heck of a time with this... if I touch ./vmware-stats and run the script with debug=1 it works as expected. If I switch off debug, it incorrectly reports that all VMs are down. VMware tools is installed on all VMs. Running ESX 3.0.0 Any ideas?

That happened to me before. Just follow what bschmidt said and everything would work out fine for sure.


Regards,
Carrey