cmd addnode failed for secondary node: Internal AAM Error – agent could not start.: Unknown HA error

Sometimes you can get the following error when enabling HA on a ESX 3.5 server.

cmd addnode failed for secondary node: Internal AAM Error – agent could not start.: Unknown HA error

The best way to resolve this problem is to disable both HA and DRS on the cluster.
Then first enable HA on the cluster. Everything should go fine now.
After HA is completly enabled on the cluster enable DRS on the cluster.

Posted in VMWare and tagged , .

4 Comments

  1. Thank you for the information, I’d been all through VmWare’s KB docs…and verified that DNS, Hostname in lowercase, etc. …had all been done. Just by luck stumbled onto your site and YOUR SOLUTION WORKED!!!!

    Kudos and thanks again!!!!

  2. simple really! I too had spent a day on this issue, reading through pages and pages of unhelpful troubleshooting documents. Basically I receieved this error following patching 4 of 8 machines in a vm cluster (incidentally the four machines in error were in HA “secondary” role):

    cmd addnode failed for secondary node: Internal AAM Error – agent could not start.: Unknown HA error

    Your solution to tuen off HA in the cluster properties then turn HA back on again worked a treat…I’m slightly annoyed annoyed i didn’t try this out sooner!

    So…

    Thanks for the top tip

  3. Good site! I truly love how it is simple on my eyes and the data are well written. I am wondering how I might be notified whenever a new post has been made. I have subscribed to your RSS feed which must do the trick! Have a nice day!

Leave a Reply