Learn how to create a VMkernel interface for vMotion and deploy a distributed switch.
- [Narrator] In production environments, typically each V switch will have at least two uplink adapters, each one connected to a separate physical switch to allow for redundancy. Even though it's not really important for a lab environment, I'd like our lab environment to mimic a real life environment so I'm going to go ahead and add a second physical adapter to my V switches. To do this, I just select the V switch and click on the little green card here, and then click on the plus. And then add in vmnic1, click on ok, now we'll see that there's two physical adapters there.
In addition I need to create a VMkernel interface for vMotion traffic. To do this, I click on the little green plus next to the world. Select VMkernel Network Adapter, go to next, I'm going to leave it on the same V switch that we already have. And I'm going to call this one vMotion. In a production environment, we would typically change the VLAN however like I said, we're not going to use VLANs in this environment so we'll leave it where it is. As of 5.5, VMware introduced the ability to do multiple TCPIP stacks.
Each stack is going to have its own VMkernel interfaces, its own routing table, and its own default router. There is a stack available for vMotion because vMotion can now be routable. For more information about TCPIP stacks, see my vSphere 6 Networking course. Click on next and this is where I'll enter the IP information. Because we're not going to be routing vMotion in the lab environment, I can make up whatever IP addresses I want, as long as they're not being use anywhere else in my network. Each ESXI host is going to need its own separate IP address and they all need to be on the same subnet.
New to 6.5 is the ability to create a default gateway per interface. Meaning that any traffic exiting this interface is going to use its own default gateway rather than the one that is assigned by the TCPIP stack. Doing so is only necessary for specific situations and most of the time you're not going to want to override the default gateway. Click on next and finish. Now we'll want to make the same two changes to our other ESXI host but I've already done that in this case.
Here's our new VMkernel adapter for vMotion. And we can see its IP address there. Then I can check the same information on the other two. To verify that each one has a unique IP address on the same subnet. I could also assign a vMotion interface to my physical ESXI host also on the same subnet, and then I'd be able to vMotion between my physical ESXI host and my virtual ESXI host. Use caution if you decide to do that as if you try to vMotion one of your ESXI hosts to itself, it will crash that server.
Next I want to create a distributed switch. To do this I go over to networking, right click on my data center, distributed switch, new distributed switch. Give it a name. There are multiple versions of the distributed switch available. Each one matches the versions of ESXI. A 6.5 distributed switch could only be used on 6.5 ESXI hosts. Each one adds additional enhancements to the distributed switch.
Since all my hosts are 6.5 I'm going to stick with the 6.5 distributed switch. I've only got two available adapters so I can reduce that. I don't want to use Network I/O Control and I'm going to create a new port group. Click on finish. Now I have a distributed switch but I need to add my ESXI host to it. Right click on it. Add manage host.
I want to add host to it. Click on plus. And I'm going to select all three of my VSAN hosts. New to 6.5 is the ability to use template mode. Check on the little box down here and now when I go to configure one host I can use that as a template for configuring the other two. Select my first host. Now I don't want to move over any of my VMkernel adapters so all I need to do is manage physical adapters.
This screen here shows my template host and then it shows me the available mix. It shows the ones that are already being in use, I don't want to steal those ones so I'll select vmnic2, assign it to uplink slot one, and then select vmnic3, and assign that to uplink slot two. Now all I have to do is click on apply to all and those exact same settings get applied my other two ESXI hosts.
Click on next, it's going to verify that this isn't going to impact iSCSI. Since I don't have iSCSI configured it won't. Then it just verifies the information and I click on finish. And that job finishes rather quickly. Now I have all three ESXI hosts connected to that distributed switch, If I go back to hosts and clusters, select one of my ESXI hosts, we'll see now that the distributed switch shows up. For more information about distributed switches, see my Configure and Manage Vmware vSphere Distributed Switch course.
Now lets take a look at our storage configuration for the lab.
- Virtual machine benefits
- Building a lab environment with a mini PC
- Working with ESXi and vCenter Server
- Installing a control center VM
- Using the HTML5 client and the web client
- Adding an ESXi host and use Remote Console
- Configuring vSAN and storage profiles
- Adding NFS datastore
- Deploying a virtual machine from OVA
- Performing a cloning operation
- Using templates
- Performing a vMotion migration
- Working with snapshots