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

My Subscriptions

Loading

Knowledge Base

Mapping VMware High Availability Heartbeats and Communication Paths (1010991)

Last Updated: 9/8/2020Categories: InformationalTotal Views: 5386Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You may experience these symptoms:

VMware High Availability (HA) shows false alerts

Cannot determine where a HA issue is generating

Resolution

When dealing with a HA problem in a cluster, it is very difficult to tell where the problem is originating.

If several hosts are showing issues, it may be any of the primary hosts which is having a problem, since client (non-primary) hosts do not talk directly to the current primary node. Therefore, the primaries share state communications with the community hosts. This is described as one of the scalability features of HA.

To identify the real primary host, view the following file:

/etc/opt/vmware/aam/vmware-sites

This file maps hostname-to-ID# for the environment

Logging details often show just the ID, not the hostname

Note: The ID is what is noted the /var/log/vmware/aam/procMon/{hostname}_fatal.out* file(s) as the host actually being used for the connections in the LAG and various EVENT statements. Host IDs are evidently the first digit before the / in the parentheses.

The vpxa logs only show the primary node as the connection, but this may not actually be the host which a secondary's communication actually goes to. The idea being to allow HA to distribute the heartbeat load among primaries.

Run the following commands on live systems to view the mapping of the cluster's hosts:

export FT_DIR=/opt/vmware/aam/bin
export FT_DOMAIN=vmware
$FT_DIR/ftcli
fcli> la -l (Shows mapping of the cluster hosts)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

KB
•
如何从群集中移除 vRealize Automation 设备 (2149866)

KB
•
对迁移兼容性错误进行故障排除：设备是参与总线共享的 SCSI 控制器 (1003797)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

VMware ESX Server

Related Versions:

Take Our Survey

Copyright © 2024 VMware, Inc. All rights reserved.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant