Nagios Support Forum

I used the VMware Wizard and configured a VM Host to monitor.

I typed in my service account's Domain credentials:
domainname/service_account_name

The service account's username has a hyphen and a period in the name, ex. dep-service.regularname

When the wizard completed and the check comes back, the Status Information displays the following error: "ESX3 CRITICAL - Error: Cannot complete login due to an incorrect user name or password."

I am referencing the following forum post, below, with needing to use the forward slash "/" instead of the Windows-based backslash "\" method:
http://support.nagios.com/forum/viewtop ... 16&t=27132

The service account was given the needed Active Directory Domain security group permissions.

I have already installed the VMware SDK plugins as needed on our monitoring server, too.

Anything else to look at?

Can you make your check work from the CLI? Sample check to try:

lmiltchev wrote:Can you make your check work from the CLI? Sample check to try:

Code: Select all

/usr/local/nagios/libexec/check_esx3.pl -H "x.x.x.x" -u <username> -p dep-service.regularname -l "CPU"

At the Nagios XI server's console, I used your command and filled in the appropriate information to contact the VM Host using it's IP address and the Domain service account name:
<username> = domain/part1-part2.completeusername

The command did not prompt me to enter my password and I received the error:
ESX3 CRITICAL - Error: Cannot complete login due to an incorrect user name or password.

I tried using the escape character "\" in front of the hyphen and the period in the username, but still got the error message. I thought the hyphen and period were valid characters, though?

The Domain service name that I am using is used in my other NRPE and NSClient++ client checks, too, with no issues.

Try:

part1-part2.completeusername@domain

Did this work for you OP?

abrist wrote:Did this work for you OP?

I can use that method to login to various Windows servers, but not on the VM Host.
I'll do some more checking and will get back to you within a couple of days due to other priorities here. Sorry.

No problem.

I'm able to login, but was using the Host "H1" (explained further, below), instead of the VCenter Server.



Okay, here's the scenario:

1). vserver.a.b (a.b is the Domain name) is a VCenter Server and contains a few Datacenters (organizational placement).
2). Each Datacenter has one or more clusters (group of hosts).
3). Each Cluster may have a Resource Pool (for available resource usage) and one or more Host, we'll identify as "H1", "H2", etc.
4). Each Host may have several VMs (guest), which we'll identify as "VM1", "VM2", etc.
Picture scheme:
Vserver (vserver.a.b)
|
Datacenter (organization)
|
Cluster
|
Host1 (H1)
|__ VM1
|__ VM2
|
Host2 (H2)
|__ VM3
|__ VM4


QUESTION:
GOAL: We would like to monitor a Cluster's Host, "H1", which has 2 VM guests, "VM1" and "VM2".

So, if I set this up correctly in Nagios XI, I would use the VMware Monitoring wizard and add the VCenter Server, vserver.a.b, in the address first, using Username: name1-name2.name3@domain_name, choosing
"Monitor the VMware host"?
Then, if I want to monitor "VM1" and "VM2", I would use the VMware Monitoring wizard and add vserver.a.b, again, and choose "Monitor a guest VM on the VMWare host"?

However, how can I monitor "H1"? Reason: If there is a problem with H1, then we can identify that a problem is actually with the Host and not one of the VM's specifically.

It appears that the terminology that is used in Nagios XI, "Monitor the VMware host", is the VCenter Server, and doesn't actually mean a VMware Host, is what I seem to be running into.

Thank you.

However, how can I monitor "H1"? Reason: If there is a problem with H1, then we can identify that a problem is actually with the Host and not one of the VM's specifically.

You can just run our vmware monitoring wizard against it and select "Monitor the VMware host" under "Monitoring Mode" in step 2.

http://assets.nagios.com/downloads/nagi ... ios-XI.pdf

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.