Esxi wont connect to vCenter

[Rebelno1]

Hi guys need help from anyone ,

I have remediated my ESXI server ESXI 5.5U3 on HP G8

and now i cant add it to my vCenter

I have network connectivity checked all firewall settings are okay nothing that should be blocking adding the server back to vCenter

i can log into the server directly with the C sharp client

I connected with SSH and i restarted the management agents with services.sh restart still will not add in

tried to add it to another vCenter we have and wont add

so i re installed the 5.5 image thinking the esxi had got corrupted and it worked i added it back to vCenter

now after remediation again it is dropped out of vCenter again  and will not add in

error

Reconnect host

ESXi-455.ce.beavers.com

Cannot contact the specified host

(ESXi-455.ce.beavers.com). 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.)

please help me what could be happening here ,

Thank you in advance

[SavkoorSuhas · Accepted solution]

I had this case, where I was running ESXi 5.5 u3b and trying to connect it to a 5.5 U2/U3 vCenter.

The fix here is, IF, you are using a 5.5 U3b ESXi host, then your vCenter should be 5.5 U3b as well.

VMware KB: Correlating VMware product build numbers to update levels

Use this above KB article and find which release your ESXi build corresponds to. If it is 5.5 U3b, then check what your vCenter Build corresponds to (vCenter > Help > About VMware vSphere)

If ESXi is 5.5U3b and vCenter is not, then upgrade the vCenter to 5.5 U3b

Suhas

[a_p_]

If you updated the host to Update 3b, then this is expected unless your vCenter Server is already running Update 3b too. Please see VMware ESXi 5.5 Update 3b Release Notes for details.

André

[TomHowarth]

Did you upgrade your vCenter server to ESXi5.5 U3 before you updated your host?

[Rebelno1]

Cheers to all for help much appreciated,I opened a ticket with vmware support

they explained this is a known issue explained here in this vmware KB 2140304

thanks to all again for help you were correct in your thinking

First experience a Good one with this Community and vmware support