Paul Salotti wrote:
How important is it that we segregate Management, vMotion and VM traffic on separate VLANs when using 10GB network? We will have Management, vMotion and the VM port groups on separate vSwitches.
Besides all the good points mentioned by weinstein above you would also want vMotion on a separate VLAN with a different IP range to be able to control it to actually use the vSwitch of your wish. If having several vmkernel interfaces on different vSwitches, but using the same IP subnet will often lead to the result of the traffic using another vmkernel adapter than you might expect.
The primary selection of outgoing interface from the vmkernel is the internal routing table and you could easily end up with using the same vmk and outgoing vSwitch + vmnic for both Management and vMotion.
If keeping separate VLANs and IP ranges for management, vMotion, IP storage, Fault Tolerance if used, there will never be an issue which outgoing interface to actually use.