Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

Error:"host has unknown health state", upon enabling proactive HA. (75123)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 8645Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

After enabling proactive HA, you will witness an error against all the hosts on the cluster:<host-fqdn> has an unknown health state, with an alert against the each host in a cluster.

Cause

This is not a VMware problem and this issue will appear when an HPE host has been registered with IP address instead of a FQDN. Except for proactive HA, all other functionality will be working as expected. Also, this unknown health state is a very general symptom and could have various causes.

Note: HPE is just an example, where we have noticed a higher number number of cases. This  problem may be seen from other hardware vendors as well. You may need to contact those vendors for more information.

Resolution

To solve the problem perform the below steps. Disable HPE Proactive from vCenter cluster:

Power-off HPE oneview appliance.

Unregister the appliance from vCenter MOB.

To unregister the appliance follow below steps:

Log in to vcenter MOB

select ‘content’

HealthUpdateManager

QueryProviderList

Invoke Method  --> you will get a string,  copy the string .

Go back to HealthUpdateManager tab, select UnregisterHealthUpdateProvider, input above-copied the string from step 3, select invoke method.

After successful unregister of HPE appliance, start HPE appliance and configure with vCenter with FQDN, do  register with FQDN.

After successful HPE registration Health status of the host in vCenter should be OK, all the status in the proactive HA will be green.

vCenter or ESXi will not update the logs during this time, check the hardware monitoring appliance logs. HPE refers to this as OV4VC aka HPE oneview.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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)

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 vCenter Server

Related Versions:

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant