ESX Host Monitoring not working--Service check timed out

[amitgupta19]

Currently i am running the following command

check_esx3.pl -H xxx.xxx.xxx.xxx -u xxxxxxxxx -p xxxxxxxx -t 60 -l cpu -s usage -w 75 -c 80

Can you please modify the command which i should try now?

[scottwilkerson]

Run this command to see if it shows any output (replacing xxx.xxx.xxx.xxx with the IP you are using)

Code: Select all

curl -vvv "https://xxx.xxx.xxx.xxx:443/sdk/vimService.wsdl"

[amitgupta19]

[amgupta@yyyyyyy01 libexec]$ sudo curl -vvv "https://xxx.xxx.xxx.xxx:443/sdk/vimService.wsdl"
[sudo] password for amgupta:
* About to connect() to xxx.xxx.xxx.xxx port 443 (#0)
* Trying xxx.xxx.xxx.xxx...
* Connection timed out
* Failed connect to xxx.xxx.xxx.xxx:443; Connection timed out
* Closing connection 0
curl: (7) Failed connect to xxx.xxx.xxx.xxx:443; Connection timed out

[scottwilkerson]

So you are getting a connection timeout.

Either your Nagios server cannot route to xxx.xxx.xxx.xxx or it is not listening at the vmware API endpoint

[amitgupta19]

Any Idea what can be done to correct this Problem

[scottwilkerson]

I would first check routing, can you ping xxx.xxx.xxx.xxx from your Nagios server?

Do you have a firewall between them?

[amitgupta19]

Yes i am able to ping the ESX Host.

I don't think that there is firewall in between them. Because all the ESX Hosts located in the same network.

I have problem with only one.

[scottwilkerson]

The only other thing I can think of is "vSphere API" isn't a licensed feature for this ESX server.

Beyond that, you are going to have to reach out to vmware about why it is not allowing access to the API

[amitgupta19]

It has been resolved.
Thanks for your support.
It was due to wrong IP of the Device i was using.

[benjaminsmith]

Hello @amitgupta19,

It has been resolved.
Thanks for your support.
It was due to wrong IP of the Device i was using.

Thanks for the update and glad it's been solved! We'll close out this thread, but feel free to open another if you have any new questions.