Wednesday, June 13, 2012 3:42 PMHello,
I have a customer that recently had some ip office products installed as well as a wireless controller. They went from having 1 data VLAN to now having a Legacy Data, Data, Voice, Wireless, and Wireless Guest. They have two Hyper V hosts. One of the hosts houses there DHCP server which is on there primary domain controller. The customer has set the port on the physical switch for the uplinks to the hosts as a trunk port containing all the VLANS. All virtual servers but one are on the Legacy DATA VLAN. The one VM that is not on the Legacy VLAN is was set up as a Voice Mail server and it is on the Voice VLAN. Since the DHCP server technically only needs to see the untagged packets from the Legacy Data VLAN, is there something that needs to be done to the nic of the VM or does the host uplink port need to be set as an access port (untagged) for the Legacy DATA. Then the other host uplink that has the Voice server I would assume has to be set as an untagged port for legacy data and have a tag for Voice and also setting up the nic for the voice server to see the tag for voice? Since I am not fimiliar with Hyper V I am trying to logically think this thru but dont have access to the Hyper V setup. Or at this point does hyper V have the option to institute a virtual switch that you can designate these specific changes to ports, leaving the physical uplinks of the hosts as trunks?
Any help would be greatly appreciated!
Thursday, June 14, 2012 7:43 AM
HyperV has Virtual switch were you can VLAN tag the network interface of your vitual machine. - Not sure if this answers your question?
This wiki will proberly help your understanding
Hyper-V: Configure VLANs and VLAN Tagging
Friday, June 15, 2012 8:52 PMWhat about in the case of the DHCP server where I want an untagged port for there data VLAN and don't want to tag the network interface for the VM. Is there somewhere you have to set a VLAN as management so if you dont tag the network interface it will default to the network interface having this VLAN as the untag access.
Saturday, June 16, 2012 10:29 AM
You can create more than one virtual network, each with different properties. Including which VLAN's your trucking to that virtual network.
So in case your only assigning one VLAN to the network interface, you dont need to specifically assign it on the interface, it will just operate with that VLAN.
Wednesday, June 20, 2012 3:37 PM
Just to recap,
If you want an untagged port for a DHCP server, you should not tag the virtual network interface for the DHCP server with a VID and make sure the assigned VLAN to the physical network interface is set as the VLAN you want the DHCP server to have for untagged data.
Currently this customer has the virtual interface tagged with a VID for the DHCP VM and the physical nic on the host currently has this VLAN only assigned to it so he is essentially tagging the DHCP server, which is unnecessary.
Wednesday, June 20, 2012 6:15 PMExactly :)
Thursday, June 21, 2012 8:12 PM