Hyper-V Network card setup?
-
I set up a Hyper-V 2016 Server last month but haven't done anything with it beyond installing the hypervisor and configuring sconfig. I'm about to get back to it here but I'm unclear on something.
My server has a quad port nic installed and right now I've only got one port plugged into the network. Now what I'm wondering is if I should team the whole thing from the Hyper-V powershell console so that virtual machines can share that team, or something else.
I can't imagine it's reasonable to have one vm per nic port, otherwise I'd be restricted to only four virtual machines until I add another nic.
What's the best practice here? I really should find some documentation..
-
Teamed and shared is the idea. Stick to that.
-
Think of it like any other resource on the machine... you pool your CPU, RAM, and storage together for the VMs to share. You treat the network in the same way.
-
@scottalanmiller said in Hyper-V Network card setup?:
Think of it like any other resource on the machine... you pool your CPU, RAM, and storage together for the VMs to share. You treat the network in the same way.
Yes, totally what I was thinking/hoping. Now I just need to figure out the powershell commands for this...
-
I leave 1 NIC (sometimes teamed) dedicated for host management and replication and such.
Then a team of 2-3 NICs for all VMs to use (not shared with the host OS).
In your case, for testing, I'd do the following:
NIC1 = Management, replication, migration (this is the one that gets a DNS entry, turn off DNS registration on the others)
NIC2 & NIC3 = Teamed - Not shared with the "management OS" (uncheck that box in Hyper-V later after team is set up)
NIC4 = Other testing as you see fit (iSCSI, DMZ, different subnet/network, failover for another network, etc)
-
The instructions are buried in my recent post.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2
-
@tim_g said in Hyper-V Network card setup?:
I leave 1 NIC (sometimes teamed) dedicated for host management and replication and such.
Then a team of 2-3 NICs for all VMs to use (not shared with the host OS).
In your case, for testing, I'd do the following:
NIC1 = Management, replication, migration (this is the one that gets a DNS entry, turn off DNS registration on the others)
NIC2 & NIC3 = Teamed - Not shared with the "management OS" (uncheck that box in Hyper-V later after team is set up)
NIC4 = Other testing as you see fit (iSCSI, DMZ, different subnet/network, failover for another network, etc)
What is the point of a management NIC let alone a team? You have everything on the same subnet in a SMB anyway.
Management networks are all fine when you have a large infrastructure and multiple subnets.
-
@jaredbusch said in Hyper-V Network card setup?:
@tim_g said in Hyper-V Network card setup?:
I leave 1 NIC (sometimes teamed) dedicated for host management and replication and such.
Then a team of 2-3 NICs for all VMs to use (not shared with the host OS).
In your case, for testing, I'd do the following:
NIC1 = Management, replication, migration (this is the one that gets a DNS entry, turn off DNS registration on the others)
NIC2 & NIC3 = Teamed - Not shared with the "management OS" (uncheck that box in Hyper-V later after team is set up)
NIC4 = Other testing as you see fit (iSCSI, DMZ, different subnet/network, failover for another network, etc)
What is the point of a management NIC let alone a team? You have everything on the same subnet in a SMB anyway.
Management networks are all fine when you have a large infrastructure and multiple subnets.
Yeah I don't have a management network set up. Though we do have a lot of servers and appliances, so it might be nice to set one up anyway. But that's another project for another day.
-
@dave247 said in Hyper-V Network card setup?:
@jaredbusch said in Hyper-V Network card setup?:
@tim_g said in Hyper-V Network card setup?:
I leave 1 NIC (sometimes teamed) dedicated for host management and replication and such.
Then a team of 2-3 NICs for all VMs to use (not shared with the host OS).
In your case, for testing, I'd do the following:
NIC1 = Management, replication, migration (this is the one that gets a DNS entry, turn off DNS registration on the others)
NIC2 & NIC3 = Teamed - Not shared with the "management OS" (uncheck that box in Hyper-V later after team is set up)
NIC4 = Other testing as you see fit (iSCSI, DMZ, different subnet/network, failover for another network, etc)
What is the point of a management NIC let alone a team? You have everything on the same subnet in a SMB anyway.
Management networks are all fine when you have a large infrastructure and multiple subnets.
Yeah I don't have a management network set up. Though we do have a lot of servers and appliances, so it might be nice to set one up anyway. But that's another project for another day.
But do you have enough (reasons) to warrant splitting out the management network from the main network?
-
@tim_g said in Hyper-V Network card setup?:
I leave 1 NIC (sometimes teamed) dedicated for host management and replication and such.
Then a team of 2-3 NICs for all VMs to use (not shared with the host OS).
In your case, for testing, I'd do the following:
NIC1 = Management, replication, migration (this is the one that gets a DNS entry, turn off DNS registration on the others)
NIC2 & NIC3 = Teamed - Not shared with the "management OS" (uncheck that box in Hyper-V later after team is set up)
NIC4 = Other testing as you see fit (iSCSI, DMZ, different subnet/network, failover for another network, etc)
Thanks. And this isn't for testing. I actually want to use this server for some production servers.
-
@dashrender said in Hyper-V Network card setup?:
@dave247 said in Hyper-V Network card setup?:
@jaredbusch said in Hyper-V Network card setup?:
@tim_g said in Hyper-V Network card setup?:
I leave 1 NIC (sometimes teamed) dedicated for host management and replication and such.
Then a team of 2-3 NICs for all VMs to use (not shared with the host OS).
In your case, for testing, I'd do the following:
NIC1 = Management, replication, migration (this is the one that gets a DNS entry, turn off DNS registration on the others)
NIC2 & NIC3 = Teamed - Not shared with the "management OS" (uncheck that box in Hyper-V later after team is set up)
NIC4 = Other testing as you see fit (iSCSI, DMZ, different subnet/network, failover for another network, etc)
What is the point of a management NIC let alone a team? You have everything on the same subnet in a SMB anyway.
Management networks are all fine when you have a large infrastructure and multiple subnets.
Yeah I don't have a management network set up. Though we do have a lot of servers and appliances, so it might be nice to set one up anyway. But that's another project for another day.
But do you have enough (reasons) to warrant splitting out the management network from the main network?
Sure, I think so. I have a bunch of iDRACs for our Dell servers (like 25ish) as well as 10 switches and a few rack appliances. I'd say maybe 50ish systems. I could see having a nice little /26 management subnet.
-
@jaredbusch said in Hyper-V Network card setup?:
What is the point of a management NIC let alone a team?
Hyper-V Management, VM replication, VM migration, backups, etc. This NIC is the one that has a DNS entry, all the others do not.
The point is to keep that traffic separate from the NICs the VMs are using and the users are using to connect to the servers.
Teamed because some (in my case) VMs are being replicated, backed up, and (sometimes) migrated across sites. In this one case, also teamed because if not teamed, it would have been left open/free anyways. If it's needed for something else, there's no downtime involved in breaking a TEAM to use it for soemthing else.
-
@jaredbusch said in Hyper-V Network card setup?:
You have everything on the same subnet in a SMB anyway.
Not all SMBs are 10-employee shops man... stop assuming.
-
@jaredbusch said in Hyper-V Network card setup?:
Management networks are all fine when you have a large infrastructure and multiple subnets.
In my case it is.
If testing things in a lab, why not learn to accommodate more than a 10-man shop?
-
@tim_g said in Hyper-V Network card setup?:
@jaredbusch said in Hyper-V Network card setup?:
You have everything on the same subnet in a SMB anyway.
Not all SMBs are 10-employee shops man... stop assuming.
Not, but even a SMB in the 500 employee range does not need multiple subnets.
Stop over complicating things.
-
@jaredbusch said in Hyper-V Network card setup?:
@tim_g said in Hyper-V Network card setup?:
@jaredbusch said in Hyper-V Network card setup?:
You have everything on the same subnet in a SMB anyway.
Not all SMBs are 10-employee shops man... stop assuming.
Not, but even a SMB in the 500 employee range does not need multiple subnets.
Stop over complicating things.
Just... stop. There's hundreds of reasons for multiple subnets in a 500-employee multi-site SMB. Please, just stop.
-
@jaredbusch said in Hyper-V Network card setup?:
@tim_g said in Hyper-V Network card setup?:
@jaredbusch said in Hyper-V Network card setup?:
You have everything on the same subnet in a SMB anyway.
Not all SMBs are 10-employee shops man... stop assuming.
Not, but even a SMB in the 500 employee range does not need multiple subnets.
Stop over complicating things.
Stop pointing out anomalies and saying I'm over-complicating things. How many 500-employee SMBs do you know of that only have one subnet? And if any, I'm sure they are one of hte few or their business model fits it just fine. Maybe 500 employees, and one server and 10 devices total...
You just need to stop this crap with your blanket assumptions.
EVERYTHING depends on each environment.
-
@tim_g said in Hyper-V Network card setup?:
@jaredbusch said in Hyper-V Network card setup?:
@tim_g said in Hyper-V Network card setup?:
@jaredbusch said in Hyper-V Network card setup?:
You have everything on the same subnet in a SMB anyway.
Not all SMBs are 10-employee shops man... stop assuming.
Not, but even a SMB in the 500 employee range does not need multiple subnets.
Stop over complicating things.
Just... stop. There's hundreds of reasons for multiple subnets in a 500-employee multi-site SMB. Please, just stop.
Multi-site does not mean you need multiple subnets within each site, which is the point I am making.
Your replication and backup processes for this size will almost never be pegging the bandwidth from your 4 NIC team. This means no impact to your users.
So again, you are adding complications and restrictions without a good business need.
Of course these function exist for a reason.
Of course they do exactly what you say they do.
Of course, you likely have no actual technical need for it in almost any SMB.
-
@jaredbusch said in Hyper-V Network card setup?:
Multi-site does not mean you need multiple subnets within each site, which is the point I am making.
True, and it also doesn't mean you need a single subnet either.
-
@tim_g said in Hyper-V Network card setup?:
@jaredbusch said in Hyper-V Network card setup?:
Multi-site does not mean you need multiple subnets within each site, which is the point I am making.
True, and it also doesn't mean you need a single subnet either.
It does without a valid business need to justify the expense and complication of adding it.
Yes the expense is relatively small, but often, the complication down the road is not.
