200 Synchronization cannot be started because the nodes are not ready!

[iamGavinJ]

I have a HA device setup script which previously worked fine, but on the latest build it fails. It appears the IP/interface binding has a new bug which causes the heartbeat and sync to come from an interface which it should not.

My setup has two servers (2012r2 VMs running in Azure) with three interfaces bound in the following order.
1 – Management/domain/heartbeat
2 – Production traffic (added to the server’s “nolisten” list with $server.SetServerParameter("nolisten", xxx) powershell cmdlet)
3 – iSCSI sync traffic

Although my setup script specifies interfaces 1 and 3, I have to disable the second production interface In order to make the HA pair create and maintain sync.

If I use TCP View (https://docs.microsoft.com/en-us/sysint ... ds/tcpview) I can see each server attempting TCP connections to the other server’s 3260 port but from the second production interface which is incorrect.

[Sergey (staff)]

Hello, Gavin! We are trying to reproduce the issue now and as soon as we find a solution this thread will be updated.