Using vSphere HA Orchestrated Restart an administrator places the most mission critical VM in the highest priority. After a host failure, the highest priority VM fails to restart while VMs in high priority restart. What would cause this to occur?
A.
There are insufficient cluster resources.
B.
Performance degradation VMs tolerate threshold is at default.
In most vSphere documentation, the word "degraded" is used to mean the same thing as "failed." This is sloppy documentation, since there are some specific topics where they do refer to hosts with certain disk problems running in "degraded mode."
from vsphere 5.1
VM Restart Priority
VM restart priority determines the relative order in which virtual machines are placed on new hosts after a host failure. Such virtual machines are restarted, with the highest priority virtual machines attempted first and continuing to those with lower priority until all virtual machines are restarted or no more cluster resources are available. Note that if vSphere HA fails to power on a high-priority virtual machine, it does proceed to try any lower-priority virtual machines.
so A might be an answer.
The surviving host could not satisfy the resources needed for the highest priority virtual machine. Therefore, vSphere HA proceeded to power on the next lower-priority virtual machine. I believe the correct answer is A.
A is wrong because the low priority VMs are restarting and the high priority VMs are not. If there was a lack of cluster resources, the high priority VMs would start first. The only thing that would cause this behavior is if the high priority VMs in particular had some issue, for example VMware Tools not installed.
The correct answer is C
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.avail.doc/GUID-FA8B166D-A5F5-47D3-840E-68996507A95B.html
(To use the Shutdown and restart VMs setting, you must install VMware Tools in the guest operating system of the virtual machine. Shutting)
The question is WHAT is causing this ?
Since its of highest priority eventhough resource isnt enough, it should be redirected to another host where there enough resources.
So being said Proactive HA aint doing the job as its disable.
Why its in this scenario is beacuse there is not enough resources on the specific host.
Why not “A” - “highest priority VM (naming it vm1) fails to restart while VMs in high priority restart (naming them vm2, vm3)”, it couldn’t be A, because at first place vm1 will restart. But it didn’t. And after that vm2 and vm3 are restarted, so there is no resource problem. Or, at least there is no information about how big are vm’s. But we could assume that if two could start, but one not, there is no resource problem. And there should be alarm before that there is no HA failover resources, etc.
Why not “D” – read this in the question: “After a host failure…”, so there is nothing to do here with Proactive HA, the host already failed.
Why not “B” – because if Performance degradation VMs tolerate threshold is at default, that’s mean that could satisfy the configured failover resources on the cluster. And this is not the cause that vm1 not restarting.
Correct answer “C” – everyone knows that if VMware Tools is not installed, the vm will not failover/restart.
I believe the answer is C. The below information on Orchestrated restart is from the e-Book used for the on-line vSphere class...
Orchestrated restart in vSphere HA enables five tiers for restarting VM and VM-VM dependencies.
Choose from among the following conditions that must be met before a VM is considered ready: • VM has resources secured. • VM is powered on. • VMware Tools heartbeat is detected. • VMware Tools application heartbeat is detected.
Optionally, you can configure a delay when a certain condition is met.
Priority tier: • VMs can be grouped into tiers indicating their startup priority. All VMs in the priority 1 tier receive their resources first and are powered on.
• Only when all the VMs in tier 1 have met their defined restart condition does vSphere HA continue to the VMs in the priority 2 tier, and so on.
"Since the highest priority VM did not meet the resource requirements, how can the other VM's be powered on?"
VMware Tools heartbeat is used to check if the VM 1 position earlier in the chain (e.g. first DB server, than App server) is up and ready, so the next VM can start. The question refers to the highest priority VM, meaning the first VM to be started. So no VM ahead in the queue and no waiting for a VMware Tools heartbeat.
So I believe answer A is correct.
http://virtualvillage.cloud/?p=393
VMs in Highest Priority should be first to Power on, then VMs in the High Priority ,so if the VMs in the High Priority was powered on first ,we can say there is enough resources .
so something not working with the Highest priority configuration!
its could be the "Guest Heartbeat" Not Detected !! so if the Guest Heartbeat not detected -- VM Monitoring not working , and VM Monitoring Need VMware Tools to be installed
I think that the correct answer is " VMware Tools" the reason is HA Orchestrated Restart use VM/Host Rules configurations with VM Monitoring and vM restart service , and thews features required VMware Tools installed on the VMs/
What do you think?
https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-67-availability-guide.pdf
Ir requires sufficient network ports which is part of the cluster resource so its A
Resource reservations Of the hosts that the virtual machine can run on, at least one must have
sufficient unreserved capacity to meet the memory overhead of the virtual
machine and any resource reservations. Four types of reservations are
considered: CPU, Memory, vNIC, and Virtual flash. Also, sufficient network
ports must be available to power on the virtual machine.
Answer is A. Host failed, not enough resources to start the Critical VM, so it goes to the next VMs to restart and they do start because there is enough resources.
Note that if vSphere HA fails to power on a high-priority virtual machine, it does proceed to try any lower-priority virtual machines. Because of this, the VM restart priority cannot be used to enforce a restart priority for a multiple virtual machine application. Also, if the number of hosts failures exceeds what admission control permits, the virtual machines with lower priority might not be restarted until more resources become available. Virtual machines are restarted on the failover hosts, if specified.
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.avail.doc_50%2FGUID-FA8B166D-A5F5-47D3-840E-68996507A95B.html
Correct answer is C
NOTE: This can be accomplished if VMware Tools is installed on the virtual machine and the VM dependency restart condition is set to Guest Heartbeats detected.
Note that if vSphere HA fails to power on a high-priority virtual machine, it does proceed to try any lower-priority virtual machines.
https://www.sikich.com/insight/setting-virtual-machine-start-order-with-vmware-vsphere-6-7-high-availability/
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
jkrug
Highly Voted 5Â years, 7Â months agoJoeTech88
3Â years, 5Â months agozhangle
Highly Voted 5Â years, 4Â months agoKeystroke13
5Â years, 4Â months agoJoeTech88
Most Recent 3Â years, 5Â months agokurohebi
4Â years, 1Â month agosha0007
4Â years, 3Â months agoCokeTheKid
4Â years, 5Â months agosahing
4Â years, 6Â months agostillface
4Â years, 7Â months agotgortva
4Â years, 10Â months agodennis314159
4Â years, 8Â months agoGPunk
4Â years, 10Â months agoRass2
4Â years, 11Â months agoGPunk
5Â years agotristansantiago
5Â years, 1Â month agopinkeshpanchal
5Â years, 2Â months agoStitch2020
5Â years, 3Â months agoJamshid
5Â years, 3Â months agoJamshid
5Â years, 3Â months ago