beta3 can't add replication partner

[barrysmoke]

I'm having an issue getting a replication partner created on beta3. I've tried 10 times tonight to get it to work, and I keep getting the same error on the screen. The only difference in this host, and my virtual hosts I've been using so far for testing is a dedicated network between the 2 hosts(with the network settings set to 10.0.0.1, and 10.0.0.2), and each host is pingable. main nics are 192.168.1.130, and 131.
I can ping .1 from .2, and .2, from .1...and same for .130, and 131.
I have no idea why I keep getting connection lost.
using the hosts independent of each other, I have no issues, only when adding a replication partner.
I tried adding the partner as the 10.x network, and the 192 network, no change in end result.
I tried setting 10.x network as both replication, and heartbeat, then heartbeat only on 192...
then I flipped it, no change.
both hosts have to be rebooted after the error, to become responsive again.

node1error.png (61.97 KiB) Viewed 3920 times

[barrysmoke]

I tried to use existing device, with the same error, connection lost

[Bohdan (staff)]

We need to check your StarWind logs from both nodes. Please e-mail those logs to "beta-testing@".

[barrysmoke]

I had been testing different subnets, and nic configurations. starwind discovered the issue was 2 default gateways, and their gui didn't handle the error/issue.
I believe they are going to look at handling the error, and I'll make sure I don't use 2 default gateways on starwind san configs.

[Bohdan (staff)]

Thank for keeping us updated.
Yes, I believe we'll find a way to handle such issues.