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

vSphere HA VMCP Settings (PDL Level & APD level) in VM Overrides may adjust to disabled after VC restart (77070)

Last Updated: 7/17/2020Categories: TroubleshootingTotal Views: 11657Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

VM Component Protection (VMCP) may not failover specific virtual machines if a VM Override is configured. If an override is customized outside of the cluster configuration for DRS automation, vSphere HA restart, Isolation Response, vCenter may override the following settings as well:

PDL protection - Disabled

APD Protection - Disabled

If a failover has occurred, you may see log messages similar to below on the Primary  HA host:

2020-04-01T02:22:41.185Z info fdm[4623477] [Originator@6226 sub=Policy opID=SWI-7akjdsu8] PDL reaction is disabled for VM /vmfs/volumes/<Datastore>/VM_Failover_Me/VM_Failover_Me.vmx. Ignore the failure.

Found in log file: /var/run/log/fdm.log

Cause

This is a known issue within vCenter Server, and the PDL/APD protection can revert to Dsabled if one of the following actions is performed:

Add a Virtual Machine in VM Overrides, however perform no customization and saving any properties.

Add a Virtual Machine in VM Overrides and editing only one property, leaving other properties unset.

Deploy NSX Edge Appliance in vSphere HA cluster. (NSX Manager configures VM Overrides Setting automatically when NSX Edge appliance is deployed in vSphere HA cluster)

The APD/PDL protection settings will reset to Disabled after vCenter Server is restarted.

Impact / Risks

This can impact vSphere HA's response in the event of an All Paths Down (APD) or Permanent Device Loss (PDL) event occurs. This can reduce the number of virtual machines to failover.

Resolution

This issue is resolved in VMware vCenter Server 6.7 Update 3g

Note: It is advised after updating vCenter Server to review existing override settings. The fix will not retro-actively cleanup any VM Override settings that already changed to disabled.

Workaround

To workaround this issue , in case if VC will restart, edit and save all properties in VM Overrides settings of VM once before the restart.

In the vSphere Web Client, browse to the vSphere HA cluster.
1. Click the Configure tab.
2. Click VM Overrides and Select a VM.
3. Click Edit, and go to vSphere HA VM Overrides settings.

If the VM Restart Priority is high , make sure to check the VM Overrides box in vSphere HA - PDL protection level Settings and/or vSphere HA - APD protection level Settings too

4. Click Finish.

Related Information

Customize an Individual Virtual Machine - VM Override
VM Component Protection

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)

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

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant