Thank you @yaroslav! I have to say I am totally amazed at the time you have taken to help me with all this. I'm certainly becoming a fan of StarWind!

Got it, so I should have something like this: Node 1: Initiator IP: Default Target Portal IP: 127.0.0.1 / 3260 Initiator IP: 172.30.30.1 Target Portal IP: 172.30.30.2 Initiator IP: 172.30.31.1 Target Portal IP: 172.30.31.2 Node 2: Initiator IP: Default Target Portal IP: 127.0.0.1 / 3260 Initiator IP...

One more question, and then I think I'm good to release the cluster to test: since I'm using redundant iSCSI links on each node do I just add the additional IPs to the Target portals in the iSCSI Initiator Properties Discovery tab? So I would have on Node 1: Initiator IP: Default Target Portal IP: 1...

Absolutely beautiful, thank you! Plugged in my IPs and names and everything worked.

Thanks again! I actually reached out for a quote for the paid version yesterday and am waiting to hear back. I don't want to try the full trial until I have pricing since if vSAN fits my needs, but we can't afford the full version, I still want to move forward with the free version. I'm now running ...

Appreciate the help! I don't want to have just a single wire for the Sync and iSCSI channels. Can I have multiple wires with individual IPs? so my sync and HB targets would look something like: #primary node $syncInterface="#p2=172.30.20.3:3260,172.30.20.4:3260" -f $addr2, $hbInterface=&qu...

I'm in the process of evaluating vSAN (free for right now) for a new Hyper-V 2022 2-node cluster. I've been reading the quick start guides as well as these forums and can't quite grasp the best way to accomplish my goals. I have 2 identical servers each with two 2-port ConnectX-6 cards (4x 100GB por...