VM migration or power-on fails with "The host is reporting errors in its attempts to provide vSphere HA support" in DMZ clusters

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

• Powering on of virtual machine from vCenter server fails with errors similar to below:

No host is compatible with the virtual machine.
The user specified host is not compatible.
The host is reporting errors in its attempts to provide vSphere HA support.

• Review of var/log/vmware/vpxd/vpxd.log on the vCenter appliance shows "HAErrorsAtDest" wrt to the ESXi host where the affected virtual machine resides:
  
  YYYY-MM-DDThh:mm:ss info vpxd[0#4#3] [Originator@6876 sub=vpxLro opID=mj##7##q-4###49-auto-9guu-h5: 7##52##0-2#-0#] [VpxLRO] -- BEGIN task-1##7##4 -- <VM_NAME> -- Datacenter. ExecuteVmPowerOnLRO --
YYYY-MM-DDThh:mm:ss info vpxd[0#4#3] [Originator@6876 sub=VmCheck opID=mj##7##q-4###49-auto-9guu-h5: 7##52##0-2#-0#] CompatCheck results: (vim.vm. check. Result) [
-->        (vim. vm. check. Result) {
-->            vm = 'vim.VirtualMachine:E2#BF#30-3##4-4##B-9##8-4A##D##AA##E:vm-<vm_moid>'
-->            host = 'vim.HostSystem:E2#BF#30-3##4-4##B-9##8-4A##D##AA##E:host-<host_moid>',
-->            error = (vmodl.MethodFault) [
-->                (vim. fault.HAErrorsAtDest) {
-->                    msg = "",
-->                }
-->            ],
-->        }
-->]
YYYY-MM-DDThh:mm:ss info vpxd[0#4#3] [Originator@6876 sub=cdrsPlmt opID=mj##7##q-4###49-auto-9guu-h5: 7##52##0-2#-0#] Dump section ######## created for cluster [vim.ClusterComputeResource: domain-c<domain_id>, <cluster_name>]
YYYY-MM-DDThh:mm:ss error vpxd[0#4#3] [Originator@6876 sub=vpxLro opID=mj##7##q-4###49-auto-9guu-h5: 7##52##0-2#-0#] [VpxLRO] Unexpected Exception: N3Vim5Fault16NoCompatileHost9ExceptionE(Fault cause: vim.fault.NoCompatibleHost
...
YYYY-MM-DDThh:mm:ss error vpxd[0#4#3] [Originator@6876 sub=Default opID=mj##7##q-4###49-auto-9guu-h5:7##52##0-2#-0#] [VpxLRO] -- ERROR task-1##7##4 -- <VM_NAME> --
Datacenter.ExecuteVmPowerOnLRO: :vim.fault.NoCompatibleHost
--> Result:
--> (vim. fault.NoCompatibleHost) {
-->        faultCause = (vmodl.MethodFault) null,
-->        faultMessage = (vmodl.LocalizableMessage) [
-->            (vmodl. LocalizableMessage) {
-->                key = "com.vmware.cdrs.placeVm.emptyCompatSet",
-->                arg = <unset>,
-->                message = <unset>
-->            }
-->        ],
-->        host = (vim.HostSystem) [
-->            'vim.HostSystem:E2#BF#30-3##4-4##B-9##8-4A##D##AA##E:host-<host_moid>'
-->        ],
-->        error = (vmodl.MethodFault) [
-->            (vim. fault.HAErrorsAtDest) {
-->                faultCause = (vmodl.MethodFault) null,
-->                faultMessage = <unset>
-->                msg = ""
-->            }
-->        ]
-->        msg = ""
--> }
--> Args:
-->
• The same virtual machine can be powered on directly from the ESXi host by using the Host client or Host CLI

Cause

In DMZ environments, the vSphere HA (FDM) agent cannot reach a "Connected" state because bidirectional communication on TCP/UDP port 8182 is restricted between ESXi hosts, or the host cannot reach its isolation address.
The ESXi host where the virtual machine resides is experiencing vSphere HA (FDM) configuration or operational faults. Because vCenter Server cannot validate HA protections (such as VM Monitoring) on the destination host, the compatibility check fails, and vCenter Server blocks the power-on operation.

Resolution

1. Firewall Validation: Ensure TCP and UDP port 8182 is open bidirectionally between all ESXi hosts in the cluster.
2. Connectivity Check: From the ESXi shell, run nc -zv [Destination_IP] 8182 to verify the path.
3. Isolation Check: Ensure the host can vmkping its default gateway or configured isolation addresses.
4. Reconfigure HA: Right-click the affected host in vCenter and select Reconfigure for vSphere HA to re-initialize the agent state.

1. Right-click the affected ESXi host in the vSphere Client inventory.

2. Select Reconfigure for vSphere HA.

3. Monitor the Recent Tasks pane to verify the task completes successfully.

4. Attempt to power on the virtual machine from vCenter Server.

In case issue persists, troubleshoot the cluster for vSphere HA configuration failure by following Troubleshooting VMware High Availability (HA) issues in VMware vCenter Server