I have several ESX servers that I cannot go up to ESX4i due to hardware compatibility constrants. There are presently ESX3.5 u3. I was going to upgrade (clean install since you can't go from ESX3.5 to ESXi3.5) them all to ESX3.5i u4 instead so they are at least patched. The way I have VMotion setup on the ESX servers presently is I have one network interface for the service console and one network interface for vmotion. I've teamed them on the same virtual switch. I've set them up so that the service console uses one adapter and then if it goes down it will use the adapter that VMotion is using. If the VMotion network interface goes down that functionality will fail over to the network interface that the service console is using. Both the Service Console and VMotion IP's are on the same subnet.
When I went to update to ESXi3.5 u4 it appears that you can no longer have the VMotion and Management network interfaces on the same virtual switch if they are on the same subnet. Is anybody else teaming the VMotion and Management network interfaces? I don't want to have to add another couple of network interfaces to the machines and use another two network ports for each ESX server just to have redundancy for vmotion and managment.
I currently use 1 VMkernel interface for both management and VMotion on 3.5u4. No issues.
VMware vExpert '2009