Forum Discussion
Server 2022 Hyper-V and multiple VLANs across single SET
What is the best way to configure two IPs on separate VLANs going over a single Switch Embedded Team (i.e. the same physical NICs handling both storage and VM network traffic) for a standalone Server 2022 Hyper-V host?
From what I've read I just need to add multiple vNICs to my SET vSwitch and assign each a VLAN (Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName iSCSI -Access -VlanId 10) but it's not working in my simulator (GNS3). The tagged traffic isn't being passed by the switches (the ports on the switches are port-channeled and trunked for the two VLANs). I'm not sure at this point if it's a switch or Windows configuration issue, a limitation of Windows Server in GNS3, or a limitation of Windows Server itself. I'm trying to simulate this prior to an actual physical deployment, and want to get it right in testing so I can hopefully avoid any networking issues on the day.
Thanks.
1 Reply
- My colleague and I were able to do a real-world test on a physical Windows Server 2022 server and the VLAN tagging works fine. We created the team, added the two vNICs for the two different VLANs, assigned each an IP and their VLAN ID, and were able to ping other systems on those VLANs. On the switch side the two switch ports were in a LAG that was trunked for the two VLANs.
So it looks like my problem had something to do with GNS3's implementation of a Windows Server VM, or perhaps due to a NIC driver VLAN tagging issue.
