Best Practice for Window 2012 Hyper-V Cluster with Multi-Subnets (VLAN’s)

I have a three host Windows 2012 Hyper-V cluster with multiple VLAN’s.  Currently I have two virtual switches configured on all hosts.  

Since there is no way (that I can find) to configure a new virtual switch through the Failover Cluster Manager, the additional virtual switch was configured through Hyper-V Manager (which was done on all three hosts).   However the cluster only sees our 2nd virtual switch on one host   I cannot find a way to make the 2nd switch cluster aware.

The issue I have is that when I move a VM between hosts I need to disable networking on the VM or the move fails with the following error:

 “Cluster resource 'Virtual Machine Test-2008R2-1' of type 'Virtual Machine' in clustered role 'Test-2008R2-1' failed. The error code was '0x80004005' ('Unspecified error').”  

After many hours of research, my question is what is the best way to set up a Hyper-V Cluster with multiple VLAN’s?  Through switch port trucking and making the VM’s VLAN aware or through making virtual switches Cluster aware?

Thanks for your help,
LVL 1
imalc3142Asked:
Who is Participating?
 
davorinCommented:
In similar configuration we are using port trunking on physical NICs and specifying VLANs on VM NICs.
0
 
imalc3142Author Commented:
Is that working with NIC Teaming?
0
 
davorinCommented:
Yes, we are using Windows 2012 NIC teaming on HP blade servers.
3-rd party NIC teaming software is not officially supported.
0
 
imalc3142Author Commented:
Thanks for your help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.