Select Page

VMware NSX Installation Cluster Status ‘Not Ready’

While preparing a NSX Installation Series I have come across a lot of issues during the setup process. The majority of the issues were caused by vSphere Certificates that have not registered correctly with services.

The error I was receiving was the below, this was found in the following log file on my vCenter server – D:\ProgramData\VMware\vCenterServer\logs\eam\eam.log – This is the ESX Agent Manager Service.

Failed to login to vCenter as extension. vCenter has probably not loaded the EAM extension.xml yet.: Cannot complete login due to an incorrect user name or password.

I come across this VMware KB ( that references this issue so I thought I would create a guide on how to resolve this issue.

You will need to login to your vCenter server and follow the below steps –

Create a C:\certificate directory on the vCenter server.

Run the following commands to retrieve the VPXD-EXTENSION Solution user certificate and key –

“%VMWARE_CIS_HOME%”\vmafdd\vecs-cli entry getcert –store vpxd-extension –alias vpxd-extension –output c:\certificate\vpxd-extension.crt

“%VMWARE_CIS_HOME%”\vmafdd\vecs-cli entry getkey –store vpxd-extension –alias vpxd-extension –output c:\certificate\vpxd-extension.key

Navigate to C:\Program Files\VMware\vCenter Server\vpxd\scripts

In my example I have installed vCenter on the D:\ Drive so I have to navigate to D:\Program Files\VMware\vCenter Server\vpxd\scripts

We now need to update the extensions certificate using this command as below –

“%VMWARE_PYTHON_BIN%” -e com.vmware.vim.eam -c C:\Certificate\vpxd-extension.crt -k C:\Certificate\vpxd-extension.key -s localhost -u [email protected]

You will need to modify the domain if you have used a different domain name to the default vsphere.local domain. You will now need to enter the password for the [email protected] account.

You will now need to restart the VMware ESX Manager service by navigating to the below directory –

D:\Program Files\VMware\vCenter Server\bin

Restart the service using these commands –

service-control –stop EsxAgentManager

service-control –start EsxAgentManager

You will now be able to prepare the clusters as you can see below!

NSX Cluster Installation Status - VMware NSX Installation Cluster Status 'Not Ready'

Pin It on Pinterest

Share This