Link to home
Create AccountLog in
Avatar of finfrockg
finfrockgFlag for United States of America

asked on

Hyper-V 2008 R2 multiple VLANs on either single physical or HP NIC Team

I'm new to Hyper-V, but not to VMware or Cisco networking.   I've got an HP DL380 G7 with 4 built-in NICs.  Trying to configure server for small branch office with this configuration -

NIC1 - Parent OS.  VLAN 50
NIC2 - Notes server child OS 2008 R2 VLAN 50, Child OS Test server 2008 R2 VLAN 57
NIC 3 & 4 - future HP NIC team trunk mode for remaining child OS installs.  VLAN 50, 52, 57

I've clearly labeled the NICs in the parent OS so I know the difference between physical and virtual adapters.  I cannot get the test server on VLAN 57 from NIC 2 to connect to the network.
Looking at the NIC2 from the Parent, it shows only the virtual network switch protocol and HP Network config utility check marked.
The virtual adapter at the Parent OS level has everything checked except VSP.
Within the Child OS -

Within Virtual Network Manager - the NIC is external.  I've played with "Allow mgmt OS to share.." both on and off and the Enable vlan ID within the Child network settings.  

What is the right combo of settings for the NIC2 physical to be shared with 2 child OS on different VLANs connected to a Cisco switch in trunk mode?  

All NICs drivers, BIOS, and firmware are the latest and greatest from HP.  Parent OS and child OS are fully patched.



Avatar of zzx999
zzx999

There is some tricks. You should use Hyper-V manager to manage your nics if you want enable VLAN's on same nick for host OS and for vm's.
If you will use native drivers on host OS to use VLAN's, these NIC's wont work in Hyper-V.

SOLUTION
Avatar of finfrockg
finfrockg
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
this address 169.254.0.0/16 is from microsoft pool and asignet automaticaly to interfaces that do not get it automaticly via dhcp.
you mentioned cisco trunk.
Have you enabled 57 VLAN on cisco?
Avatar of finfrockg

ASKER

After enough testing different options, it finally worked.
Please close I figured out the problem myself.
I figure it out myself immediately after posting the question.