How To: VLAN’s with Hyper-V NIC Team (LACAP Active Trunk)
-
Hi Folks,
Would need some help getting VLAN’s working in combination with a Hyper-V NIC Team. This is the situation.
Hyper-V host running Windows Server 2019
- 1 Management LAN network card
- 4 Network cards teamed as LACP Teaming Mode and Hyper-V Port Load Balancing. The NIC Team is fully up and running.
- The NIC Team is connected to 4 VM’s including pfSense (LAN interfaces)
HP 1810-24G 24G port Gbps Switch
- Port 1,2,3 and 6 are connected to the NIC Team as LACAP Active Trunk port (TRK1)
- Trunk port 1 on Native VLAN 1 is Untagged (all other ports also)
- Trunk port 1 on VLAN10 is Excluded (all other ports also)
Running pfSense 2.4.5-RELEASE-p1 as a virtual machine
- LAN (hn0) is connected to the NIC Team (IP: 10.0.0.254)
- WAN (hn1) is connected to the ISP modem (Bridge mode)
- VLAN10 (on hn0-Lan), VLAN Tag: 10 (IP: 10.10.0.254)
On the Hyper-V host ran the following PS command to allow VLAN 10 traffic . Using the MAC address to address the LAN interface of pfSense. The LAN interface is part of the NIC Team mentioned earlier.
After running this command all connectivity on the network stops?! Also VLAN 1.
Get-VMNetworkAdapter -VMName "01. pfSense Firewall" | Where-Object -Property MacAddress -eq "00155d000f08" | Set-VMNetworkAdapterVlan -Trunk -NativeVlanId 1 -AllowedVlanIdList "10"
Running the following PS command brings everything up and running again.
Get-VMNetworkAdapter -VMName "01. pfSense Firewall" | Where-Object -Property MacAddress -eq "00155d000f08" | Set-VMNetworkAdapterVlan -Untagged
Would appreciate some insights here. Does this problem occur because of the NIC team?
Looking forward to get this done with you help.
Kind regard,
Herman F.
