Mirror feature doesn't sync automatically?

[anton (staff)]

...and we still can provide you with ftp server access for upload Just e-mail either zipped logs or your decision to support@starwindsoftware.com for assistance. Thank you for cooperation!

[basscom]

Zipped log file has been sent to support@starwindsoftware.com.

Please let me know your findings as I am anxious to resolve this.

Thank you.

[anton (staff)]

Got the stuff from you, checking what's wrong... We'll keep you updated! Thank you for your patience!

Zipped log file has been sent to support@starwindsoftware.com.

Please let me know your findings as I am anxious to resolve this.

Thank you.

[@ziz (staff)]

Zipped log file has been sent to support@starwindsoftware.com.

Please let me know your findings as I am anxious to resolve this.

Thank you.

We reviewed your logs.
The problem is that the client is sending data packets of size 512kB.
StarPort, which is being used to send data to remote mirror, has maximum data packet size of 256kB.
You must limit the maximum data packet size on the client initiator.
How to do it for MS iSCSI Initiator or StarPort:
http://www.starwindsoftware.com/forums/ ... t1089.html

[basscom]

StarPort parameters were checked in the registry for both StarWind hosts and the MaxBufferSize was already set to 262144 (256kB). Here is what I've tried so far as suggested in the topics linked in this thread:

StarWind server registry:
(searched for MaxBurstLength and changed the values below in 3 different locations)

MaxBurstLength - 0x00040000 (262144)
MaxRecvDataSegmentLength - 0x00040000 (262144)
MaxTransferLength - 0x00100000 (1048576)

Confirmed this value was already set to 256kB on both StarWind servers:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StarPort\Parameters]
MaxBufferSize - 0x00040000 (262144)

StarWind management console:

Max Burst Length - 262144
Max Receive Data Segment Length - 1048576

XenServer 5.6 FP1 console:

Edited /etc/iscsi/iscsid.conf:

maxburstlength - 65536
maxreceivedatasegment - 131072

Added node.conn[0].tcp.window_size = 65536


Rebooted all servers and recreated RAID-1 Mirror device in StarWind console. Verified that the mirror is functioning normally (synchronizing) when data is written to it with an iSCSI connection from a Windows server. So mirroring is working!

Created new iSCSI storage connection in XenCenter and verified that the new iscsid.conf values were passed through to /etc/iscsi/nodes/[my iqn]/[my ip]/default.

Created 2 new virtual disks on iSCSI storage from XenCenter. StarWind console shows mirror unsynchronized seconds after creating virtual disks. Forcing 'Check and Synchronize Mirror' works, but as soon as any data is changed on iSCSI storage again (like creating new virtual disks) the mirror becomes unsynchronized.

I'm coming to the end of the road here. If StarWind cannot provide me with a solution this week I will have to abandon this prodcut, which is unfortunate as I planned on selling this to my customers.

Please check over all the changed values I listed above and provide me with feedback soon.

Thank you.

[Alex Satler (staff)]

Dear basscom,
Thank you for contacting us via Forum.

As I am concerned, Basscom is a partner of StarWind Software Inc. and you have a direct channel to get support from StarWind.

By going through a proper channel, you will get a timely response to all of your questions.

Please log in into your partner portal - http://var.starwindsoftware.com/, click "Support" tab and choose "Log a support case"

If it's a pre-sale case, please be sure to register this deal with StarWind in order to get a support. If it's a post sale case, please provide us with Purchase Reference number.

Only in such case, we may guarantee you a good quality, timely response!

You may contact me directly via email: alex.satler@starwindsoftweare.com should you have any additional questions.

It would be my pleasure to further assist you!

[basscom]

Problem resolved! Required changing the MaxBufferSize StarPort parameter to 512kB (524288).

Here is a revised list of values to change or confirm for StarWind 5.6 and XenServer 5.6 FP1 compatibility:

StarWind server registry:
(search for MaxBurstLength and change the values below in 3 different locations)

MaxBurstLength - 0x00040000 (262144)
MaxRecvDataSegmentLength - 0x00040000 (262144)
MaxTransferLength - 0x00100000 (1048576)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StarPort\Parameters]
MaxBufferSize - 0x00080000 (524288)

StarWind management console:

Max Burst Length - 262144
Max Receive Data Segment Length - 1048576

XenServer 5.6 FP1 console:

Edit /etc/iscsi/iscsid.conf:

node.session.iscsi.MaxBurstLength = 65536

Add to iscsid.conf:

node.conn[0].tcp.window_size = 65536

[Anatoly (staff)]

Good to hear that!:)

Fell free to contact support again in case of need (if hope there will be no such )