StarWind Software

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

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.

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?

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

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.

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

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

Were you able to connect the targets to ESXi?
I added the target to the ESX hosts, but rescan doesn't discover any disk

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.

Here some screenshot

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.

It's a fresh install

Disk are correctly created

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.