ANSASERVERS
Contributor
Contributor

ESXI 6.5 and Vcenter 6.7

Hey Guys,

I was hoping that someone on here would be able to point me in the right direction. I am having major issues getting two servers to connect to our vcenter server. We keep getting this dreaded error message which makes no sense:

"Cannot contact the specified host (10.17.101.114). The host may not be available on the network, a network configuration problem may exist, or the management services on this host may not be responding."

I can confirm that both esxi servers can resolve the dns name of the vcentre server as well as the ip addresses and the gateways

One hyper visor is running 6.5.0 Update 2 (Build 8294253) and the other one is running 6.5.0 Update 1 (Build 7388607)

We where running Vcenter 6.5 but hypervisor 6.5.0 Update 1 (Build 7388607) lost connection after an update pushed out via vcenter and we decided we would attempt to upgrade

Here is what i have checked

- All Servers have internet access

- All servers can ping vcenter server

- All servers can resolve domain names on the internal network

- All servers have the correct time and date

- All Services appear to be started and working

0 Kudos
5 Replies
a_p_
Leadership
Leadership

Although ESXi 6.5 is not listed under Related Versions, it may be worth checking https://kb.vmware.com/s/article/1005803

André

0 Kudos
ANSASERVERS
Contributor
Contributor

HI Mate,

Thanks for your reply. I have looked at this article but it does not seem to be the issue. I am now getting a new error within the log file:

2018-09-26T15:53:18.460Z error vpxd[04422] [Originator@6876 sub=HostAccess opID=3d052086-8d57-4cf4-b85c-71b1e3481dcc-3344-auto-3345-h5c:70001790-8f] Failed to discover version: N3Vim5Fault9HttpFault9ExceptionE(Fault cause: vim.fault.HttpFault

--> )

--> [context]zKq7AVECAAAAAEvzjwAXdnB4ZAAAMJwqbGlidm1hY29yZS5zbwAAUC4bAJ6yGAGbN4V2cHhkAAFjOIUBR7mDAVm8gwERwYMB+3hyAYCacgEGo3IBok16AehYegJykP9saWJ2aW0tdHlwZXMuc28AAVVvcAH6c28BW4FvAfjbbwA9CiMABg0jAOHzKgPUcwBsaWJwdGhyZWFkLnNvLjAABL2LDmxpYmMuc28uNgA=[/context]

2018-09-26T15:53:18.463Z info vpxd[04422] [Originator@6876 sub=vpxLro opID=3d052086-8d57-4cf4-b85c-71b1e3481dcc-3344-auto-3345-h5c:70001790-8f] [VpxLRO] -- FINISH lro-243943

2018-09-26T15:53:18.463Z info vpxd[04422] [Originator@6876 sub=Default opID=3d052086-8d57-4cf4-b85c-71b1e3481dcc-3344-auto-3345-h5c:70001790-8f] [VpxLRO] -- ERROR lro-243943 -- datacenter-81 -- vim.Datacenter.queryConnectionInfo: vim.fault.NoHost:

--> Result:

--> (vim.fault.NoHost) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultMessage = <unset>,

-->    name = "10.17.101.41"

-->    msg = ""

--> }

--> Args:

-->

--> Arg hostname:

--> "10.17.101.41"

--> Arg port:

--> -1

--> Arg username:

--> "root"

--> Arg password:

--> (not shown)

-->

--> Arg sslThumbprint:

-->

2018-09-26T15:53:19.407Z info vpxd[04444] [Originator@6876 sub=vpxLro opID=sps-Main-571308-523-f] [VpxLRO] -- BEGIN lro-244014 -- AuthorizationManager -- vim.AuthorizationManager.hasPrivilegeOnEntities -- 52135eab-6d69-39d0-7117-32a3236b150e(528a2d65-e59b-65fc-c37a-8c41aff06bd1)

0 Kudos

Are you able to login to the affected ESXi servers directly?

On esxi host,check /etc/opt/init.d/vmware-vpxa , and restart this service.

Blog: https://rickverstegen84.wordpress.com/ Twitter: https://twitter.com/verstegenrick
0 Kudos
ANSASERVERS
Contributor
Contributor

The service is running, i restarted it and it has made no effect. Please see the screenshot:Screenshot - 577e8980611b3d1ed404cb379a5e2df1 - Gyazo

0 Kudos
ANSASERVERS
Contributor
Contributor

Does anyone else have idea?

0 Kudos