SOLVED

Hyper-V Host network (VLAN) problem in Cluster

%3CLINGO-SUB%20id%3D%22lingo-sub-188923%22%20slang%3D%22en-US%22%3EHyper-V%20Host%20network%20(VLAN)%20problem%20in%20Cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-188923%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20build%20a%20Windows%20Server%202016%20Hyper-V%20Fail%20over%20Cluster.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2%20identical%20hardware%26nbsp%3Bhosts%3C%2FP%3E%3CP%3E2%20LAN%20ports%20on%20each%20host%20are%20in%20a%20Team%3C%2FP%3E%3CP%3E1%20External%20vSwitch%20is%20bound%20to%20the%20Microsoft%20Multiplexor%20Adapter%20on%20both%20hosts%3C%2FP%3E%3CP%3E4%20LAN%26nbsp%3B%3CSPAN%3E%20ports%20on%20each%20host%20%3C%2FSPAN%3Eare%20used%20for%20ISCSI%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20domain%20controller%20and%20Fail%20over%20Cluster%20Manager%20VM's%20are%20running%20on%20this%20cluster%20in%20the%20same%20VLAN%20(Example%201101)%20as%20the%20Hosts.%20This%20is%20all%20working%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20the%20problem%20starts%20when%20i%20create%20a%20new%20VM1%20on%20Host%201%20and%20VM2%20on%20Host%202.%20But%20when%20i%20Assign%20an%20other%20VLAN%20(Example%201102)%20On%20Host%202%20LAN%20works%20fine.%20I%20get%20DHCP%20and%20can%20do%20everything%20i%20want%20like%20join%20the%20domain%20that%20is%20availible%20in%20VLAN%201102.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EProblem%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EOn%20Host%201%20i%20get%20a%20also%20valid%20DHCP-adress%2C%20but%20all%20other%20traffic%20does%20not%20work.%26nbsp%3BSo%20joining%20the%20same%20domain%20is%20not%20possible.%20Also%20i%20can%20not%20Ping%20the%20other%20devices%20outside%20the%20host%20or%20VM2%20on%20host%202.%20When%20i%20Live%20Migrate%20the%20VM2%20to%20host%201%20they%20can%20find%20each%20other%2C%20but%20traffic%20too%20for%20example%20the%20gateway%20is%20not%20possible.%20When%20i%20LM%20both%20VM's%20to%20Host%202%20everythings%20works%20as%20i%20should.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20already%20changed%20the%20MAC%20address%20Pool%20and%20at%20first%20it%20worked%2C%20but%20later%20on%20the%20problems%20came%20back.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-188923%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EClustering%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-189321%22%20slang%3D%22en-US%22%3ERe%3A%20Hyper-V%20Host%20network%20(VLAN)%20problem%20in%20Cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-189321%22%20slang%3D%22en-US%22%3E%3CP%3EFound%20it!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHad%20to%20disable%20VMQ%20on%20Host1%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I've build a Windows Server 2016 Hyper-V Fail over Cluster.

 

2 identical hardware hosts

2 LAN ports on each host are in a Team

1 External vSwitch is bound to the Microsoft Multiplexor Adapter on both hosts

4 LAN  ports on each host are used for ISCSI

 

The domain controller and Fail over Cluster Manager VM's are running on this cluster in the same VLAN (Example 1101) as the Hosts. This is all working fine.

 

Now the problem starts when i create a new VM1 on Host 1 and VM2 on Host 2. But when i Assign an other VLAN (Example 1102) On Host 2 LAN works fine. I get DHCP and can do everything i want like join the domain that is availible in VLAN 1102.

 

Problem:

On Host 1 i get a also valid DHCP-adress, but all other traffic does not work. So joining the same domain is not possible. Also i can not Ping the other devices outside the host or VM2 on host 2. When i Live Migrate the VM2 to host 1 they can find each other, but traffic too for example the gateway is not possible. When i LM both VM's to Host 2 everythings works as i should. 

 

We already changed the MAC address Pool and at first it worked, but later on the problems came back.

 

 

 

1 Reply
Highlighted
Solution

Found it!

 

Had to disable VMQ on Host1