Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Troubleshooting VMware High Availability (HA) in VMware vSphere 4.x (1001596)

Last Updated: 9/24/2016Categories: TroubleshootingTotal Views: 397779Language:
Chinese (Simplified)JapaneseSpanishEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

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 successful

Disabling and re-enabling HA on the cluster does not resolve the issue

VMware Infrastructure (VI) Client displays the error:

Internal AAM Errors - agent could not start

In the aam_config_util_addnode.log file on the ESX, you see entries similar to:

[myexit ] Failure location:
[myexit ] function main::myexit called from line 2199
[myexit ] function main::start_agent called from line 1168
[myexit ] function main::add_aam_node called from line 171
[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.

Solution

This article guides you through the process of troubleshooting a VMware HA cluster. The article identifies common configuration problems and also confirms the availability of required resources on your ESXi host.

Note: For troubleshooting steps specific to VMware vCenter Server 5.x HA/FDM, see Troubleshooting VMware High Availability (HA) issues in VMware vCenter Server 5.x and 6.0 (2004429).

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, 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. Do not skip a step.

Most issues can also be solved by disabling HA and then re-enabling it. Ensure to do this before proceeding with these steps.

Note: If you perform a corrective action in any of these steps, attempt to re-enable VMware HA again.

Check the release notes for current releases to see if the problem has been resolved in a bug fix. For more information, see VMware vSphere4 Documentation or VMware Infrastructure 3 Documentation.

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

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

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

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 an ESX host (1339).

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).

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).

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

Notes:

HA uses these ports:

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

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

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

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 the vCenter Server agents (1003714).

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

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).

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 a VMware High Availability Cluster in vSphere (1003715).

Verify that UDP 8043 packets used for the HA backbone communications are not dropped among the ESX hosts. For more information, see HA fails to configure at 90% completion with the error: Internal AAM Error - agent could not start (1018217).

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).

Note: If your problem still exists after trying the steps in this article:

Gather the VMware Support Script Data. For more information, see Collecting diagnostic information for VMware products (1008524).

File a support request with VMware Support and note this Knowledge Base article ID in the problem description. For more information, see How to Submit a Support Request.

Additional Information

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

Troubleshooting the VMware High Availability error: Unable to contact the primary host in a cluster (1004633)

VMware HA fails with the error: AAM Agent did not start (1004965)

For translated versions of this article, see:

Español: Solucionando problemas en VMware Alta Disponibilidad (HA) - High Availability (1034620)

简体中文: 在 vSphere 中对 VMware High Availability (HA) 进行故障排除 (2061954)

日本語: vSphere での vSphere High Availability（HA）のトラブルシューティング (2078889)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESXi 5.0 へアップグレードするときのベストプラクティス (2005102)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant