It’s critical that I be able to set up separate and secured VLAN’s in Hyper-V. To do this you set up an External Virtual Switch with VLAN tagging enabled.
I’m using a HP DL380 G5 with the following configuration:
- Windows Server 2008 x64
- HP PSP 8.0
- 2 * NIC’s: HP NC373i Multifunction Gigabit Server Adapter (V4.1.3.0)
- Hyper-V RC1
The first NIC is set up for the parent partition (that OS you install first and manages Hyper-V locally). It is attached to a normal Cisco switch port. The second NIC will be used for the virtual switch. It’s connected to a Cisco switch that’s configured to trunk a set of VLAN’s that the VM’s will run on.
I set up the VM’s and tried to set up the External Virtual Switch with VLAN tagging. Problem – It failed with this error:
"Error Applying New Virtual Network Changes
Cannot enable virtual LAN (VLAN) identification. The virtual network switch is connected to a physical network adapter that does not support VLAN identification."
No matter what I did I couldn’t resolve this: driver updates (N/A), reinstalling the NIC, uninstalling HP software, etc. I fired up a post on the Minasi forum and a server whiz called Willem Kasdorp sorted me out. MS had documented a workaround which my hour of googling failed to turn up. The cause of the problem was the NIC driver. The solution was to open the properties of the parent partition’s NIC#2, configure the driver and set the VLAN ID to "1". Now I could create my virtual switch and everything worked perfectly.
Credit: Willem Kasdorp.
EDIT:
While having this problem I opened a call with MS via my IT Pro Momentum account. I got a quick response and they confirmed this solution. Setting the VLAN ID of the physical card to a "non zero value" resolves the issue.