Link to home
Start Free TrialLog in
Avatar of cobmo
cobmoFlag for United States of America

asked on

Configuring MS Windows 2016 Hyper-V servers NIC settings

I have setup an MS Windows 2016 server Hyper-V Host with 3 Hyper-V Servers.  The NIC has 4-ports. All seems to work fine.  
However, I'm not sure I configured correctly.  The attached pdf shows the Network Sharing Adaptor screen of the Host and one of the Hyper-V servers.  On the Host, there are 7 connections on the Network and Internet view. The Host is fine with its static IP but the Hyper-V servers created the Hyper-V Virtual Ethernet Adaptor as well has the HP Ethernet Port it is assigned. The Hyper-V Virtual Ethernet adaptors assigned a DHCP IP address.  In looking at one of the Hyper-V servers (bottom first page of pdf), it only has the Adaptor I created and selected in the Hyper-V settings which I configured with a static IP.

My uncertainty at issue is that on the Host, the Hyper-V Virtual Ethernet Adaptors with the DHCP addresses shows up in DNS as Ball18 - 4 times.  Have I made a mistake in this configuration or is it doing what it is supposed to do? I would think that DNS having 4 entries as Ball18 with 4 different IPs would be inaccurate. The 2nd page shows the sample server hyper-V settings in which I created the Adaptors #2, #3, and #4 for each HV server.
Ball18Sample.pdf
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

IF they are all on the same network, why not team them?
Avatar of cobmo

ASKER

Because Im not aware how to do that. I thought if I assigned a specific port on the nic that each HV would have their own without sharing resources.  What is the benefit of "teaming" them?
Teaming combines the NICs so if one or more become disconnected, there is no interruption in connectivity.  It's very easy to do.  This blog illustrates how (should be the same in 2016):
https://blogs.technet.microsoft.com/kevinholman/2012/06/02/windows-server-2012-creating-a-nic-team-for-load-balancing-and-failover/
Just looking at your current configuration, I would say the only thing you missed was NIC Teaming as @Lee Pointed out.

Usually we do 2 Teamed, then 2 for iSCSI w/our individual VLANS configured on an Extendable External Switch.
Avatar of cobmo

ASKER

So the Host is fine. I would "Team" Ball18-DC Port 2 with its vEthernet (Ball18-DC Adaptor #2)?
give me a screenshot of the Network Connections in Detail view and make sure I can see the full device Name.
ASKER CERTIFIED SOLUTION
Avatar of Matty-CT
Matty-CT

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Should look something like this:
 
User generated image
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

Please have a read through them as they explain a lot about how Hyper-V works, how to configure it, and what to expect out of the host box as far as performance goes.
@Philip

Nice Articles ! If only those had been around when I configured my first one :P
Avatar of cobmo

ASKER

The Management checkbox was the feature I was looking for with this issue.  I thank all of you for your articles and "teaming" advice which I will research further.