Forum Discussion
HyperV 12 on Windows 2025 ready for production?
Fighting with three HyperV servers in a failover cluster. I understand that now you have to use SET teaming and lbfo is no longer supported. I also understand that SET is still quite buggy.
I have created three teams with two adapters in each of them, but it confuses me how they appear in "Network and internet > Ethernet" vs "Advanced Network setting.
I have set the vEthernets to the static IPs that I need. But the way the NIC shows up seems random... Some of them shows the IP of the vEthenets and they are all set to DHCP
Network seems very unstable if I use more than one NIC in a team. As far as I can google, I am not the only one having these issues. SET networking does not work stable if more than 1 NIC - correct?
So if one needs an HA setup - how to handle NIC teaming correct? Can HyperV 12 on Windows 2025 be used in a prof. live setup?
thx...
1 Reply
Check for your loadbalancing setting on the uplink ports and on the team (get-vmswitch and get-vmswitchteam). It is easiest to have them at HyperVPort. Then a VM will always talk over one specific host nic until that nic fails. Also for the upstream network this is much easier since you don't need to deal with LACP.
And I don't think the data nics need an IP address, only management and live migration.
