Following up on my recent posts on Hyper-V, I thought I’d write up a quick post on setting up multiple VLAN’s in Hyper-V. In my research I found these posts:
They pretty much say everything that’s needed so you don’t need any whitepapers from me – I’m sure you’re glad to hear!
The concept is that you create a trunk on any physical switch ports that are connected to your VM’s. You then publish the required VLAN’s to that trunk (forgive me – I’m not a Cisco guy; I just ask a local expert for what I want and he does a great job in doing it). You can then VLAN tag either your virtual network in Hyper-V (if everything on that network, i.e. on that physical NIC, should be in the VLAN) or you assign VLAN tags to the VM’s.
This is quite secure. You’re pretty much doing what you do in VMware ESX. The machines with different VLAN tags cannot talk directly to each other without going through either a router or a firewall that connect the VLAN’s. The VM’s can co-exist on a VLAN with physical hosts.
The thing you’ve got to watch out for is that the NIC associated with the virtual switch must support VLAN’s and accept packets with VLAN tags.
Credit: Virtual PC Guy.
BTW: I highly recommend that blog because it’s full of great information and sample VBS/Powershell scripts.