VMotion requires the setup of a private, Gigabit Ethernet migration network between all of the VMotion-enabled hosts. When VMotion is enabled on a host, configure a unique network identity object for the host and connect it to the private migration network.
Does this mean I need to get our network guys to setup a VLAN on the switch for all ports connecting to each ESX server? I have four ESX servers so I need to have four ports on the switch configured to a separate VLAN, such as 10.30.22.XX and a gateway of .1
I have read the documentation, but want to make sure
There are alot of unusual concepts in a VMware environment that many network guys are not used to. It's always a challenge trying to get them to change there ways. It helps to sit down with them and make them understand the unique networking features of Vmware (the concept of Vswitches, Vnics, Vmotion, Vlan tagging, Port groups, etc.). Once they understand more about it they tend to put up less resistance when you come to them with requests. Just tell them about all the network ports you'll be saving them when you have 50 virtual servers only using 10 or so network ports when they previously used 50 as physical servers....
These are good resources for ESX networking...
One comment here is that I've set the gateway to be the same as the server. Since you need no routing outside of the vlan, you do not need a gateway.
Seems to have resolved issues for others. I've always done it this way so I'm not sure if setting the gateway to a true gateway works any differently.