Hyper-V 2012: Why VLAN ID number instead of using a friendly port group name?

Excerpt from an article.

Here is where my dislike of Hyper-V network steps in. When one creates a new VM and it must be assigned a particular VLAN it has to be done by VLAN ID number and not using a friendly port group name.

I assume for most admins this configuration setting is not a large inconvenience as they may only have 3 or 4 VLANs. However, what if you have 10 or 15 or 50 VLANs in your environment? Every time you create a machine you have to know which VLAN ID number corresponds to the proper network segment for your new Management VM, or your new SQL server VM.

I think I can use -VMName instead of -ManagementOS for LAN, NLB and DAG to add them to appropriate VMs.  

But in all books an articles I'm reading the VLAN assigned to a VM is done by VLAN ID number.  

Is there something I should be aware of about using -VMName instead of selecting a VLAN ID for each VM I'm adding?

Thanks
quadrumaneAsked:
Who is Participating?
 
Craig BeckConnect With a Mentor Commented:
It's really about how the network and Hyper-V interact.  If you connect all of your host NICs to VLAN-tagged switch ports you would have to set the VLAN ID for each Guest, as the article says.  Or, you could assign one NIC in your host to VLAN1 at the switch, another port to VLAN 2 at the switch, etc, etc, then assign them to your Guests as you require.

Unless something has drastically changed between Hyper-V2 and HyperV3, assigning the VLAN ID can only be done in one place, using the VLAN ID.  There is no concept of port groups as such - that's done at the network level.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.