Home » VMware » VCP550D » What condition could result in this behavior?
An organization has a HA/DRS cluster containing a mixture of ESXi 4.1 and 5.5 hosts in the cluster. An ESXi 5.5 host has failed and HA attempted but failed to restart the virtual machines on another host. HA admission control is disabled.
What condition could result in this behavior?
A. A virtual machine has an incompatible hardware version
B. Insufficient resources exist on the remaining ESXi hosts
C. vMotion migration is not supported between ESXi 5.5 and 4.1 hosts
D. HA failover is not supported between ESXi 5.5 and 4.1 hosts
Correct Answer: A
Explanation/Reference:
Explanation:
A: High Availability and consequently fault tolerance on virtual machines in a cluster can only be effected when the virtual machines on the cluster has compatible hardware versions. Any mismatch and fault tolerance cannot be maintained. Thus if HA failed to restart the virtual machines on another host when the host in question (in the cluster) failed, then it can be because there is no matching/no compatible virtual machine.
Incorrect Answers:
B: It is mentioned that this is a DRS cluster and the purpose of DRS clusters is to balance the workload with regard to resources. Thus failure of a virtual machine restart in a case where one of the hosts in the cluster has failed is not due to insufficient resources in the cluster.
C: vMotion can be effected between ESXi 5.5 and 4.1 hosts and thus this failure to restart the virtual machines on another host in the cluster is not a vMotion issue.
D: HA failover is supported between ESXi 5.5 and 4.1 hosts when making use of Tech Support Mode.
References:
https://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp#com.vmware.vsphere.availability.doc_40_u1/c_createha_param_admctrl_hostfail.html
