How do I configure virtual machine networks as a highly available resource in a Hyper-V failover cluster?
Posted on 2010-11-23
I have created a Hyper-V failover cluster and I have a question about virtual machine networks and ensuring the cluster fails over the VMs to another node when a network connection for a VM network goes down.
My experience tells me that if I rip out a network cable from a NIC designated as a virtual machine network, the cluster does not fail over the VMs. Rather, the cluster maintains its current status and the VM just goes offline. I find this strange and don't understand the design decision behind it. I would think networks dedicated to VM traffic would be cluster resources and cause the cluster to failover if they go down.
How do I set things up such that if a physicial adapter devoted to VM traffic goes "down", the vms fail to another cluster node? By default, when you use SCVMM to configure a virtual machine network and attach it to a physical nic, that network doesn't appear as a cluster resource.
I suppose a way to ensure redundancy would be to attach each VM to two virtual machine networks and use the bridging functionality within the VM itself but that seems a bit cheesy and not quite enterprise-class.
Any input on this would be helpful.