So you’ve got vCenter up and running and hosts added, it’s time to enable the cool things vCenter can do - namely vMotion, HA and DRS. I’ve gone back and forth on how I wanted to present vMotion and networking in the home lab. On one hand many existing deployments are likely running 1Gbps, though newer ones are likely to start with 10Gbps as prices have dropped. After a quick Twitter chat I decided to move forward as I would if I had 10Gbps networking and not have separate physical interfaces in my host for different traffic types.
When we setup our ESXi templates there was only a single NIC, let’s add a 2nd NIC to the VM’s. For purposes of this labs (and maybe I’m still old like this) I will keep my management network on a standard switch and my VM network and vMotion traffic on a distributed switch.
- Right click on your ESXi virtual machine and select settings
- Click the Add... button and select Network Adapter
- Select NAT, click Finish and click OK
- Restart the host from vCenter (right click and select reboot) or from the DCUI (F12 >> root password >> F11)
Once the ESXi virtual machine has been restarted, you should see two interfaces in the vSphere Web Client. Repeat for your 2nd host.
In the vSphere Web Client, click on the network tab in the navigator so we can create the VDS.
- Right click on dc01 and select New Distributed Port Groups...
- Name the port group vmotion and click next
- Keep the defaults and click next, then finish, we'll use this port group in a bit
- Right click on dc01 and select New Distributed Switch
- Name your switch, if you've not caught on yet I like short names so my VDS will be called vds0101 (Now wait I thought it was going to just be vds01...why 4 digits all of a sudden! Easy, its VDS #1 (vds01) in datacenter 01 vds0101 :) )
- Select your VDS version, I will go with 5.5
- I'll keep defaults the rest of the way here even though I only have 1 uplink right now available in my hosts, next, next finish.
- Right click on the VDS and select Add and Manage Hosts
- Select Add Hosts and click Next
- Click the + New Hosts button
- Select both hosts, click OK then click Next
- Keep Manage Physical Adapters and Manage VMkernel adapters selected and click next
- If you've followed along here, you should have vmnic1 not connected to any switch so far, that is what we will use for the VDS uplink. Select vmnic1, click assign uplink
- Assign to Uplink 1 and click OK; repeat for all hosts
- With vmnic1 assigned to the VDS click next
- On step 5, Manage VMKernel network adapters, you will see that we only have the existing VMkernel adapters that are currently used for management on the standard switch, no worries we can create a VMkernel interface from this page that we will assign vMotion traffic to
- Select vxprt-esxi01 and click on + New Adapter
- Click the browse button, select vmotion and click OK, then click next
- Under enable services click the Enable vMotion Traffic checkbox and click Next
- Assign an IP address from your IP space, typically you have a separate VLAN defined for vMotion traffic on your switch so you might have a management IP address of 192.168.6.11 for vxprt-esxi01, my vMotion IP might be 192.168.7.11 (I like my last octet to match so vxprt-esx01 would always have a last octet of .11 in any VLAN it is a part of). In this case I am going to jump into the 192.168.6.24x space so I will assign 192.168.6.141 to this interface, 192.168.6.142 for vxprt-esx02 and so on. Again in the lab I'm not likely to have more than a few ESXi hosts so I'm not to worried about going into the 250s
- Repeat for vxprt-esxi02
- Make sure vmk0 is set to Do not migrate and click Next
- On the analyze impact it should be no impact, click next then finish
Your hosts will be added to the VDS and vMotion will be enabled on the newly created VMkernel adapter. To test, I have created an empty virtual machine on vxprt-esxi02 in the silver datastore, I am going to vMotion and Storage vMotion that virtual machine to vxprt-esxi01. Here you can see the screenshot
- Now, right click on the virtual machine and select migrate
- Select Change both the host and datastore (we don't have shared storage setup yet)
- Select the cluster and click next
- Select vxprt-esxi01 and click next
- Select vxprt-esxi01-silver-local and click next
- Click finish
You can see the progress of the vMotion in the Running Tasks window. After a few minutes you should now see your virtual machine on vxprt-esxi01