A. The scenario here is you have a cluster of Hyper-V servers that have multiple network cards connected to different subnets. Each Hyper-V server has multiple virtual switches configured. You have these virtual switches configured on each node in the cluster.

Remember that Hyper-V clusters require the virtual switches on all nodes in the cluster to have identical names. Hyper-V doesn't have to do any clever logic to ascertain which virtual switch it should connect the virtual NIC from a virtual machine to. Hyper-V just connects the virtual NIC to the virtual switch that has the same name as the virtual switch it was connected to on the previous node.

Related Reading:
  • Q. How can I add virtual machines (VMs) to the Hyper-V console?
  • Q. What is the processor compatibility setting in Hyper-V R2?
  • Q. Does Hyper-Threading affect Hyper-V?
  • Virtualization Shootout: Hyper-V vs. ESX Server 3.5


  • Check out hundreds more useful Q&As like this in John Savill's FAQ for Windows. Also, watch instructional videos made by John at ITTV.net.