Save to My DOJO
It’s one thing to be able to install ESXi on a single host, but how do we make it as real-world as possible? Sure, you can build a single host but you need multiples in order to do anything remotely cool with ESXi. You have options when it comes to VMware vSphere networking best practices, that’s the good thing. The bad thing is that realistically, you probably won’t have the hardware to support the “ideal” setup. Most consumer-grade switches don’t support VLANs, so you’ll want to make sure you get one that does if possible.
“Flux segregation is an important component in vSphere networking”
NOTE: This article mainly covers the switching layer. For guidance on specific NICs to use in your homelab hosts, it is best to take a look at the 1GB NICs using the VMware Compatibility Guide. If you’re in a place where you want to test 10Gb switching in your lab, then you’ll need to adjust the physical switches listed in option 2 below. Note also that the type of portgroup will define what networking features are supported by vSphere 6.0.
Let’s take a look at a few options.
Now we’ll start with the most simple setup, a single flat VMware vSphere networking, and a single NIC. Yuck.
Your default ESXi install actually defaults to this and it’s one of the reasons I see it all the time. It’s my least favorite of all and it is obviously vSphere networking. The only place this should be considered an option is if you don’t have the budget to upgrade your existing switch.
I’ve seen a lot of people start this way and then quickly realize they want to upgrade to a better solution. I’d never recommended it as a consultant in a production environment but technically in a homelab, yes you could do it. It WILL work. With all of that being said upfront, what you’re essentially doing with this setup is running all vmkernel port groups and virtual machine port groups on the same NIC in the vSphere networking stack. All storage, virtual machine, management, vMotion, etc. If you’re lucky enough to have a host with more than a single NIC, you might want to split some of that up. Possibly put virtual machine traffic on another unmanaged switch. If you’re anything like me, you have a box of hardware laying around. For a while, I used two basic unmanaged switches in my lab and they worked ok. If your vSphere networking looks like the one pictured, it might be time to move into the second option!
Your next best option to configure vSphere networking for ESXi hosts would be to pick up a basic managed switch. One switch I’d recommend is this TP-Link 16 port. It’s a pretty good value, supports both VLANs and Link Aggregation, and would allow you to segregate your vSphere networking traffic even though you’re only using a single switch. Generally, I create a VLAN for management traffic, vMotion, etc. I like to keep my lab VM traffic on its own VLAN as well so it keeps my normal home network as-is. The beautiful thing is flexibility. You can now isolate everything and potentially use less physical cabling. You set up the trunk port on your switch and when adding a port group, add the VLAN ID into that field and you’re done!
A few other switch options for you if you decide to go this route:
Our last option pretty much exists for those of us who are doing nesting of our ESXi hosts. With nested hosts, the VMware vSphere networking is virtualized on top of the ESXi host. The best part here is that because you’re nested you need a small uplink to the outside world for things like updates, etc. But other than that you can design the port groups on your physical ESXi host and build on top of those. It becomes much easier this way. As the years have passed, I have become more and more of a fan of this type of homelab. Basically, one massive physical server and smaller nested ESXi hosts are hosted on top of it. It opens up scripting options and ease of deployment as well. As long as the nested ESXi hosts are on those same port groups, you’re good to go!
Regardless of what you are going to set up in your lab, be it a simple setup or something more advanced, you should always strive to follow vSphere networking best practices. Even if it makes little sense at home and it’s not vSphere advanced networking training, it is a great way to learn how to do things right.
Refer to the vSphere networking guide for guidance on vSphere networking best practices, it includes everything you need and more.
To protect your VMware environment, Altaro offers the ultimate VMware backup service to secure backup quickly and replicate your virtual machines. We work hard perpetually to give our customers confidence in their backup strategy.
Plus, you can visit our VMware blog to keep up with the latest articles and news on VMware.
As I mentioned above, I am becoming more and more a fan of nested ESXi. Your nested design can more accurately represent a real scenario by breaking out the vSphere networking and you can change things more easily depending on the scenario you are currently testing for. As far as physical network design, just stick with a standard managed switch, I’m not partial to brands but have had great luck with the TP-Link one I linked above. If you’re looking to go one step above, you could buy two physical switches for even more redundancy and load balancing, and even start doing some failover testing and training as well! I suppose it’s all in what you have in the budget. Just stay away from one big flat network with all your services running on a single subnet. It’s troublesome and even in a lab, will barely get you by.
How about you? What type of vSphere networking setups have you used in your home labs to date? Has anything worked better than others? We’d love to know more! Let us know in the comments section below!
Not a DOJO Member yet?
Join thousands of other IT pros and receive a weekly roundup email with the latest content & updates!