Cluster DRS - Advanced Rules

[Velli]

Hello people!

The truth is that I did not know where to look and ask, but thanks to William Lam have met this community.

I'm work a project on VMware vSphere and ESXi 5.5. I've added a DRS cluster and I've added some basic rules. I need to go beyond that.
I would like to know some advanced rules for a DRS cluster. The one that interests me most is that a virtual machine can move from one host to another when the CPU reaches a perfomance of 30%.

Thank you very much for attention. I hope you can help me.

[zXi_Gamer]

One thing, I can immediately think of is setting an alarm or customizing an existing HostCPU alarm.

Under DRS,Alarms,  you can find a definition for Host CPU Usage. You can either create a new alarm based on Host CPU usage and set the threshold of CPU to 30% and set the action item as Move into maintenance mode. If DRS is configured, this would make the migrations of the VM to other hosts.

But it would also impact the other VMS in the host.

I will post more data, if you require, as I am running late

Oh and welcome to the communities.

[Velli]

Thank you very much for the reply and the welcome. It's my pleasure.

In effect, the message "Host cpu usage" always appears. But, apparently not give me more trouble.

About the option that I am telling you, I'll attach a picture so you can see it.

In this section, I'd add the options I mentioned above.

Virtual machines are migrated should reach 30% CPU or 40% Memory, etc. this is an example.

Thank you again, I need this to work!

[vThinkBeyondVM]

Hi Friend,

Below are the advanced options that DRS have that can be configured from the screen shot that you have given above::

• CostBenefit
• UseDownTime
• IgnoreDownTimeLessThan
• MinImbalance
• MinGoodness
• MaxMovesPerHost

Refer : DRS performance Tuning section from below PDF to get all the details on all DRS advanced settings.

http://www.vmware.com/pdf/Perf_Best_Practices_vSphere5.1.pdf

Note: You need to specify advanced option and its value. However, it is not recommended to change DRS default settings until it is really required. Also we should be very clear on the impact that custom setting can have on DRS. DRS does not migrate the VMs the way that you want based on CPU % 30-40.etc. Read : DRS Deepdive - Yellow Bricks.

Yes, Alarm itself can not take any action for you. It just alarm you to take action.

Can you please me to the resource where you got :when the CPU reaches aperfomance of 30%. etc..

For configuring DRS : Refer:

http://pubs.vmware.com/vsphere-55/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-55-resourc...

Let me know if you need any other details.

[Velli]

Thanks for all the info!

I have reviewed all the documentation, but don't understand the exact option that I should add for the machines are migrated using 30% of CPU.

[zXi_Gamer]

I have reviewed all the documentation, but don't understand the exact option that I should add for the machines are migrated using 30% of CPU.

Hey there,

                What myself and @vickyvision2020 are trying to put is that in advanced options of DRS cluster which you have pointed out, you can have only the settings which vickyvision2020  has mentioned.

• CostBenefit
• UseDownTime
• IgnoreDownTimeLessThan
• MinImbalance
• MinGoodness
• MaxMovesPerHost

To have your requirement, you need to set an alarm in the VC to focus on Host CPU usage which will then migrate the VMS by putting the host in maintenance mode

Create DRS and DPM Alarms

[zXi_Gamer]

Or one more method which I could think of is by running a powercli script when the Host CPU reaches 30%, which triggers migration of the VMS instead of putting the host to maintenance mode.

Please let me know.