EDIT: 11/29/2011
I have no updated these to reflect vSphere 5 changes!
VMware vSphere 5 Host Network Design Layout and Configuration
My current situation sits as follows. We have zero rack space. Literally none. I can't even rack up our new IBM x3650 M2 servers or the NetApp FAS2020a SAN for the vSphere migration. Thus, I have to make space by virtualizing a few boxes first.
I thought about going ahead and unboxing the x3650 systems and setting those on the ground, wiring and firing them up, but then I realized I would have to spend a weekend unplugging all 10 cables out of each server to rack them up, then hoping I made sure to label my cables correctly. So my new plan goes as such: I have a HP DL380G5 w/ 2 Quad Core E5405, 16GB of RAM, 540GB of internal HDD, and only 2 NICs. This server will give me the ability to P2V a few servers to the local storage, then use SVmotion to move those VMs over to the SAN when it's added to vCenter. I already have my switch environment setup with VLANs configured and ready for deployment for my IBM servers. My logic follows as such:
Service Console = VLAN 50
VMotion = VLAN 51
SAN Traffic = VLAN 22
VM Traffic = VLAN 1, 180, 750
I was struggling yesterday as to how I could SVmotion these VMs because I didn't have enough NICs to dedicate 1 NIC for Service Console, VMotion, and the VM Network. Thanks to Gabe (@gabvirtualworld) he reminded me about using trunk links for everything instead of doing the VLAN separation on the switch. Per Gabe, SVmotion relies on the VMotion VMkernal, so it's necessary to have for migration. Pretty simple. just setup trunk links and tag your VLANs at the vSwitch.
On your switch, Cisco 3750G in my case, setup trunk links for your 2 connections:
conf t
int range Gi1/0/8-9
desc TempESX_NICS
switchport trunk encap dot1q
switchport mode trunk
switchport trunk allowed vlan 1,22,50,51,180,750
I created the allow list because VLAN 1 can potentially have problems if it's not specified.
During the install of ESX4 there is a point where you select the NIC for Service Console connection. Underneath is a checkbox for specifying the VLAN. Tick the box and type in your VLAN, in my case, 50. Finish up w/ your ESX4 installation.
Connect the vSphere Client to your new host and setup the vSwitch as such:
Add vmnic1 to the Properties of vSwitch0, create your new port groups for VMotion and VM Network (remember to specify the VLAN) and use explicit failover for all your port groups:
Service Console = vmnic0 Active, vmnic1 Stand-By
VMotion = vmnic1 Active, vmnic0 Stand-By
VMs = vmnic0 & vmnic1 Active
Hopefully this will allow a seamless SVmotion.
Per Gabe:Test a svmotion, if it fails, set nic1 standby on the VM portgroups oh and by fail I mean that it breaks half way or near the end, not in the beginning fail because of timeouts
I will report back.
-------------
UPDATE!
I completely forgot about this post, but as you might have guessed, Storage vMotion went without any problems what so ever. You can even turn off the VM and use Veeam FastSCP to transfer the VM if needed.