Cheshire Cat Computing

Hi Steve,
Great job.
I'm newbie in Linux, but I have here Nagios installed (not by me, but it's here).
I have read almost whole discussion, and I would ask one think.
Is it possible to make short howto for newbies like me?
Because, I have seen many opinions and questions here.

So my questions are:
- do I have to install anything on my Vcenter?
- on Linux server I will install Perl API - is that one right ? (http://communities.vmware.com/community ... e_sdk_perl) - VI Perl Toolkit 1.6 Download
- next step is only your script

what is : SOAP::Lite and Class::MethodMaker. ??

sorry for my stupid questions

thank you

sonic

Nothing needs to be installed on the Virtualcentre server.

That is the correct Perl API (they've changed their description of it recently)

Those two are Perl extension modules. You can install them using CPAN on Linux, or PPM on Windows. To use CPAN, have an Internet connection and C compiler handy and use 'perl -MCPAN -e shell' then 'install SOAP::Lite' etc. Your distribution may have packages for these modules already available.

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

Doh, nevermind on the --host problem. Using the IP address of the ESXi box instead of it's name seems to work fine.

Hmmm....new installation and the VMware perl toolkit (and dependencies) all said they installed successfully.

However, I get this message:
Can't locate VMware/VIRuntime.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at ./check_vmware line 34.
BEGIN failed--compilation aborted at ./check_vmware line 34.

OS: Ubuntu Server 10.04 LTS

Any ideas?

The plugin can't find the VMWare toolkit libraries.

Make sure you've installed the Perl 10 version of the libraries, and make sure they installed ot the site_perl path -- if not, you'll need to add the path to the @INC path in the script. Also make sure you've the '-epn' line near the top of the script if you're using the Embedded perl compiler (the script doesnt work with the EPN).

My guess is that the toolkit didnt install to your site_perl path properly.

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

Is this known to work with the new SDK?
http://communities.vmware.com/community ... e_sdk_perl

Scrap that - I've installed the new version and it works fine.

I'm only planning to use this to monitor the Cluster and ESX hosts themselves (via the VC), as I already have monitoring for all the guests via WMI.


Question: Is NSCA required to return valid data into Nagios? I can return valid information to the CLI (eg. Virtual Machine CPU Usage is Yellow) but within Nagios I get (Return code of 127 is out of bounds - plugin may be missing).

It's been a while since I implemented/developed a NAGIOS system - any help?

Update:

It returns normal data when logged in as root ('No alarms detected')

When logged in as user Nagios, it returns:

SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server certificate request A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client certificate A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:SSLv3 read finished A
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server certificate request A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client certificate A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:SSLv3 read finished A
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server certificate request A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client certificate A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:SSLv3 read finished A
No alarms detected.

This should work with the current SDK, as you've discovered. However...

NSCA is not required for the plugin to run in normal, active-check mode. However if you want it to run in batch mode (where it queries all the VMs at once and submits status checks for them all together) then you will need NSCA.

If you're ggetting all those options, then you are running in SSL debug mode for some reason. There's a possibility this may be due to the new SDK having differrent defaults. Fortunately the global options to the script come from the SDK so you can run check_vmware --help to see if there are additional debug options you can now disable; I will obtain the absolutely latest SDK and test it here.

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