Forum Discussion
New-VMSwitch SET teaming BSOD
hi to all
i have installed the server 2025 evaluation to try hyper-v and failover cluster features.
I used 2 hpe proliant bl460c gen9 with shared storage (yes i know, is not supported. but this is a lab to test if the product is capable of replacing VMware)
one good news is that server 2025 accepts drivers designed for server 2019 and server 2016.
the failover cluster runs without problems and do what is expected.
the hyper-v... well... is another history...
when i try to configure in PS a vswitch with 2 nic in teaming a BSOD is displayed... both nic's are in dhcp. If i configure one nic with static ip address, the command stops at 80%.
the command i used:
New-VMSwitch -Name "SET" -NetAdapterName "Ethernet 3","Ethernet 4"
this behaviour occurs in both servers.
Even though I am probably far too late:
I noticed similar problems with SET and an old HPE 530T card. Another system with X710 NICs works flawlessly.
I can configure the team if I connect at most 1 cable on a HPE 530T, but as soon as the second link activates the system goes into a BSOD loop. Once I remove any additional links the system works again. The old teaming still works when created manually.
Observed on Server 2022 and 2025.
There is a new firmware update for the card which I have to test, but I don't have high hopes.
