Hyper-V v3.0 & Virtual Switching

[BoomAM]

Hi,
Is anyone here any good with Hyper-V and virtual switches?

I'm just building myself a test box and i'm trying to setup multiple VLANs, but its not actually letting me put multiple virtual switches on one physical NIC.

Is this by design? As it happens on two test rigs, one running W8 with Hyper-V and one is 2012 with Hyper-V. So its not a limitation of the host OS.

I swear i'm missing something or i'm thinking too "VMWare" as having to VLAN Tag each VM rather than just assigning them to a virtual switch just seems too....archaic.
Surely its not a case of one NIC/Team per VLAN?

Anyone got any ideas? What am i missing?

Thanks.

 

[Saundie]

Is it your intention to put the VMs on to different VLANs? If so, you set the VLAN on the synthetic network adapter on the VM itself;

I don't have access to a 2012 server at the moment, however in Hyper-V on Server 2008 R2 you cannot create multiple external networks on the same physical NIC - it will tell you that it "Cannot bind to 'NIC' because it is already bound to another virtual network", which is presumably what Server 2012 is telling you about the virtual switch you're trying to create?

Hopefully I haven't misunderstood what you're doing and that the above is actually useful to you!

 

[BoomAM]

Is it your intention to put the VMs on to different VLANs? If so, you set the VLAN on the synthetic network adapter on the VM itself;....
Hopefully I haven't misunderstood what you're doing and that the above is actually useful to you!

Thank you for the reply.
Sort of, i'm aware of how to do what you say, but setting it per VM seems very archaic compared to how VMware does it.
I can sort of see the purpose of having it like that for large clusters, as then it carries VM network properties between migrations/hosts, but it still seems odd to me compared to what i'm used too with vmware.

 

[Saundie]

I am not familiar with VMware, having never used it, hence my hesitation in my reply. In order to get that sort of functionality on the Microsoft virtualisation platform, you need to use System Center Virtual Machine Manager. What you're talking about sounds like what Microsoft calls a network location - http://blogs.technet.com/b/scvmm/ar...nding-network-location-and-tags-in-scvmm.aspx. I agree that it is somewhat primitive compared to what VMWare offers, but then again it's a lot cheaper than VMWare once you include all of the vSphere management software (or at least, this used to be the case, it's been years since I last looked into it!).

 

[BoomAM]

Been reading around technet, and yes your right, VMM is needed to do what i would consider "normal" virtualisation management.