Refer to the exhibit.
An administrator is applying patches to a batch of ESXi 5.x hosts in an under-allocated HA/DRS cluster. An attempt is made to place the host into maintenance mode, but the progress has stalled at 2%. DRS are configured as shown in the exhibit. Of the four choices below, two would effectively resolve this issue.
Which two steps could be taken to correct the problem? (Choose two.)
A.
Manually migrates any running virtual machines to another host
B.
Set the cluster to Fully Automated
C.
Disable HA Monitoring to allow Maintenance Mode to proceed
D.
Set the cluster migration threshold to Aggressive
C is definitively part of the right answer if the
ESX host in a VMware High Availability cluster fails to enter maintenance mode and stops at 2% (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007156)
This is normal behavior for a VMware HA/DRS cluster that is using strict admission control.
Disabling strict admission control (allowing virtual machines to power on even if they violate constraints) should allow a host to enter maintenance mode in this situation. A bug was discovered that would not allow a host to enter maintenance mode even if strict admission control was disabled.
This was resolved in VirtualCenter 2.5 Update 3 and disabling strict admission control should now allow hosts to enter maintenance mode correctly.
To workaround the issue, temporarily disable VMware HA in the cluster settings. You will then be able to put the ESX Server host into Maintence mode and do the work required. You can then re-enable HA on your cluster.
For detailed steps, see VMware High Availability: Concepts, Implementation, and Best Practices.
Note: DRS needs to be enabled on your cluster in Fully Automated mode if you want VirtualCenter to migrate your running virtual machines automatically to other hosts when placing your host in Maintenance Mode.
Fix the answer from D to B. There are couple same questions and the answer is A and C. I was shocked to see A,B here…