Nagios Support Forum

PhilG wrote:Nope.
Error: "ESX3 CRITICAL - Error: Cannot complete login due to an incorrect user name or password."

I have no problem monitoring the actual VCenter server, but when I provide the Host's IP, and the same username and password (which I have successfully used to monitor the VCenter server and the VM guests), that's the error I get, above.

VCenter Server (has an IP which can be pinged, and I can login to) -> DataCenter -> Cluster -> Host (has an IP, but you don't login/authenticate on to) -> VM (all Linux or Windows servers, can login to).

Using the VMware Wizard and choosing "Monitor the VMware host", I can add the VCenter Server and authenticate with the service account mentioned earlier with no issues.

Using the VMware Wizard and choosing "Monitor a guest VM on the VMWare host", I add the VCenter Server and account, then the wizard identifies and lists all the VMs (powered on or turned off), but no Hosts.

If I use the VMware Wizard and choose "Monitor the VMware host", and then try to add the Host (using the IP or FQDN) and authenticate with the service account mentioned earlier, I get that "ESX3..." error message.

I can ping the Hosts from my workstation with no issues. I can go into our VMware vCenter console and see everything working with no issues.

Why can't I monitor the Host? The parent is the vCenter Server, then the child is the Host, then the VM is a child to the Host.

I don't believe the wizard was written that way. The hosts aren't treated like guests in vCenter (from this Wizard's perspective). You need to monitor each host directly using this wizard, which means individual credentials for each host.

I suggest you look at box293_check_vmware which can be downloaded here:
http://exchange.nagios.org/directory/Pl ... re/details

There is a wizard for it:
http://exchange.nagios.org/directory/Ad ... rd/details

It has a more feature rich wizard and the plugin will do a lot more than what check_esx3.pl does. It treats hosts as children of vCenter, so only one set of credentials is required.

PhilG, let us know if Box293 answered your question.

lmiltchev wrote:PhilG, let us know if Box293 answered your question.

I'll address this with my team and will get back to you if this is something we are willing to implement, use basic monitoring, or ditch the idea altogether.

Alright.

The team was not interested in implementing the other plug-in.

Back to basic monitoring.

Can you try wrapping the username and the password in single or double quotes? Do you have any special characters in the password? Can you successfully log in the ESXi host using the same (domain) credentials?

lmiltchev wrote:Can you try wrapping the username and the password in single or double quotes? Do you have any special characters in the password? Can you successfully log in the ESXi host using the same (domain) credentials?

I am very sorry that I did not come back until today, Fri. 3/13/2015 to see this.

At this time, we'll continue using basic monitoring. I am doing Linux Administration, Web Administration, some Windows Administration, Applications Administration, and I'm the only guy with no backup now that this place decided to reorg internally and move my colleague (who I use to work with doing this stuff) over to a different area, and he just informed me that he's leaving in a few weeks. I'm a little frazzled right now, so sorry to vent.

PhilG wrote:I'm a little frazzled right now, so sorry to vent.

I think all IT people everywhere can agree that part of their job at times is to be a therapist, so it's quite alright :)

For the time-being, are we clear to close this thread up?

tmcdonald wrote:

PhilG wrote:I'm a little frazzled right now, so sorry to vent.

I think all IT people everywhere can agree that part of their job at times is to be a therapist, so it's quite alright

For the time-being, are we clear to close this thread up?

I was in a class for this past week.

Yes, please do close this post.