VMware ESX Error “cmd addnode failed for primary node: Internal AAM error”


KB ID 0000298 Dtd 16/07/10


Seen in a Virtual Center HA environment – even after selecting “Reconfigure for HA” on the ESX host.

Errors: cmd addnode failed for the primary node:Internal AAM error – agent could not start – Unknown HA error. Cannot complete the configuration of the HA agent on the host – See the task details for additional information. Other HA configuration error.

cmd adnode failed



1. How you proceed depends on your infrastructure. If possible, using vMotion/Migrate all the guest machines on this host, to your other ESX hosts. (Note: if that’s no an option you will need to shut down the guest machines).

2. Put the offending ESX host into maintenance mode (Right click it enter select maintenance mode).

3. Assuming you are connected to the Virtual Center, right click the offending host and select “remove”.

cmd adnode

4. Then add it back to the cluster (Right click the cluster and select “Add Host”).

adnode failed error esx

5. HA will be reconfigured on the host as its added back in.


Related Articles, References, Credits, or External Links


Author: Migrated

Share This Post On