StarWind Software

I'm 99.9% sure I know the answer to this question but I just want to double check...

When I'm looking at the iSCSI sessions for a target, you'll see the sessions for each of the nodes, then on some targets you'll see connection to VMware servers ---
I'm assuming that means that particular target on that particular node is the one actually serving up that particular disk --- correct?

I was also curious - is there a way to "move" which node is serving up the disk?

Since I have three nodes and three disks - would it make sense to have one node each serving one of the disks?
For example: Node A has Disk 1; Node B has Disk 2; Node C has Disk 3...

Hello, kb9jlo, thank you for your question. Yes, you are right, these are connections to the host. As I see you have 2 iSCSI connections to DECSESXi11, and 1 to DECSESXi10 and DECSESXi12. Could you please clarify if you are using hyper-converged infrastructure?

Sergey (staff) wrote:Hello, kb9jlo, thank you for your question. Yes, you are right, these are connections to the host. As I see you have 2 iSCSI connections to DECSESXi11, and 1 to DECSESXi10 and DECSESXi12. Could you please clarify if you are using hyper-converged infrastructure?

I'm never quite sure what you mean by "hyper-converged"...

I have three Starwind nodes (MS Server 2016 VM's) each on a VM host. Three nodes, three hosts.
Each node has (3) disks, each approx. 6 TB and since there are 3 nodes that's 3 copies. I use Infiniband 10GbE cards for sync & heartbeat.

I was looking in VMware vCenter today and in HA I can see who has control of the cluster and I think I can see who has what disks... Not sure what all I'm seeing, of course the master was easy to figure out.

You can distribute VMs between available compute resources (hosts) using vMotion. You have to assign a network interface for vMotion on each node. Check this video from VMware:
https://www.youtube.com/watch?v=oMQFH8dQGfA
Please note, virtual disks must be Thick Provision Eager Zeroed in order to enable clustering features.