Hi all,

I have a customer that need Hyper-V cluster nodes network subnet on a VLAN\subnet different than the guest VMs to be hosted on the Hype-V cluster (hosts in a subnet and guests on different subnet). Is this possible? Is it only about doing network routing on the router\L3 switch? 

• Moved by Alex LvMicrosoft contingent staff, Moderator Friday, January 30, 2015 1:27 AM

You could trunk all the VLANs that are necessary on the physical switch on the ports that you've connected your hyper-v hosts to.

1. Then create a virtual NIC for the host, through your Hyper-V switch. On this NIC you can then assign the IP address for the host, in its respective VLAN.

Add-VMNetworkAdapter -ManagementOS -SwitchName <name> -Name <nic_name>

OR

2. Go to the hyper-v switch that they are using, and enable vlan identification for management OS, then tag it with the VLAN in the GUI.

3. For the virtual machines, you enable and tag the network card for the VM in under settings for the respective VM.

• Edited by Marvin Myrbråten Thursday, January 29, 2015 1:31 PM
• Proposed as answer by Alex LvMicrosoft contingent staff, Moderator Friday, January 30, 2015 9:26 AM

Hi Marvin,

I will have the below configuration (for each Hyper-V server - I will have 6 servers):

1. Two NICs for VM access and Hyper-V remote management (Public LAN) configured in one team and set static IP on it.

2. Two NICs for live migration configured in one team and set static IP on it.

3. Two NICs for heart beat (cluster communication) configured in one team and set static IP on it.

4. Two iSCSI NICs for storage connectivity

The VMs will have another subnet but will be joined to domain, so what I need is to trunk\routre all the VLANs that are necessary (VLANs on hosts and VMs) on the physical switch on the ports that we connected our hyper-v hosts to then in Hyper-V on each server, I will configure the below virtual networks:

1. Virtual network from the public LAN NIC and enable vlan identification for management OS then tag it with the VLAN in the GUI (I do not understand this point?)

2. Virtual NIC from each iSCSI NIC to configure storage from SAN to some VMs.

Please help on this configuration verification.

Hi Ahmad K. Jayyusi,

You can set the different VLAN with your vm, as Marvin said, we just need configure the VLAN ID and enable the switch trunk, the others consider is live migration, we need add the live migration network in Hyper-V manager, we recommend that you do not use the same network adapter for virtual machine access and management with live migration NIC.

The related KB:

Hyper-V: Live Migration Network Configuration Guide

https://technet.microsoft.com/en-us/library/ff428137(v=ws.10).aspx

Im glad to be of help to you!

And, if you don't want to bother with VLANs, it can easily be configured without any VLANs - just use different subnets.  VLANs can be useful, but they are not a re

Hi Ahmad K. Jayyusi,

You can set the different VLAN with your vm, as Marvin said, we just need configure the VLAN ID and enable the switch trunk, the others consider is live migration, we need add the live migration network in Hyper-V manager, we recommend that you do not use the same network adapter for virtual machine access and management with live migration NIC.

The related KB:

Hyper-V: Live Migration Network Configuration Guide

https://technet.microsoft.com/en-us/library/ff428137(v=ws.10).aspx

Im glad to be of help to you!

Hi Ahmad K. Jayyusi,

  When using Hyper-V to virtualize workloads, our recommendation is to configure all VLANs for VMs within the Hyper-V Virtual Network Switch instead of configuring VLANs on team interfaces. Configure all VLANs for VMs within the Hyper-V Virtual Network Switch instead of configuring VLANs on team interfaces.  Taking this approach ensures that virtual machines are capable of being configured for any VLAN traffic that is passed to the NIC team and prevents confusing configurations that can occur when certain VLAN traffic is split off on a separate VLAN from the Hyper-V Virtual Switch.

If you want to use VLAN IDs only at Teaming Nics, following is how proceed with this approach;

1. Create a trunked port on your switch.

2. Create a team

3. Create several Team Virtual NICs in parent partition assigning different VLAN IDs to each virtual NIC

4. Create a Virtual Network from each of the Teaming Virtual NICs

5. Connect VMs to proper Virtual Networks

6. Dont specify the VLAN ID field in VM properties

7. But in some cases (e.g. HP NCU) step 6 is exactly opposite. You must specify VLAN ID both on virtual NIC level (step 3) and each VM level (step 6)

The related article:

http://blogs.technet.com/b/keithmayer/archive/2012/11/20/vlan-tricks-with-nic-teaming-in-windows-server-2012.aspx

Im glad to be of help to you!

Hi Alex,

Suppose the hosts subnet is 172.16.30.x/24 and VMs subnet is 172.16.31.x/24.

I will do the following:

1.  Create a trunked port on switch

2.  Create a team, assign a static IP (172.16.30.x/24) on it then join server to domain 

3.  Create a Virtual Network from the teamed Virtual NIC and assign VLAN ID (VLAN 172.16.30.x/24 ID - could be 3 for example) on it   

4.  Assign VMs static IP (172.16.31.x/24) and connect VMs to the Virtual Network created in step 3 and specify the VLAN ID field in VM properties (VLAN 172.16.31.x/24 - could be 4 for example).

Is this right?

• Edited by Ahmad K. Jayyusi 2 hours 17 minutes ago