Monitoring VCenter 6.7 in Nagios XI

[bsanjay]

Hello Team,
We have upgraded from VCenter 6.5 to VCenter 6.7 but after upgrading the check is failing and we are getting below error message.

NOTE - We are sending this checks from VMA

vi-admin@localhost:~> ~/box293_check_vmware.pl --server 10.10.24.128 --check Host_OS_Name_Version
UNKNOWN: Server version unavailable at 'https://10.10.24.128:443/sdk/vimService.wsdl' at /usr/lib/perl5/5.10.0/VMware/VICommon.pm line 734.
vi-admin@localhost:~> ~/box293_check_vmware.pl --server 10.10.24.128 --check vCenter_Name_Version
UNKNOWN: Server version unavailable at 'https://10.10.24.128:443/sdk/vimService.wsdl' at /usr/lib/perl5/5.10.0/VMware/VICommon.pm line 734.
vi-admin@localhost:~> ~/box293_check_vmware.pl --server 10.10.24.128 --check CPU_Usage
UNKNOWN: Server version unavailable at 'https://10.10.24.128:443/sdk/vimService.wsdl' at /usr/lib/perl5/5.10.0/VMware/VICommon.pm line 734.
vi-admin@localhost:~> ~/box293_check_vmware.pl --server 10.10.24.128 --check CPU_Info
UNKNOWN: Server version unavailable at 'https://10.10.24.128:443/sdk/vimService.wsdl' at /usr/lib/perl5/5.10.0/VMware/VICommon.pm line 734.


Best Regards,
BSanay

[cdienger]

Is the file still available after the upgrade? Check from the XI command line:

Code: Select all

curl https://10.10.24.128:443/sdk/vimService.wsdl -v

[bsanjay]

Hi Cdeinger,
Yes, this is accessible. Please find the output of the provided curl command,

bsanjay@nagiosxi:[/tmp]: curl --insecure https://10.10.24.128:443/sdk/vimService.wsdl -v
* About to connect() to 10.10.24.128 port 443 (#0)
* Trying 10.10.24.128...
* Connected to 10.10.24.128 (10.10.24.128) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate:
* subject: C=US,CN=mycv.local
* start date: Mar 15 20:17:18 2020 GMT
* expire date: Mar 10 20:17:17 2030 GMT
* common name: brvc1.ux.corp.local
* issuer: OU=VMware Engineering,O=mycv.local,ST=newyourk,C=US,DC=local,DC=vc,CN=ny
> GET /sdk/vimService.wsdl HTTP/1.1
> User-Agent: curl/7.29.0
> Host: 10.10.24.128
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Mon, 29 Jun 2020 12:43:12 GMT
< Cache-Control: no-cache
< Connection: Keep-Alive
< Content-Type: text/xml; charset=utf-8
< Content-Length: 545
<
<?xml version="1.0" encoding="UTF-8" ?>
<!--
Copyright 2005-2020 VMware, Inc. All rights reserved.
-->
<definitions targetNamespace="urn:vim25Service"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:interface="urn:vim25"
>
<import location="vim.wsdl" namespace="urn:vim25" />
<service name="VimService">
<port binding="interface:VimBinding" name="VimPort">
<soap:address location="https://localhost/sdk/vimService" />
</port>
</service>
</definitions>
* Connection #0 to host 10.10.24.128 left intact


Best Regards,
Sanjay Batkura

[cdienger]

The last version of the VMA is 6.5 which may not be compatible with 6.7 vcenter:

https://blogs.vmware.com/vsphere/2017/0 ... ation.html

You may want to confirm this with the VMWare team and see if there are options.

An alternative to the box293_check_vmware plugin is to run the SDK on the XI side of things and is covered in https://assets.nagios.com/downloads/nag ... ios-XI.pdf.