VMware Cloud Community
AlexMo85
Contributor
Contributor
Jump to solution

Add host ESX5.5 to VCENTER 5.5 get error

Hi,

I have an error message when I try to add a host (an ESXi 5.5) to Vcenter (5.5) ...

There are already 2 ESXs on this Vcenter but this third that I just installed is rejected by vcenter

Error message :

Call "Datacenter.QueryConnectionInfo" for the "NAME" object on vCenter Server "vCenter.DOMAIN.LC" failed.

I can connect with the web client directly on my new ESX with IP address...

it seems to be a problem with https connection but i don't know why 

vpxd.log :

2017-04-24T11:00:58.000+02:00 [05596 error 'HttpConnectionPool-000001'] [ConnectComplete] Connect failed to <cs p:000000000cb601e0, TCP:192.168.3.11:443>; cnx: (null), error: class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read)

2017-04-24T11:00:58.000+02:00 [07500 error 'httphttpUtil' opID=1ce49111] [HttpUtil::ExecuteRequest] Error in sending request - SSL Exception: error:140000DB:SSL routines:SSL routines:short read

2017-04-24T11:00:58.000+02:00 [07500 error 'vpxdvpxdHostAccess' opID=1ce49111] [VpxdHostAccess::Connect] Failed to discover version: vim.fault.HttpFault

2017-04-24T11:00:58.014+02:00 [07500 info 'commonvpxLro' opID=1ce49111] [VpxLRO] -- FINISH task-internal-247026 -- datacenter-2 -- vim.Datacenter.queryConnectionInfo --

2017-04-24T11:00:58.014+02:00 [07500 info 'Default' opID=1ce49111] [VpxLRO] -- ERROR task-internal-247026 -- datacenter-2 -- vim.Datacenter.queryConnectionInfo: vim.fault.NoHost:

--> Result:

--> (vim.fault.NoHost) {

-->    dynamicType = <unset>,

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

-->    name = "192.168.3.11",

-->    msg = "",

--> }

--> Args:

-->

Would you have any idea to solve this problem?

thanks

1 Solution

Accepted Solutions
rcporto
Leadership
Leadership
Jump to solution

Can you tell us the exact build number of your vCenter Server and the ESXi host that you just installed? If your host are running version 5.5 Update 3b or later, your vCenter must be running version 5.5 Update 3b too, see: ESXi 5.5 Update 3b and later hosts are not manageable after an upgrade (2140304) | VMware KB

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

2 Replies
rcporto
Leadership
Leadership
Jump to solution

Can you tell us the exact build number of your vCenter Server and the ESXi host that you just installed? If your host are running version 5.5 Update 3b or later, your vCenter must be running version 5.5 Update 3b too, see: ESXi 5.5 Update 3b and later hosts are not manageable after an upgrade (2140304) | VMware KB

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
AlexMo85
Contributor
Contributor
Jump to solution

Thank you for your reply. It seems you're right Smiley Happy

Vcenter : 5.5.0 Build 2183111

ESXi 5.5 U3

So I will try with the 5.5 U2 as my other ESX ...

Thanks a lot

0 Kudos