Error occurred while communicating with EsxAgentManager :vCenter shows error after vCenter Certificate Renewal.

 

PROBLEM:

"vCenter Network and Security" shows error "Error occurred while communicating with EsxAgentManager". EAM Status Showing "Starting". NSX manager Communication fails.

REASON:

This issue mostly occurs whenever vCenter Certificates has expired and renewed by administrator.

SOLUTION:

Update the "ESX Agent Manager extension Certificate (EAM)" with current "vpxd-extension" certificate by following below steps.

For Windows Based vCenter

1. Create a folder "c:\certificate".

2. Run below commands in "cmd" to retrieve the vpxd-extension certificate.

"%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

3. Execute "cd C:\Program Files\VMware\vCenter Server\vpxd\scripts" in "CMD".

4. Run below command to update the "EAM extension Certificate"

"%VMWARE_PYTHON_BIN%" updateExtensionCertInVC.py -e com.vmware.vim.eam -c C:\Certificate\vpxd-extension.crt -k C:\Certificate\vpxd-extension.key -s <PNID/FQDN of vCenter Server> -u Administrator@vsphere.local

5. Restart the Esx Agent Manager (EAM) Service

service-control --stop vmware-eam

service-control --start vmware-eam

For vCenter Appliance:

1. shell.set --enabled true

2. Create a directory by running command "mkdir /certificate"

3.  Run below commands to retrieve the vpxd-extension certificate.

/usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store vpxd-extension --alias vpxd-extension --output /certificate/vpxd-extension.crt

/usr/lib/vmware-vmafd/bin/vecs-cli entry getkey --store vpxd-extension --alias vpxd-extension --output /certificate/vpxd-extension.key

4. Run below command to update the "EAM extension Certificate"

python /usr/lib/vmware-vpx/scripts/updateExtensionCertInVC.py -e com.vmware.vim.eam -c /certificate/vpxd-extension.crt -k /certificate/vpxd-extension.key -s <FQDN of vCenter Server> -u Administrator@vsphere.local

5. Restart the Esx Agent Manager (EAM) Service

service-control --stop vmware-eam

service-control --start vmware-eam

vCenter 6.7 : Unable to extend Datastore, Free space is not showing while Increase datastore Capacity

Problem:

In vCenter 6.7 Unable to Increase the Datastore Size. LUN is extended from SAN side, but free space is not reflecting while Increase Datastore Capacity.

Reason:

The feature called "Storage Filtering" is preventing the Increase datastore Capacity operation from Vcenter Console. This feature is using to prevent corruption in VMFS datastore.

Unable to Extend the VMFS from vCenter

Solution:

Login to ESXi Host Management interface and Extend the VMFS datastore directly from ESXi. Once extended from ESXi, rescan storage from vCenter console.

Extend VMFS Datastore from ESXi GUI

Note: In Multi Node Cluster, if one ESXi is not shoing the available space, try to extend from another ESXi Host. It is normal behavior sometimes some of the host will not show the available free space. Also try to re-scan the storage adapter from vCenter console by choosing individual host.

vCenter 6.7 Error "java.lang.reflect.InvocationTargetException" While joining AD

Symptom:

Unable to join VMware vCenter 6.7 in to AD domain. While attempting, it showing error "java.lang.reflect.InvocationTargetException"

Reason:

This is known Behaviors mostly seen in vCenter with External Platform Service Controller in HA Mode.

Solution:

Join vCenter to AD using Command Line.

1. Connect vCenter Server Appliance with SSH. (Login to PSC Appliance in case of External PSC)

2. Type "shell" to go to shell prompt.

3. Execute  "/opt/likewise/bin/domainjoin-cli join [domain] [user name]"

    Example: /opt/likewise/bin/domainjoin-cli join mylab.com labadmin"

4. Enter the password of the AD user you specified in the command.

5. Reboot the Appliance with command "reboot"

6. Login again via ssh and verify AD join status with below command.

    /opt/likewise/bin/domainjoin-cli query