Error at Replication stage

[Kishore CA]

Hello Team,

Setup:
> I have 2 Node vSphere Cluster.
> I have deployed "Starwind Vsan" in both the vSphere Host and configured as per the link https://www.starwindsoftware.com/resour ... r-vsphere/
> StarWind Management is on VM in same cluster with widows server 2019.

Error:
> At Replication stage I'm getting n error saying "200 Failed: Synchronization Failed" "Couldn't send the command to partner node".

Kindly help me out.

This is the first time i'm trying StartWind.

Regard,
Kishore CA

[yaroslav (staff)]

Welcome to StarWind Forum. Please make sure the replication links are set as described here https://forums.starwindsoftware.com/vie ... p+3#p31505.

[FlashMe]

Hello KIshore CA,

please confirm following situation:

• You are using VMware vSphere as Hypervisor (Not Hyper-v):
• You are using StarWind Appliance for vSphere?:
• You are using StarWind VSAN inside Windows VM on top of VMware vSphere?:
• StarWind Management Console is installed on seperate Server which has connection management interfaces:

Best regards

[Kishore CA]

Hi,

• You are using VMware vSphere as Hypervisor (Not Hyper-v):
> Yes, i'm using VMware vSphere as Hypervisor

• You are using StarWind Appliance for vSphere?:
> Yes, I have deployed StarWind Virtual SAN (OVF) i.e. CentOS package in both ESXi Host. I have downloaded OVF Package using link https://www.starwindsoftware.com/releas ... re-vsphere

• You are using StarWind VSAN inside Windows VM on top of VMware vSphere?:
> No

• StarWind Management Console is installed on seperate Server which has connection management interfaces:
> Im using windows server 2019 VM on same vSpjhere for StarWind Management Console (with trial license).


Regards,
Kishore CA

[yaroslav (staff)]

It can be script configured wrong. Please see more tips in the link in my comment above.

[FlashMe]

@yaroslav: Customer is using vSphere not Hyper-v. The link is for hyper-v..

@KIshore CA: Building Process of StarWind VSAN is really simple if you build up the ESXi Nodes and networking correctly.

Please check following:

Go to your VSA Appliance via Browser: https://"ipaddressofyourvsa":9090 login an open the terminal. Try to ping every sync interface ip of your partner node.Are they reachable ? If not: Theres the problem and some misconfiguration in vSphere and networking.

If you like you can write me a DM and i will try to answer your questions. But im working in germany so replies will be a little bit delayed.

Best regards.

[yaroslav (staff)]

@FlashMe

Thank you for your suggestions.
The VSA scripts are the same and their logic is the same. It is likely the script is not set up correctly. Based on my experience, this is the most common cause for sync not running in free version:)
You are right, it might also be an MTU-related issue, yet simple pinging might not reveal the problem as packets will be fragmented.

[Kishore CA]

Hi,
I have configured using script initially I faced same problem. Presently I’m using trial version with GUI even now I’m getting same error.

Ping check between VMs for both Sync IP and also Hearbeat IP is ok..

In respect to MTU i have set 9000 in both VMs but I need to check Switch configuration.

I will check and confirm the MTU settings in switch and confirm…

[Kishore CA]

Welcome to StarWind Forum. Please make sure the replication links are set as described here https://forums.starwindsoftware.com/vie ... p+3#p31505.

Yes sir replication links are set as described. But for heartbeat I have used only one 10G link adapter but in the script you have mentioned 2 IP that is the only difference I have noticed sir ..

[yaroslav (staff)]

The script implies setting opposite IP addresses (i.e., "local" IPs for partner 1 are to be set in partner 2's fields and vice versa).
Please try setting MTU to 1500 for the entire network stack.

[Kishore CA]

After changing to MTU 9000 in switch it has worked but later finding issue in synchronization.

I have uploaded the logs kindly check and help me out.

Replication_Manager_2.JPG (51.02 KiB) Viewed 24040 times

Replication_NW_Setting.JPG (42.55 KiB) Viewed 24040 times

VM2_Sync Command.JPG (17.42 KiB) Viewed 24040 times

[yaroslav (staff)]

Changing MTU brings down the network interface. Please make also sure to align the MTU value on the entire network stack.
Please restart StarWindService on the not synchronized node.
Also, make sure network redundancy requirements are met https://www.starwindsoftware.com/system-requirements. If there are no direct links in your system, make sure to have redundant switches or consider plugging synchronization directly.
Please also avoid traffic mixing on physical interfaces (i.e., use dedicated links for iSCSI and Synchronization). See more at https://www.starwindsoftware.com/best-p ... practices/

[Kishore CA]

Hi all,
Thanks for every one for the support.
Finally it worked.

As per the procedure (https://www.starwindsoftware.com/resour ... r-vsphere/) i have attached RAID Disk has VMWare Datastore and then added has a disk to individual StarWind vSAN VMs, it dint work. But later i have attached directly RAID disk has RDM disk to each VMs and then it worked.


Thanks,

Regards,
Kishore CA

[yaroslav (staff)]

Hi,

Thanks for your update! I am glad to know that it works now.