Cheshire Cat Computing

Hello Steve,
I just tried version 0.9. All works but I do get the "No Fairness.." msg.
I deleted it from the source code, and now it is better.
Also about the disk i was able to get the instance name by doing a --verbose
<val xsi:type="DatastoreSummary">
<datastore type="Datastore">datastore-42</datastore>
<name>CX300-H-1</name>
<url>sanfs://vmfs_uuid:468d22c0-18e2777d-338f-001aa01ca921/</url>
<capacity>536602476544</capacity>
<freeSpace>222202691584</freeSpace>
<accessible>true</accessible>
<multipleHostAccess>true</multipleHostAccess>
<type>VMFS</type>

Then I used:
./check_vm.pl --config=configvm.txt --report=disks --instance="CX300-H-0"
All filesystems within parameters|free=32489078784;;;0; total=557540442112;;;0;
I was wondering if the Used bytes exists ? and the Crit/Warn could be set?

Saddly still from my Centreon/Nagios interface I get no output.
/usr/local/nagios/libexec/check_vm.pl --version
VI Perl Toolkit version: 1.6
Script 'check_vm.pl' version: 1.0
I know it localy it works, even under user nagios. Any ideas what it could be? I have many other perl scripts that works fine.

Anyways, thx very much for the great work!

No Fairness - this is a problem with the VI API, hopefully it will be fixed in v3.5.4 or later. Just ignore the problem for now.

Disk used bytes - these exist of course, but are not (yet) reported in the perfinfo string. I can add this. You can set thresholds ion the check_vmware command line with --warn and --crit, see the help text.

What happens when you run it with --debug on the Nagios server? Do you get any output at all?

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

Hi Steve,

just for your information. We migrated to vSphere 4 during this weekend. Your Plugin is still working! It was not necessary to do any changes to the API and the Plugin Config.

Regards from Germany.

Dennis

Thanks for the info! We're not getting vSphere4 for another few weeks so its good to have the advance info. Im hoping the 'No Fairness' problem and performance speed issues are fixed in the vS4 API as well...

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

Hi Steve,

i didn't upgraded the Perl API Toolkit yet. It's still Version 1.6 which seems to be the latest.

attached you find a screenshot of your esx nagios checks.



So the "No Fairness" problem is still there.

Regards

Dennis

Just to be sure, you won't ever get Fairness data unless you have a cluster configured with HA and DRS enabled (this is what the fairness is used for). In the VC client interface you should see fairness charts showing the loading split between the members of the cluster in this case.

The next version of the agent should probably not display this warning since it causes so many worries and is not really a problem...

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

Hi,

I tried out check_vmware today. All I can check on an ESX 3.5 Host is the whole error status and the datastore of the ESX Server. If I want to check for example CPU, RAM, NET from a guest system, I only get the following result:



The user I use is a root user. I don`t want to install NSClient++ on all guests so it would be great if it is possible just to check the ESX 3.5 Servers.

THX, hambuergaer.

Which version are you using? The /0 error appeared in the previous version and was killed off (I think). I may not have properly updated all the online repositories due to having to leave work at short notice for my father's funeral ( . Will be back in NZ in a week and hopefully can catch up with things then. Can you confirm you have v0.9?

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

Yes, I`m using V09.b

Hi Steve,

sorry for my late reply. Yes, we have a HA and DRS Cluster.

Today i found some time to play with the vSphere Management Assistante Appliance: http://www.vmware.com/appliances/directory/178973

I copied your plugin to the Appliance and started testing.....

First I tested checking the cpu and memory data of a single esx host over the vCenter Server.


At the second test i did the same query for our HA & DRS Cluster over the vCenter Server.


We also have a single esx 4.0 host here, which is not in a cluster. I ran these checks also to this host.


The No Fairness data problem is still there and VMWare didn't fixed it in vSphere 4. So we have to wait again....

Best wished from Germany

Dennis