Hyper-V teaming worth it for LACP?
-
@Donahue said in Hyper-V teaming worth it for LACP?:
I recently setup my new host and one of my old ones on Hyper-V 2019. The old host got a new (2) 10GB NIC and the new host has (4) 10GB ports. In my efforts to get the hosts working and all my VM's converted over, I neglected to setup teaming on the host. Now that most of my VM's are converted, I attempted to make a team on the old host with (2) ports, but I did not use the method that most of the posts on ML use. I created a new vswitch with both ports as members using WAC, but I am not sure if this is the same as what I see in other posts. In WAC, I am able to set it to dynamic for the load balancing algorithm (the only other choice is Hyper-V port), but there is no place to say if it is switch independent or dependent. Also, if I look under NIC teaming in server management, it shows up as a vEthernet at 20gbps, but does not have any other information about algorithm or mode. I am wondering if I should break this back apart and do it from server management (which does have all the options). Also, I have read @JaredBusch's comments on generally using switch independent mode because of it's ease, but since my switch (edgeswitch XG) does support LACP, it seems like it would be beneficial to set it up to help balance incoming traffic as well.
Almost all smart switches support LACP.
I still wouldn't use it because I don't see the need to.
Systems run without lag caused by the network. Even backups run quite quickly.
Now, your network may hit thresholds that need something more. If so, do it by all means. That is precisely why options exist.
-
@JaredBusch So to summarize, configure it as switch independent and only change it if I see inbound traffic saturating a single link?
-
@Donahue are you expecting to saturate multiple 10GB links?
-
@Donahue said in Hyper-V teaming worth it for LACP?:
I attempted to make a team on the old host with (2) ports, but I did not use the method that most of the posts on ML use. I created a new vswitch with both ports as members using WAC, but I am not sure if this is the same as what I see in other posts. In WAC, I am able to
WAC did not exist when I wrote my posts.
At this time I have never even setup WAC yet for a client.
So I have no idea what the settings are.
-
@JaredBusch said in Hyper-V teaming worth it for LACP?:
@Donahue said in Hyper-V teaming worth it for LACP?:
I attempted to make a team on the old host with (2) ports, but I did not use the method that most of the posts on ML use. I created a new vswitch with both ports as members using WAC, but I am not sure if this is the same as what I see in other posts. In WAC, I am able to
WAC did not exist when I wrote my posts.
At this time I have never even setup WAC yet for a client.
So I have no idea what the settings are.
I'm not impressed much with it. As far as I can tell, you cannot see the console of a non windows VM, because it forces it to go through RDP. Maybe there are hoops to jump through to enable RDP to a linux machine, but I have not bothered to find out why. So I am using both WAC and hyper-V manager for the time being.
-
@Donahue said in Hyper-V teaming worth it for LACP?:
@JaredBusch said in Hyper-V teaming worth it for LACP?:
@Donahue said in Hyper-V teaming worth it for LACP?:
I attempted to make a team on the old host with (2) ports, but I did not use the method that most of the posts on ML use. I created a new vswitch with both ports as members using WAC, but I am not sure if this is the same as what I see in other posts. In WAC, I am able to
WAC did not exist when I wrote my posts.
At this time I have never even setup WAC yet for a client.
So I have no idea what the settings are.
I'm not impressed much with it. As far as I can tell, you cannot see the console of a non windows VM, because it forces it to go through RDP. Maybe there are hoops to jump through to enable RDP to a linux machine, but I have not bothered to find out why. So I am using both WAC and hyper-V manager for the time being.
I love the WAC idea, and some of it is really slick, but we have it at some clients and it's really buggy and problematic in the real world. Clearly improving quickly and getting better, but like most things MS, to really use it you have to do one really specific setup that is quite costly and almost never applicable to our clients.
-
The default algorithm in Server 2019 is Hyper-V Port for LBFO Teams. There's no reason to tweak anything beyond the "Share with host OS" setting. Choose the ports to be included in the team, bind a virtual switch to the team, and flip the VMs over to the newly created vSwitch.
Takes about 10 seconds to do the above in PowerShell. The link is to a guide for setting up a standalone host using PowerShell.
-
@JaredBusch said in Hyper-V teaming worth it for LACP?:
@Donahue said in Hyper-V teaming worth it for LACP?:
I attempted to make a team on the old host with (2) ports, but I did not use the method that most of the posts on ML use. I created a new vswitch with both ports as members using WAC, but I am not sure if this is the same as what I see in other posts. In WAC, I am able to
WAC did not exist when I wrote my posts.
At this time I have never even setup WAC yet for a client.
So I have no idea what the settings are.
We do everything in PowerShell and to some degree the native tools. WAC has been low on the To Do List for us.
From what I understand though, there should be a button or link that one can click to expose the underlying PowerShell WAC would be using when the NEXT button gets clicked?
-
Yeah, i think i need to learn powershell. I probably rely too much on GUI's
-
@Donahue said in Hyper-V teaming worth it for LACP?:
Yeah, i think i need to learn powershell. I probably rely too much on GUI's
Same fees, tenth of the time.
