Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

VMs become HA unprotected after power-on (66928)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 18190Language:
JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

After upgrading or with a fresh install of vCenter server (6.5.x or 6.7.x version), you might experience an HA error message against VM in the vCenter inventory

ERROR: This virtual machine failed to become vSphere HA Protected and HA may not attempt to restart it after a failure

You may create a VM by anyway, for example but not limited to

- Register a VM from SAN

- Create a new VM from a web client

- Deploy a VM from a template

- Deploy an  OVF

Upon verifying the logs, you could find entries similar to:

fdm.log

2018-12-17T16:34:09.107Z verbose fdm[2155611] [Originator@6876 sub=Invt opID=SWI-2700283f] vm /vmfs/volumes/422c5750-79fe7a4c/testjames2/testjames2.vmx from __localhost__ changed inventory desireProtected=1
2018-12-17T16:34:14.116Z verbose fdm[2155617] [Originator@6876 sub=Invt opID=SWI-6fafb458] vm /vmfs/volumes/422c5750-79fe7a4c/testjames2/testjames2.vmx from __localhost__ changed inventory actualProtected=1
2018-12-17T16:34:14.116Z verbose fdm[2155617] [Originator@6876 sub=PropertyProvider opID=SWI-6fafb458] RecordOp ADD: protectedVm[“/vmfs/volumes/422c5750-79fe7a4c/testjames2/testjames2.vmx”], fdmService. Applied change to temp map

# grep -i  “actual protection state for VM” vpxd.log
2018-12-14T10:06:36.288-08:00 verbose vpxd[29965] [Originator@6876 sub=dasVm opID=jnm1ctvk-871453-auto-iof2-h5:70091269-e0-01-01-01-02-7edf64bd] actual protection state for VM vm-4357 ‘n/a’ -> ‘unprotected’
2018-12-14T10:06:46.790-08:00 verbose vpxd[04231] [Originator@6876 sub=dasVm opID=jnm1ctvk-871526-auto-ioh4-h5:70091308-89-50629fcf] actual protection state for VM vm-4357 ‘unprotected’ -> ‘n/a’
2018-12-14T10:07:01.141-08:00 verbose vpxd[04245] [Originator@6876 sub=dasVm opID=jnm1ctvk-871607-auto-iojc-h5:70091358-a-01-01-01-02-1cba2558] actual protection state for VM vm-4524 ‘n/a’ -> ‘unprotected’
2018-12-14T10:09:00.234-08:00 verbose vpxd[04251] [Originator@6876 sub=dasVm opID=jnm1ctvk-872323-auto-ip39-h5:70091846-9-2c575892] actual protection state for VM vm-4524 ‘unprotected’ -> ‘n/a’
2018-12-14T10:09:48.567-08:00 verbose vpxd[29954] [Originator@6876 sub=dasVm opID=jnm1ctvk-872563-auto-ip9w-h5:70092001-5d-01-01-01-01-7fe98fc7] actual protection state for VM vm-4524 ‘n/a’ -> ‘unprotected’
2018-12-17T08:34:57.517-08:00 verbose vpxd[05830] [Originator@6876 sub=dasVm opID=jnm1ctvk-886926-auto-j0cv-h5:70093018-77-01-01-01-02-86210fc] actual protection state for VM vm-4790 ‘n/a’ -> ‘unprotected’.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

Provide a workaround and cause of some occurrence of an unprotected VM HA error when it is actually protected

Cause

Once a new VM is created and powered on, the protection update is not being propagated to vCenter from FDM Primary Node. This leads to the unprotecting alarm against the VM in vCenter.

The HA error will still be visible in the UI even after VM restarts. However, VMware verified that the underlying HA functionality remained unchanged. That is, the VM was restarted appropriately on another host by HA when the host it was residing on failed.

Impact / Risks

The risk is low as the actual protection state of the VM is correct. The state is not relayed correctly to the VC UI. Also, we have seen this problem only with newly added VMs and not with already existing/protected VMs.

Resolution

The issue is resolved in the ESXi version 6.5 u3 and 6.7 u3 available for download at the VMware Download Page .

Workaround

As a workaround,

Disable and (Re)enable HA

Disabling HA does not affect running virtual machines at all. It does leave them unprotected by HA for the short time until HA is re-enabled.

Note: VMware HA can be disabled only if there are no virtual machines with VMware Fault Tolerance (FT) enabled. If there are virtual machines with VMware FT enabled in the cluster you are disabling, turn off VMware FT before disabling VMware HA.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

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

KB
•
vCenter 报告“主机无法与其他主机通信 (Host cannot communicate with other hosts)”，但从未发生过网络分区 (66984)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

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

VMware vCenter Server 6.5.x

Take Our Survey

Support Assistant