Knowledge Base

Failed HA configuration when adding vSphere host to cluster

Posted by Brian on May 11, 2010 in Knowledge Base, Troubleshooting, VMware, vCenter Server, vSphere | View Comments

Recently while setting up a new cluster on vSphere I had an issue with adding one of the hosts to the cluster. It would fail the HA configuration piece each time I would try. The host would join the cluster but HA would have a Red alarm for its failure. Nothing seemed to be wrong with the host, hardware or configuration. I would get the error listed below on each attempt.

cmd addnode failed for primary node: Internal AAM Error agent could not start

I found the following VMware KB article to help troubleshoot these types of errors. My issue ended up being an issue with the cluster that was created. I created a new cluster and moved my ESX Hosts and Virtual Machines over to it and the issue was gone. Before trying this route I had examined several of the options listed in the KB article.

Windows 7 Virtual machines or tools stop responding

Posted by admin on Feb 21, 2010 in Knowledge Base, VMware | View Comments

This is something that I had encountered when testing VM’s in our PoC for XenDesktop recently.  We could come back after a few hours and find the VM in a hung state or in sleep mode. The sleep mode symptom was a obvious sign of were to start looking. After playing with the power settings a few times and turning off all of the options the issues went away.

According to a new KB article from VMware this is more of a common problem. Stop by here for the original document.