Hi again all! In this blog post I wanted to cover VLAN tagging inside of Virtual Machine Manager. Specifically touching on how to bypass a one to one relationship for a VLAN to a VMNetwork. This relationship is really useful when you are delegating control of these networks to a tenant admin but if you are not in a hosting environment it may seem like one layer of abstraction too many. Simpler
To achieve this you will have to create a new Logical Network first. During creation instead of choosing “VLAN-based independent networks” choose the “One connected network option” and tick the bottom checkbox.
In the next window Name the Network Site appropriately for your environment and then add the associated VLAN tags, hit next, then finish.
You will now see a VMNetwork with the same name as your Logical Network has been created
Don’t forget to add the new Logical Network to the Host or to the Logical Switches Port Profile depending on what option you are using. I’m using a Logical Switch with Port Profiles so I’ll look at the properties of the Port Profiles Network Configuration and tick the checkbox for my new Logical Network.
Now under my VMs I can take a look at Hardware Configuration. In the scenario of using a “VLAN-based independent networks” as my selection from my Logical Network to change VLAN tags I would have to pick an new VM Network and that would autofill in my VM Subnet and finally my VLAN tag. This process can seem a bit cumbersome for someone that is just wanting to change tags in a private cloud environment like we are used to doing in Hyper-V Manager or Failover Cluster Manager.
With this configuration I can simply choose my new Logical Network, Enable VLAN, and Select my tag from the drop down.