WBrowning
VMware Employee
VMware Employee

You have a good setup and looks like it would work well.

I would reiterate the "perfect world" reference and say I tend to recommend to my customers that vMotion be seperated out if resources allow.  In the case of a host with two 10G NIC's this is not possible so leveraging bi-directional traffic shaping features handle this.  But in deployments where many NIC's are available, especially 1G NIC's, physically seperating vMotion traffic is my preference.  Both get you there and both are good practices.  I tend to choose segregation over software shaping simply because vMotion is very bursty and was designed to use as much bandwidth as it gets out of the box.  In limited bandwidth scenarios (to me 1G NIC's are limited bandwidth) physically allocating bandwidth to vMotion takes care of all considerations in one swoop.  Of course in high-bandwidth environments (multiple 10G NICs) it would be much better to carve up the bandwidth, let traffic shaping and control do its thing, and know that you are utilizing all of your bandwidth investment as efficiently as possible.

This is all relevent to the use case and context takes precident.  Hope this helps - just my 2 cents. Smiley Happy

Bi-directional Traffic Shaping
Bi-directional Traffic Shaping
Reply
0 Kudos