The load is high on a HA/DRS cluster. DPM is enabled. A vSphere administrator determines that
hosts are NOT powering on automatically to support the load.
Which configuration would result in this condition?
A.
VM-to-VM or VM-to-Host DRS rules have been configured that restrict where some VMs can be
moved.
B.
DPM has been set to the most Conservative threshold.
C.
Some of the virtual machines have been removed from HA consideration by the vSphere
administrator.
D.
DRS is set to Manual Automation.
Explanation:
D is correct
Host power operation and related virtual machine migration recommendations are made, but not automatically executed
http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.resmgmt.doc/GUID-6432FD4E-3D86-4878-912F-7545DA87E281.html
0
0
That link confirms “The power management automation level is not the same as the DRS automation level” D is for DRS, not DPM.
Therefore isn’t the answer B? DPM has been set to the most Conservative threshold… so only Priority 1 recommendations based on HA requirements and/or user-specified capacity requirements.
http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.resmgmt.doc_50%2FGUID-3B63E956-D1BD-4F31-B28A-F126ADA011D3.html
http://blog.solori.net/2009/07/24/in-the-lab-vsphere-dpm-quirky-but-functional/
0
0
DPM only kicks in when DRS is active (in automated mode)!
Note: VM should vMotion/Storage vMotion first(!) before a Host can be shutdown AND a Host should be awakened before VM can land on that Host. DRS is takes care of vMotion, DPM only works on Hosts NOT VM’s.
DRS:
http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.resmgmt.doc/GUID-23A2BE80-BCE2-49D7-902E-F7B8FDD8F5F8.html
DPM:
http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.resmgmt.doc/GUID-3B63E956-D1BD-4F31-B28A-F126ADA011D3.html
Host-Level overrides can be set:
http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.resmgmt.doc/GUID-B74D8872-1E2C-493F-8A89-E6B92D2DF24C.html
0
0
If DRS is set to Manual DPM will never kick in (it has nothing to do), right? That’s why D is the correct answer.
0
0
Why A is not correct?
0
0
It doesn’t say that _any_ vm’s can’t be moved, only some. Therefore the ones that aren’t bound to specific hosts could be still moved and load distributed more evenly.
0
0
I think this question is misleading because a host is the physical server running vSphere which isnt affected by DRS. If it said VMs I would have picked DRS with no question.
0
0
https://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp#using_drs_clusters_to_manage_resources/c_threshold.html
DPM and DRS thresholds re independent of each other.
0
0
Playing by VMware picky semantics rules, there’s simply no such setting for DRS as “Manual Automation” (note – both start with a capital letter, thus implying there must be such an item in vSphere client). Also, going by common sense, automation cannot be “manual” 😉
This leaves us with either A or B.
0
0
B.
0
0
http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.resmgmt.doc/GUID-5E5E349A-4644-4C9C-B434-1C0243EBDC80.html
“vSphere DPM monitors the cumulative demand of all virtual machines in the cluster for memory and CPU resources and compares this to the total available resource capacity of all hosts in the cluster. If sufficient excess capacity is found, vSphere DPM places one or more hosts in standby mode and powers them off after migrating their virtual machines to other hosts. Conversely, when capacity is deemed to be inadequate, DRS brings hosts out of standby mode (powers them on) and uses vMotion to migrate virtual machines to them.”
This confirms that DRS resumes hosts, not DPM. Then the following post confirms that DRS has to be configured in Fully Automated mode in order for this mechanism to work correctly:
http://www.vhersey.com/2011/08/setting-up-dpm-and-using-vcenter-scheduled-task-to-turn-dpm-off-and-on/
In conclusion: the answer is D.
0
0
DPMは、DRSがautoで有効になってるときのみ作動する
0
0
plural design
http://www.XquielQMVW.com/XquielQMVW
0
0