I am running Server 2012 Datacenter on a 2-node cluster. I have a few Hyper-V guests running successfully.
We have 3 VLANs in place:-
VLAN1 is used by all staff devices (PCs, tablets, phones etc), with DHCP being issued by a Hyper-V guest also running Server 2012 Datacenter
VLAN300 is for Customer PCs only (connected via LAN cable) - IPs are allocated by a Watchguard Firebox XTM515, and are in the range 192.168.101.x
VLAN200 is for Customer Wi-Fi - IPs are (currently) allocated by the same Watchguard Firebox, and are in the range 192.168.100.x. Anyone who connects to VLAN200 has to authenticate, and this authentication is handled between the Firebox and an Ubuntu Linux box running Apache and Python. The Firebox passes some data to a python script which then passes control back to the Firebox.
There are a total of 13 Watchguard AP200 units on the physical network handling both VLAN1 and VLAN200
We have intermittent issues with VLAN200 where it suddenly gives up on allocating IP addresses even though the pool still should have plenty to give out. The resolution is to reboot the Firebox (and sometime the connected APs too)
We've had technical support with Watchguard, and they have said that there is a problem with the Firebox handling DHCP on a VLAN Wi-Fi. This has been ongoing for at least a couple of years, so far with no fix.
All of the VLANs, for the majority of time, work well.
However, what I want to do is virtualise the Linux unit so that it runs as a Hyper-V guest but on VLAN300 and this is where my problem lies.
I have the Hyper-V Linux guest installed and I have enabled the VLAN Identification and set it to 300, but it will not communicate with anything on the same VLAN. The ports on the Netgear GS752TPS switch that the 2 Hyper-V hosts connect to have been configured as trunk ports for VLAN300.
I need to get this running so that I can eventually install DHCP services on this Linux box to take the function away from the Firebox.