StarWind - Windows2003 & ESX 3.0.1 connection broken

[kenap62]

@ all

I did installed StarWind on one Windows 2003 server and created one conection on local host on port 3260. One of local hdd I did add as STPI shared SCSI device.
On the ESX I created connection to this shared iSCSI device and I can create VM on this LUN.
Some time later I saw that the connection on my Windows 2003 server ( Starwind Software ) not more connected. All icon are grey. I have to reconnect the conection. If the connection brokeb it's not possible for my to work or create some new VM on this volume.

I don't know why the connection goes broken.
Same issue I have if the Windows server had been rebootet. I did think the connection has to by connect automaticly .

What's wrong or waht I do false...

StarWind software are licenced.

Thanks for you help and I#m sorry for my bad english.

Peter

[anton (staff)]

Do not use SPTI and ESX. DiskBridge was specially designed to map whole disk. SPTI mode is not stable b/c of the issues in the ESX initiator.

[kenap62]

Anton

many thanks..

I changed to DiskBridge but I mean it's slower as by SPTI.

it will by faster if I using Linux?
At the moment I using Windows 2003 systen as iSCSI device.

Adapted U160 SCSI controller
1 GB network connection between ESX and W2k3 Server.


Peter

[anton (staff)]

Faster, slower... They are lalative numbers. Do you have *exact* ones?

Anton

many thanks..

I changed to DiskBridge but I mean it's slower as by SPTI.

it will by faster if I using Linux?
At the moment I using Windows 2003 systen as iSCSI device.

Adapted U160 SCSI controller
1 GB network connection between ESX and W2k3 Server.


Peter

[kenap62]

@Anton....

I checked and changed last days all setting ( SCSI Adapter & NIC ) and it is very fast now.

But one question I have again.

If I reboot my Windows 2003 with iSCSI RocketDivision Software the connection will not by connected automaticly.

How can I configure the service to connect my iSCSI automaticly.

Many fhanks

Peter

[anton (staff)]

Actually performance should drop like this (fastest -> slowest)

1) ImageFile (with enabled caching)
2) DiskBridge (as it uses async I/O and thus deserialized)
3) SPTI (as it's fully serialized)

So in your case if SPTI works faster - it's not normal...

Pretty easy - check the StarPort iSCSI PDF manuals about how to enable "Automount" in device options.

@Anton....

I checked and changed last days all setting ( SCSI Adapter & NIC ) and it is very fast now.

But one question I have again.

If I reboot my Windows 2003 with iSCSI RocketDivision Software the connection will not by connected automaticly.

How can I configure the service to connect my iSCSI automaticly.

Many fhanks

Peter