Nedienas ar VMWare HA konfigurēšanu, ir risinājumi!

You are experiencing:
  • VMware High Availability (HA) failover errors:

    HA agent on <server> in cluster <cluster> in <datacenter> has an error

    Insufficient resources to satisfy HA failover level on cluster

  • HA agent configuration errors on ESX hosts:
    • Failed to connect to host
    • Failed to install the VirtualCenter agent
    • cmd addnode failed for primary node: Internal AAM Error – agent could not start
    • cmd addnode failed for primary node:/opt/vmware/aam/bin/ft_startup failed

  • Configuration of hosts IP address is inconsistent on host <hostname> address resolved to <IP> and <IP>
  • Port errors:

    Ports not freed after stop_ftbb

  • The first node in the HA cluster enables correctly but the second node fails to configure HA just after 90%.
  • The network settings and HA configuration are all correct. DNS and ping tests are all okay.
  • Disabling and re-enabling HA on the cluster did not resolve the issue.
  •  VMware Infrastructure (VI) Client displays the error:

    Internal AAM Errors – agent could not start

  • In the aam logs on the ESX, the file aam_config_util_addnode.log shows text similar to:

    11/27/09 16:20:49 [myexit ] Failure location:
    11/27/09 16:20:49 [myexit ] function main::myexit called from line 2199
    11/27/09 16:20:49 [myexit ] function main::start_agent called from line 1168
    11/27/09 16:20:49 [myexit ] function main::add_aam_node called from line 171
    11/27/09 16:20:49 [myexit ] VMwareresult=failure
  • Adding a host to the cluster fails with the error:

    Cannot complete the configuration of the HA agent on the host.  Other HA configuration error.


Note: For VMware vCenter Server 5.0  HA/FDM troubleshooting, see Troubleshooting Fault Domain Manager (FDM) issues (2004429).

This article guides you through the process of troubleshooting a VMware HA cluster. The article identifies common configuration problems as well as confirming the availability of required resources on your ESX Server. 

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
Note: If you perform a corrective action in any of the following steps, attempt to reconfigure VMware HA again. Most issues can also be solved by unconfiguring, and then reconfiguring HA again. Ensure you do this action before proceeding with these steps.
  1. Check the release notes for current releases to see if the problem has been resolved in a bug fix.  See the Documentation page for vSphere 4 or VMware Infrastructure 3.

  2. Verify that there are enough licenses to configure VMware HA. For more information, see Verifying that a feature is licensed (1003692).

  3. Verify that name resolution is correctly configured on the ESX Server. For more information, see Identifying issues with and setting up name resolution on ESX Server (1003735).

  4. Verify that name resolution is correctly configured on the vCenter Server. For more information, see Configuring name resolution for VMware VirtualCenter (1003713).

  5. Verify that the time is correct on all ESX Servers with the date command. For more information on setting up time synchronization with ESX Server, see Installing and Configuring NTP on VMware ESX Server (1339).

  6. Verify that network connectivity exists from the VirtualCenter Server to the ESX Server. For more information, see Testing network connectivity with the Ping command (1003486).

  7. Verify that network connectivity exists from the ESX Server to the isolation response address. For more information, see Testing network connectivity with the Ping command (1003486).

  8. Verify that all of the required network ports are open. For more information, see Testing port connectivity with the Telnet command (1003487).


    • HA uses the following ports:

      Incoming port – TCP/UDP 8042-8045
      Outgoing port – TCP/UDP 2050-2250

    • Also, ensure that AAM (Automated Availability Manager) is enabled on the ESX Security Profile. If these ports are not open on the ESX firewall, HA will not configure.

  9. If configured with Advanced Settings, confirm that the configuration is valid. For more information, see Advanced Configuration options for VMware High Availability (1006421).

  10. Verify that the correct version of the VirtualCenter agent service is installed. For more information on determining agent versions and how to manually uninstall and reinstall the HA agents on an ESX host, see Verifying and reinstalling the correct version of VMware VirtualCenter Server agent (1003714).

  11. Verify the VirtualCenter Server Service has been restarted. To restart the VirtualCenter Server Service, see Stopping, starting, or restarting the vCenter Server service (1003895).

  12. Verify that VMware HA is only attempting to configure on one Service Console. For more information, see VMware High Availability configuration issues when an iSCSI Service Console is on the same network (1003789).

  13. Verify that the VMware HA cluster is not corrupted. To do this you need to create another cluster as a test. For more information, see Recreating VMware High Availability Cluster (1003715).

  14. Verify that that UDP 8043 packets used for the HA backbone communications are not dropped between the ESX hosts.  For more information see HA fails to configure after task passes 90% “Internal AAM Error – agent could not start” (1018217).

  15. Ensure that the ESXi host userworld swap option is enabled. For more information see ESXi hosts without swap enabled cannot be added to a VMware High Availability Cluster (1004177).
Notes: If your problem still exists after trying the steps in this article:

Additional Information:
Verify the contents of the /etc/hosts files on the ESX/ESXi host and ensure the IP address of the host in the DNS is the same as the IP address in the hosts configuration file. Also ensure the IP, FQDN and shortname are added to the ESX/ESXi hosts file. For further information see the following KBs.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s