Starwind will not sync after upgrade

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
chell
Posts: 48
Joined: Mon Dec 11, 2017 1:19 am

Thu Nov 14, 2019 4:44 pm

Hi

I upgraded my startwind to 8.0.0.13279.
before the upgrade I had changed the starwind port to 3262. This was working before the starwind upgrade. Since the upgrade the nodes will not synchronize.

The node that has been marked as synchronized displays the error message that the other node is not synchronized. Under replication manager the synchronization channel and heartbeat channels have ticks and show the correct ip addresses and port.
The node that has not been marked as synchronized displays the error message that the device is not synchronized. It also reports that the heartbeat and synchronization channel is down. Under replication manager the synchronization channel and heartbeat channels have crosses. They show the correct IP addresses and port.
I've tried turning off firewalls.

I created a new device as a test. it create the device on the 2nd server but when it goes to synchronize for the first time i get the error "synchronization cannot be started because nodes are not ready, try to synchronize nodes manually. pending"

Any ideas?
Quadrocake
Posts: 1
Joined: Thu Nov 14, 2019 5:07 pm

Fri Nov 15, 2019 2:47 pm

It looks like your node that currently is synchronized have wrong StarWind network settings. Make sure that in starwind.cfg you have <Port value="3262"/> on both nodes.
But notice that StarWind currently have bug and you may have to readd your servers in management console with port 3263
chell
Posts: 48
Joined: Mon Dec 11, 2017 1:19 am

Sat Nov 16, 2019 5:47 pm

What are the default ports for starwind?
These are the ports that i have in the starwind.cfg
<BCastEnable value="yes"/>
<BCastInterface value="0.0.0.0"/>
<BCastPort value="3263"/>
<Port value="3262"/>
<listen value="*,"/>
<CtlPort value="3261"/>
Michael (staff)
Staff
Posts: 317
Joined: Thu Jul 21, 2016 10:16 am

Tue Nov 19, 2019 6:17 pm

Here is the default connections section in StarWind.cfg
<connections>
<!--Port number for iSCSI connections (default 3260)-->
<Port value="3260"/>
<!--Interface to listen to. "0.0.0.0" corresponds to "listen to all interfaces".-->
<Interface value="0.0.0.0"/>
<!-- Interface to listen to filtering by MAC-address. Default value is empty string.-->
<!-- It can be full MAC-address like "10-10-10-10-10-10" or partial template like "10-10-10*" -->
<!-- <InterfaceByMAC value=""/> -->
<!--Port number for Control connections (default 3261)-->
<!-- <CtlPort value="3261"/> -->
<!--Interface to listen to Control connections. "0.0.0.0" corresponds to "listen to all interfaces".-->
<!-- <CtlInterface value="0.0.0.0"/> -->
<!-- StarWind location protocol -->
<BCastEnable value="yes"/>
<BCastInterface value="0.0.0.0"/>
<BCastPort value="3261"/>
</connections>
chell
Posts: 48
Joined: Mon Dec 11, 2017 1:19 am

Wed Nov 20, 2019 9:24 am

Hi
I solved the problem. It was the Intel pro network card drivers.
Boris (staff)
Staff
Posts: 805
Joined: Fri Jul 28, 2017 8:18 am

Wed Nov 20, 2019 10:37 am

Thanks for updating the thread with the resolution. Great you were able to resolve this hardware fault.
Post Reply