Hyper-V. Virtual machine doesn’t support “physical” VLAN. Is it true?

I’ve got new Dell PE2950 servers with a dual Broadcom BMC5707C NIC and two dual Intel PRO/1000 PT. My initial design was to use teamed Broadcoms for platform, two Intel NICs (one from the first card and another from the second one ) for iSCSI with multipath (two different IP subnets and VLANs will be used for it. so no need for teaming) and the rest of Intels for Hyper-V and may be backup.

imageTeaming Broadcom cards is piece of cake – all you need to do is download Broadcom Advanced Control Suite 3 and a few clicks of you mouse. BTW it can be scripted using BaspSCfg.exe (f.i. BaspSCfg -name LAN0 -type 1  -pnic 5:0.0 -pnic 9:0.0 -vname ad -vid 11).

iSCSI was even easier: standard network card configuration, no teaming, no VLAN (just need to change untagged VLAN to iSCSI on switches) – nothing fancy.

But I killed whole day to make Hyper-V work. First at all Hyper-V doesn’t support teaming. Well I understand why ( it comes from design of virtual switch) but don’t understand why not to have it. For physical switches I put two ports in link aggregation (LAG) to connect switches using two CAT6 cables, so in case of one port or cable failure I’ll working infrastructure. But why I cannot have the same LAG in physical-virtual connections. We need at least fail-over to the second card.

imageOK… if teaming doesn’t work you have nothing do to about it (unless you are a Hyper-V developer smile_teeth ) but I definitely need VLAN. I managed to connect a virtual or guest OS and new virtual NIC on the host or parent partition to the real world – can access other physical servers in different VLANs/subnets. But it worked only for untagged network. All tagged networks didn’t work at all – the guest system could ping its own IP address only.  I tried both MS and Intel drivers, got all latest patches smile_sad.

I was lucky I was not first who came across this issue.  And my answer was in the registry (of course it must be there. nothing’s changed since NT3.5 smile_wink).

If you are going to connect a virtual switch to a broadcom you have to change VlanID property from 0 to 1, for Intels change VlanFiltering from 1 to 0.  The keys can be found in   HKLM\SYSTEM\CurrentControlSet\Control\Class\{CLID}\XXXX, where DriverDesc is "Intel(R) PRO/1000 PT Dual Port Server Adapter". After rebooting VLAN work for Hyper-V NICs and guest OS. rainbow

Next step will be clustering. I hope it won’t kill Hyper-V VLANs  fingerscrossed

CheerZ
Oleg

Advertisements

About oleggap

IT Pro
This entry was posted in Hyper-V. Bookmark the permalink.

3 Responses to Hyper-V. Virtual machine doesn’t support “physical” VLAN. Is it true?

  1. Matt says:

    The latest broadcom drivers fix this issue – run your manufacturer driver update package and you should be right to go.Ran in to the same problem with the Broadcom NetExtreme II on a IBM x3650 – latest updateXpress fixed the issue.

  2. Oleg says:

    Thanks Matt.Just got alert about your commentLive Team needs to fix alerting on space – half a year lag is tooooo much

Comments are closed.