I recently setup a Hyper-V cluster on Windows Server 2008 R2. Live Migration & failover would not work. Quick Migration would work. I also could only see the CSV (Cluster Shared Volume) on one NODE at a time. I then noticed this error in the cluster event logs:
Cluster Shared Volume ‘Volume1’ (‘Cluster Disk 2’) is no longer available on this node because of ‘STATUS_BAD_NETWORK_PATH(c00000be)’. All I/O will temporarily be queued until a path to the volume is reestablished.
I set this cluster up with three networks 1. iSCSI 2. Heartbeat 3. Public; and a CSV on the iSCSI network for the virtual machines. After some research I discovered that you actually want “File and Printer Sharing for Microsoft Networks” and “client for Microsoft networks” enabled on your heartbeat network cards on all nodes in your cluster.
Now there is information out there saying that you need to disable “File and Printer Sharing for Microsoft Networks” and “client for Microsoft networks” on all network cards except for the ones connected to the public network when clustering in Windows. I found this to be true except when using CSV in a Hyper-V cluster. I have setup file server and print server clusters before this way and everything worked just fine. CSV requires the SMB (Server Message Block) protocol and this is enabled in Windows Server 2008 by making sure “File and Printer Sharing for Microsoft Networks” and “client for Microsoft networks” are checked.
More about the requirements for CSV can be found here: http://technet.microsoft.com/en-us/library/ff182358(WS.10).aspx
