Guide on properly configuring Hyper-V networking

I'm looking for a guide or step-by-step instructions on properly configuring Hyper-V networking for both the host and virtual (guest) Server 2016 Datacenter operating systems.

In my environment, the Server Datacenter 2016 base operating system is currently running on a server system board that has 4 physical NICs. Currently, only NIC 1 has a network cable connected to it and the other three NICs are disabled within Device Manager.

This means that the base operating system and the Hyper-V virtual operating systems are all currently using the same NIC. This Hyper-V switch is configured as an external network.

I have run these commands from an elevated PowerShell (on the Hyper-V base server) which then return the results shown below.

Please provide me with this information on how to properly configure the Hyper-V virtual networking. If any additional information on my networking environment or Server 2016 Datacenter operating systems are needed please let me know.


Open in new window


Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\administrator> get-netadapter

Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
----                      --------------------                    ------- ------       ----------             ---------
vEthernet (Virtual Swi... Hyper-V Virtual Ethernet Adapter              5 Up           00-1E-67-4D-32-FD       100 Mbps
Ethernet                  Intel(R) I350 Gigabit Network Connec...       2 Up           00-1E-67-4D-32-FD       100 Mbps
Ethernet 3                Intel(R) I350 Gigabit Network Conn...#3       3 Not Present  00-1E-67-4D-32-FC          0 bps
Ethernet 4                Intel(R) I350 Gigabit Network Conn...#4       4 Not Present  00-1E-67-4D-32-FB          0 bps
Ethernet 2                Intel(R) I350 Gigabit Network Conn...#2      10 Not Present  00-1E-67-4D-32-FA          0 bps

PS C:\Users\administrator> Get-NetLbfoTeam
PS C:\Users\administrator> Get-VMSwitch

Name           SwitchType NetAdapterInterfaceDescription
----           ---------- ------------------------------
Virtual Switch External   Intel(R) I350 Gigabit Network Connection

PS C:\Users\administrator>
IT GuyNetwork EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Here's how I would tackle it:

(Assuming you are not using any VLANs at the moment)

Enable the NICs.
Go to Server Manager and under Local Server enable NIC Teaming.
Create a team of the 3 unused network adapters.
Call the team HV-TEAM or something similarly descriptive.
Go to network connections and disable TCP/IP and Client for Microsoft Networks for the newly created team adapter
Plug 'em in to the switch.
Go to Hyper-V and create a new external virtual switch.
Give it a descriptive name.
Use the Microsoft Multiplexor Driver as the external network adapter.
Do not check "allow management operating system to share this network adapter"
In Hyper-V Manager change the network adapter to the newly created virtual switch under the settings for each VM.
Once you've ascertained that all VMs are using the new switch, delete the old one.

That's about it. You might want to go back to network connections and make sure that your original network adapter has the correct TCP/IP settings. If the virtual network adapter was shared with the OS it would've attempted to acquire a DHCP IP address. I don't think I missed any steps but I did bang this out fairly quickly.

Your stats show 100Mbps link. Might want to up that to something 21st century.  I tease. :P

Seriously though, happy to help get you up and running.
IT GuyNetwork EngineerAuthor Commented:
Yes I will be replacing my network switch with a Gigabit network switch this weekend.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Jose Gabriel Ortega CastroCEOCommented:
Well in short, you are underusing the 2016 capabilities of your server.

You can use NIC Teaming (Add 4 NICs to get 4x more network speed).

You can do it in the host (by connecting the 4 cables) and then use this

Or just connect each physical connection into a virtual switch and then connect them as nic team into the Virtual machines

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
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
I have two very thorough EE articles on all things Hyper-V:

Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations

Team two ports and team the other two ports. Set the first team up with an IP on the production network for management and set the second team up exclusively with the virtual switch.
Cliff GaliherCommented:
There is *no such thing* as a "right" way.  If there was then you wouldn't have options. The system would just pre-configure everything and be done.

How you configure your Hyper-V network is *VERY* workload dependent. That's why you have options.  As for what works for you....that you decide based on the workload (as mentioned) and EXPERIENCE.  Working in I.T. is much like any profession.  You don't graduate law-school and get "named partner" status at the first law firm you work at.  Same with working with any new technology in I.T. (whether that's Hyper-V, VMWare, SQL, Exchange, etc.)

All this is to illustrate why your question, as asked, is impossible to answer.  If you don't know Hyper-V, my advice is hire someone.  There is no way you can learn what you need to learn in a forum (how can you know the advice you are getting is good?), or even a more authoritative source, such as a book or a class.  Those are the *start* for learning, not the end. If you are willing to learn then read.  Read. And read.  That's how I learned. And many experts (in Hyper-V) learned.  I am *still* learning (containers is my current focus.)    But I 'd never ask "what is the best way to set up Windows Containers."  I know enough to know that is too broad for a question.

If you need immediate answers (and I suspect you do from previous "windows update" questions), you should hire someone.  If you can take the time though, read first.  Ask more specific questions later.  Experts here (including myself, despite what impression this answer leaves) are  more than willing to help.  But answering requires a foundation.  A foundation I see missing, based on this and other questions.

In short, with only four NICs,  I don't know what the "best" configuration is for you.  I don't know what your topology might be.  Do you use SAN storage?  Are you going for Hyper-converged?  Have you measured the current strain on the VMs?  The network?  How that is currently being distributed?  How could I answer that without those answers?  When I onboard(ed) a new client, I would do an audit.  That included "weeks" of actual performance data gathered at the source.  Obviously I can't replicate that here (nor collect my usual fee.)  Thus my only real answer...hire someone.
Cliff GaliherCommented:
Case in point: Philip answered while I was typing. (For the record, Philip and I know each other and I consider him a colleague and good friend...bonded over Scotch quite a few years ago)...

He wants a team of 2 and 2.  A perfectly valid "right" topolog in many circumstances.  

Personally, I don't team the host NICs.  In a cluster, maybe.  But in a cluster, one big team with QoS configured is actually more redundant and provides more bandwidth to the guests.  In a non-cluster, the guests are the devices needing bandwidth.  So I would be more inclined (in genera) to team 3 to the switch so that Hyper-V's dynamic load balancing has more to work with.  1 for the host.  If the host fails (rare, especially on a quad NIC, where all fail or none), I can get on-site to replace the NIC or deal with issues.  Bandwidth trumps host redundancy.

That equation changes with 2-dual NICs, or four-single NICs.  Which only highlights my point:  Two experts (I consider Philip a significant expert and contributor in the field, and I hope he feels the same way) have mildly differing experiences.  Both forged in EXPERIENCE.  How do you choose between us?  I still stand by "it depends on YOUR workload."  I don't think either he nor I can definitively say which is right.  Only that gut reaction of which solution we'd architect "in a void."  Which is where that multi-week audit comes in.

Anyways, soapbox done.
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 2016

From novice to tech pro — start learning today.