Synchronizing stucks at 0%

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

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

massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Fri Jun 04, 2021 2:08 pm

Hello,
I'm configuraing a 2 node HA with the free version of Starwind Linux Appliance.
Executing the script CreateHA_2.ps1 the synchronization stucks at 0%
Target and device seems to be correctly created in both nodes.
Here my file:

param($addr="192.168.0.31", $port=3261, $user="root", $password="starwind",
$addr2="192.168.0.41", $port2=$port, $user2=$user, $password2=$password,
#common
$initMethod="Clear",
$size=1024,
$sectorSize=512,
$failover=0,
#primary node
$imagePath="\mnt\disk1",
$imageName="disk1",
$createImage=$true,
$storageName="",
$targetAlias="sw-vsa01",
$autoSynch=$true,
$poolName="vsan",
$syncSessionCount=1,
$aluaOptimized=$true,
$cacheMode="none",
$cacheSize=128,
$syncInterface="#p2=192.168.1.21:3260" -f $addr2,
$hbInterface="#p2=192.168.2.21:3260" -f $addr2,
$createTarget=$true,
#secondary node
$imagePath2="\mnt\disk1",
$imageName2="disk1",
$createImage2=$true,
$storageName2="",
$targetAlias2="sw-vsa02",
$autoSynch2=$true,
$poolName2="vsan",
$syncSessionCount2=1,
$aluaOptimized2=$false,
$cacheMode2=$cacheMode,
$cacheSize2=$cacheSize,
$syncInterface2="#p1=192.168.1.11:3260" -f $addr,
$hbInterface2="#p1=192.168.2.11:3260" -f $addr,
$createTarget2=$true
)

Thanks in advance
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Fri Jun 04, 2021 2:13 pm

For completetion I add this information:
192.168.0.x is my mangement network
192.168.1.x is synchronization network
192.168.2.x is iSCSI\heartbeat network
Testing the same configuration with a trial license works great.
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Fri Jun 04, 2021 2:20 pm

Welcome to StarWind Forum. Did you create the device in the Trial license with the script too?
Were you able to connect the targets to ESXi?
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Fri Jun 04, 2021 3:57 pm

No, in the trial license I create the device with the management tool.
I tried the script but it failed with the same result: synchronization at 0%
At the moment I haven't try to connect the created target in ESXi, but I will update as soon as possible
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Sat Jun 05, 2021 3:17 am

Thanks, please keep me posted. Please make sure to have at least one IP from a different card.
How to use multiple IPs? See this guide viewtopic.php?f=5&t=5624&p=31505&hilit=tip+3#p31505.

Let me know if you have more questions.
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Mon Jun 07, 2021 1:15 pm

I obtain this message on VSA1:

- Synchronization channel '192.168.1.21:3260'on 'iqn.2008-08.com.starwindsoftware:192.168.0.41-sw-vsa02' is down
- Hwartbeat channel '192.168.2.21:3260'on 'iqn.2008-08.com.starwindsoftware:192.168.0.41-sw-vsa02' is down
- Partner '192.168.1.21:3260'on 'iqn.2008-08.com.starwindsoftware:192.168.0.41-sw-vsa02' is not synchronized

and this in VSA2:
- Synchronization channel '192.168.1.11:3260'on 'iqn.2008-08.com.starwindsoftware:192.168.0.31-sw-vsa01' is down
- Hwartbeat channel '192.168.2.11:3260'on 'iqn.2008-08.com.starwindsoftware:192.168.0.31-sw-vsa01' is down
- Partner '192.168.1.11:3260'on 'iqn.2008-08.com.starwindsoftware:192.168.0.31-sw-vsa01' is not synchronized

Connecting with putty to VSA1 I can ping 192.168.0.41, 192.168.1.21 and 192.168.2.21
Connecting with putty to VSA2 I can ping 192.168.0.31, 192.168.1.11 and 192.168.2.11
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Mon Jun 07, 2021 1:31 pm

Network condfiguration is:
Management connected to a switch (192.168.0.11 for ESX-01, 192.168.0.21 for ESX-02, 192.168.0.31 for VSA-01 e 192.168.0.41 for VSA-02)
Sync interfaces (192.168.1.11 for VSA-01 and 192.168.1.21 for VSA-02) are connected with a cross cable
Heartbeat and iSCSI interfaces (192.168.2.11 for VSA-01 and 192.168.2.21 for VSA-02, 192.168.2.31 for ESX-01 e 192.168.2.41 fot ESX-02) are connected with a cross cable
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Mon Jun 07, 2021 1:37 pm

Were you able to connect the targets to ESXi?
I added the target to the ESX hosts, but rescan doesn't discover any disk
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Mon Jun 07, 2021 1:56 pm

Hi,

Are HA devices synchronized on both ends? Did you ran the rescan script? If so, did it ran smoothly in the VM (screenshot of the output will be much appreciated)?
Finally, if HA devices are synchroized and you are sure that the rescan script runs without any issues, disable network port bindng.
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Mon Jun 07, 2021 2:35 pm

VSA-01.png
VSA-01.png (32.99 KiB) Viewed 5171 times
Here some screenshot
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Mon Jun 07, 2021 2:35 pm

VSA-02.png
VSA-02.png (28.35 KiB) Viewed 5171 times
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Mon Jun 07, 2021 2:44 pm

Hi,

Is there any data on those disks or is it just a fresh install?
The disks were not created or are not visible to the system.
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Mon Jun 07, 2021 2:45 pm

It's a fresh install
massimo.favretto
Posts: 17
Joined: Mon May 10, 2021 2:29 pm

Mon Jun 07, 2021 2:55 pm

Disk are correctly created
Attachments
VSA-01_Disk.png
VSA-01_Disk.png (10.31 KiB) Viewed 5167 times
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Mon Jun 07, 2021 3:08 pm

StarWind VSAN does not see the disks. Share the StarWind.cfg with me from /opt/StarWind/StarWindVSA/drive_c/StarWind from both hosts together with .swdsk and _HA.swdsk headers.
Post Reply