VMware vCenter 7 server deployment failing and "no healthy upstream" forever errors

To avoid problems in vCenter 7 installation, use your physical infrastructure DNS and a public NTP server, for example (time.google.com).

Without using this setting, the vCenter services fail to start, and the deployment fails at 67% or more in the starting services progress. 

Even if the deployment succeeds if the appliance restarts, the services will fail to start, and "No healthy uplink" appears forever.

Depending on the time synchronization of the virtual infrastructure may cause the deployment to fail, or the HTLM5 vSphere Web Client error "No healthy upstream", delayed startup, or even failed startup of services. 

vCenter deployment and vSphere Web Client is very sensitive and complicated to the time synchronization. Once we used the physical infrastructure DNS and a Public NTP server (time.google.com) everything ran smoothly, vSphere Web Client started on time. 


Please read this topic in VMware documents "Synchronizing Clocks on the vSphere Network."

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.install.doc/GUID-9FD3A5E3-6C2D-4161-9270-4BF57FADCE6D.html#GUID-9FD3A5E3-6C2D-4161-9270-4BF57FADCE6D

In vCenter 7 is mandatory to use reliable clock synchronization. 






No comments:

Powered by Blogger.