Clustering servers in a VMware environment
I want to set up two servers in one VMware cluster, but one of the servers has a problem. I keep receiving an error that states, “cmd addnode failed for primary node: Internal AAM Error.” As a result, the agent will not start. Can you please advise a course of action?

Software/Hardware used:
ASKED: December 9, 2008  7:38 PM
UPDATED: December 9, 2008  7:53 PM

Answer Wiki:
<i>This answer comes courtesy of virtualization expert Rick Vanover:</i> Adding servers to a VMware Infrastructure 3 (VI3) cluster is usually a non-event. In the case of certain functions not working correctly for unexplained reasons, we can employ a few approaches correct the problem. First thing, check domain name system (DNS). VMware HA, as well as all ESX to vCenter communication, is extremely dependent on accurate name resolution. One configuration that has caused problems for me is not getting all relevant DNS suffixes or DNS servers listed on the configuration of the host. If that still doesn't work, you should consider rebuilding the host. This could be reinstalling ESX, or taking it out and putting another host in to see if the cluster can function with a different host. On <a href="http://communities.vmware.com/index.jspa">VMware communities</a>, there also are some comments about host names that are extremely long. So in the interest of testing, keep the host name less than 13 characters or so in order to be safe.
Last Wiki Answer Submitted:  December 9, 2008  7:47 pm  by  SearchServerVirtualization ATE   385 pts.
All Answer Wiki Contributors:  SearchServerVirtualization ATE   385 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _