在vSphere 7.0集群上启用HA功能时，VMCP启用失败

  • 2020年10月23日
  • 0回答
  • 3930的浏览量
Riddhima.singh
排名
Userlevel 1
徽章 ＋1

在VMware vCenter中，创建新集群时，默认的HA配置是关闭的:

开立的HA配置集群(集群在库存- >选择“配置”选项卡- > vSphere可用性部分- >“编辑”按钮vSphere公顷)我们可以看到哈是禁用的,响应“PDL数据存储”和“与adp数据存储”是预定义的“关机和重启虚拟机”。

当这个新集群仍然为空时，如果vShere HA从这个配置窗口打开，它会解锁PDL/APD响应的配置部分:

如果在添加主机到集群之前，“Datastore with APD”下的响应没有被修改为“Disabled”，那么，之后当新镜像ESXi主机(with混杂。APDhandlingEnable = 0(由foundation流程设置)加入cluster后，APD响应配置部分被锁定，我们无法将其更改为“禁用”对于独立集群的建议．

导致在此集群上启动HA失败，提示“Cannot enable vSphere HA VM Component Protection for specified cluster, because it contains a host with APD Timeout is disabled.”。

这是由于PDL或PAD条件下，选择了“下电并重启虚拟机”响应，这将需要在集群中的所有ESXi主机上启用APD处理(混杂。APDhandlingEnable = 1）.

这个问题有两种解决方法:

  • 首选—当新建集群时，仍然没有ESXi主机时，可以开启HA，将PDL/APD响应修改为“Disabled”。后续在该集群中添加ESXi主机(APD处理关闭)时，APD响应配置会被锁定为“disabled”，不会阻止集群上开启HA。

  • 如果ESXi主机已经加入集群，此时无法开启HA功能，可以在主机上临时开启APD处理(通过设置混杂。APDHandlingEnable“1，以解锁APD故障的响应配置。在此之后，您可以将HA集群设置中的PDL/APD响应更改为“Disabled”，然后在集群上启用HA。稍后，您将需要禁用主机上的APD处理(通过设置混杂。APDHandlingEnable“0)，以保持在受支持的配置范围内。看到kb - 3328有关如何在ESXi上更改高级参数的说明，并找到有关ncc检查esx_misc_settings_check的更多细节。

  • 更多的细节,https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000brHPCAY


In VMware vCenter, when a new cluster created, the default\u00a0 HA configuration is disabled:<\/span><\/span><\/p>

\u00a0<\/p>

When opening the HA configuration for this cluster (Select cluster in inventory -> \"Configure\" tab -> vSphere Availability section -> \"Edit\" button for vSphere HA) we can see that HA is disabled and the response for \"Datastore with PDL\" and \"Datastore with APD\" is pre-defined as \"Power off and restart VMs\".\u00a0<\/span><\/span><\/p>

\u00a0<\/p>

While this new cluster is still empty, if vShere HA is turned on from this configuration window, it unlocksconfiguration sections for PDL\/APD response:<\/span><\/span><\/p>

\u00a0<\/p>

If the response under \"Datastore with APD\" was not changed to \"Disabled\" before adding host(s) to the cluster then, later when freshly imaged ESXi host(s) (with <\/span>Misc.APDhandlingEnable = 0 <\/span>set by foundation process) are added to cluster, the APD response configuration section is locked and cannot be changed to \"Disabled\" according our <\/span>recommendations for standalone clusters<\/u><\/a>.<\/span><\/span><\/p>

\u00a0<\/p>

As a result, attempting to enable HA on this cluster fails with the following message: \u201cCannot enable vSphere HA VM Component Protection for specified cluster, because it contains a host <name\/IP> with APD Timeout is disabled.\u201d<\/span><\/span><\/p>

This is due to\u00a0 the selected\u00a0 \"Power off and restart VMs\" response for PDL or PAD conditions, which will require APD handling to be enabled on all ESXi hosts in the cluster (<\/span>Misc.APDhandlingEnable =1<\/span>).<\/span><\/span><\/p>

\u00a0<\/p>

There are two workarounds for this issue:<\/span><\/span><\/p>

本主题已关闭供评论
Baidu