@fuznutz04 said in KVM networking & teaming:

@DustinB3403 said in KVM networking & teaming:

@fuznutz04 no he's saying you can only assign it in VM or via CLI. You still create your team.

I think he is actually saying, you can create the NIC team in Cockpit. (You can, I did it already), but you then just assign that team, via the VM Guest settings. ...I think.

For what's it's worth, that is what I said.

@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. 😉

@tim_g said in Hyper-V Network card setup?:

@dave247 said in Hyper-V Network card setup?:

Thanks. And this isn't for testing. I actually want to use this server for some production servers.

Sorry, didn't know. I mistakenly assumed testing and lab because of the time frame.

But you can't go wrong with doing it that way.

If you have no need for an extra NIC you could do a 3-NIC team. If you are fine with no management NIC, do a 4-port team and share it with your management OS if for some reason you need that many NICs in a team. Though you probably don't.

Yeah well it is for some low-risk servers, so, kinda almost testing, but not really, if that makes sense. lol

@Mike-Davis said in switch and NIC teaming in Hyper-v:

Good points. Now that I think about it, in this case it's pointless since they have a 1GB uplink to the main switch. Since all ports go in to one switch and there is only one 1GB uplink nothing is gained in terms or redundancy or bandwidth.

You always gain redundancy you can have 3 links fail.

@JaredBusch said in NIC teaming on Hyper-V:

Then you make you vSwitch. If you already have your vSwitch setup, make a team with the ports NOT on the vSwitch, move the vSwitch to the team and then add the final NIC to the team.

Not much to add here. SwitchIndependent mode is a big one on Hyper-V. Sure, Windows can easily use LACP and other means, but what if you want to use two or more uplink switches for redundancy? LACP can't handle this and there is just a handful of proprietary protocols that can. SwitchIndependent mode is doing exactly this by "load balancing" VMs and Host traffic between the available links and failover in case something goes south.

This way, like @JaredBusch said above, you can have LACP-like functionality (max single port speed for a single traffic source) over multiple inexpensive switches. In fact, the switch doesn't know anything about that type of teaming, you could even use unmanaged switches (but really, don't do that)

My hosts are running in this mode.