When you encounter no healthy upstream error, it means that the vCenter is not up and ready yet. Just wait a few minutes before connecting to vCenter via a web browser.
But every no healthy upstream error is not finished with unprepared vCenter. There might be some issue which does not allow the services of vCenter to be running properly.
Fix vCenter 7 no healthy upstream error?
There is another guide to help you fix no healthy upstream error of vCenter 7. It might be occurred after upgrading vCenter 6.7 to vCenter 7.
- Shutdown the vCenter
- Upgrade the VM hardware version
- Edit settings > VM Options > General Options > Select VMware Photon OS
Note: make sure you have allocated enough memory and CPU for the vCenter 7 virtual machine. The vCenter 7 is CPU and memory hungry.
Read the related community post on vMware forum.
It’s a nasty error that won’t be fixed by a fresh installation of vCenter7. I’m still trying to find the main cause of this error in vCenter 7.
Related article: Setup a Penetration Testing Lab.
Hardware Requirements for the vCenter Server Appliance
When you deploy the vCenter Server appliance, you can select to deploy an appliance that is suitable for the size of your vSphere environment. The option that you select determines the number of CPUs and the amount of memory for the appliance. The hardware requirements for a vCenter Server appliance depend on the size of your vSphere inventory.
The upgrade of the appliance is a migration of the old version to the new version, which includes deploying a new appliance of version 7.0. You can deploy the new vCenter Server appliance on an ESXi host 6.5 or later, or on a vCenter Server instance 6.5 or later. Your system must also meet specific software and hardware requirements.
Hardware Requirements for a vCenter Server Appliance
|Number of vCPUs||Memory|
|Tiny environment (up to 10 hosts or 100 virtual machines)||2||12 GB|
|Small environment (up to 100 hosts or 1,000 virtual machines)||4||19 GB|
|Medium environment (up to 400 hosts or 4,000 virtual machine)||8||28 GB|
|Large environment (up to 1,000 hosts or 10,000 virtual machines)||16||37 GB|
|X-Large environment (up to 2,500 hosts or 45,000 virtual machines)||24||56 GB|
Note: If you want to add an ESXi host with more than 512 LUNs and 2,048 paths to the vCenter Server inventory, you must deploy a vCenter Server appliance for a large or x-large environment.