Hello,
I am trying Starwind iSCSI SAN for Hyper-V on a 2 node Hyper-V Cluster.
I have latest version of starwind and free Hyper-V 2008 R2 with the latest updates.
I've created 2 HA devices (images) on Starwind (1 for Quorum and 1 for the VM) on both nodes.
I've connected to these devices using iscsi initiator (iscsicpl) on both nodes with MPIO option enabled.Also run mpiocpl and enabled MPIO on both nodes.
So far so good, both devices are recognized on hyper-v cluster manager where I have enabled CSV.I created then a new HA virtual machine using the cluster manager.
Now the problem is that when I try to simulate a failure on the cluster for example shutting down the first node the clustered ip does not appear on-line on the second node.Instead when I try to shutdown cluster service on each node at a time the clustered ip appears on-line on the second one.
I first thought that it was a problem on the cluster configuration and I recreated it but with the same results.
Trying to troubleshoot I noticed that when i cold shutdown one node the iscsi initiator on the second node does not mount correctly the disks on starwind SAN.So if i go and press manually "Auto Configure" the disks then magically the cluster starts to work on the second node! Isn't this supposed to happen automatically? I mean Auto Configuring the disks after loss of one node?
One second thing I would like to ask is what happens if for some reason one of nodes goes down and I have just a node now for the cluster and the HA devices on starwind management console appear with red exclamation mark (broken).Is there a way to make them "on-line" without bringing up the second node to do a full sync?
Thank you
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software