Naming Hyper-V Network Connections

Please can I have some guidance on sensible ways to name network connections on Windows 2012 R2 servers that host Hyper-V Guests?

I teamed two physical NICs "Ethernet 1" and "Ethernet 2" to make "Ethernet Team" for fault tolerance and bandwidth sharing but the Hyper-V Role then creates another "... - Virtual Switch" which seems to be the connection my server then uses

I understand Hyper-V Manager can create more Virtual Switches if needed

I know manually moving Hyper-V Guests between serves has issue where source and target serves have differing network connection names
ARamptonIT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ButlerTechnologyCommented:
We use the subnet in the name when creating hyper-V virtual switches to remind us which switch connects to which VLAN and make it easy to move systems between hosts without switch issues.

210 Subnet
220 Subnet

As for the naming of the actual Network Connection, you could adopt a similar strategy like 210 Subnet A and 210 Subnet B.  I would also physically  mark the NIC on the system to avoid confusion.  In the long run, I don't think the naming strategy on the network connections will be important.
MaheshArchitectCommented:
The network card that is getting converted into switch, you rename it as per zones (External \ internal \ host only) and append "switch" word so that you can understand that it is acting as switch

once virtual network gets created rename it s per zones  (External \ internal \ host only) and append network word so that you can understand that is is working as network card

Also if there is VLAN based NICs you have, add VLAN tag in the naming convention for easy identification

No matter if you are usingh Hyper-V cluster \ standalone server, just note down \ snapshot virtual network settings with MAC address, it will help in case of rebuilding hyper-v servers from scratch if required

In case of Hyper-V clusters, you should keep naming conventions and network card count identical for correct working and understanding

Mahesh
Svet PaperovIT ManagerCommented:
There are no conventions or recommendations of how the NICs should be named. Microsoft changed the naming from “Local Connection” to “Ethernet” in 2012 which makes them less confusing in some cases.

It’s up to you, if you want to rename them further or not. The objective should be that the network connections are easily identifiable either by writing down their names, types, etc. in your internal documentation, or by renaming them, or (best case) by both.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.