StarWind Software

Hi,

i can't make Vmware Vsphere v 4.1 detect the "Starwind enterprice HA" target to detect it as a virtual Scsi storage.

could you please tell me the steps for doing that.

regards

Sure. At what step you're failing *EXACTLY*? You cannot create HA with StarWind? VMware initiator does not see StarWind managed LUNs? It does enumerate LUNs but fails to connect? It connects and works fine untill VM migration?

tarekff wrote:Hi,

i can't make Vmware Vsphere v 4.1 detect the "Starwind enterprice HA" target to detect it as a virtual Scsi storage.

could you please tell me the steps for doing that.

regards

Thanks for your reply.

i opened Starwind management console 5.5 and added a host and a target to this host
then i opened the VMware workstation v 7.1 and powered On the ESXi server.
then i opened vsphere client, connect to Esxi server then went to configuration, storage adaper, iscsi software adapter and enabled software intiator and add the starwind host IP as a send Target.

but the Vsphere client did not detect the ISCI of the starwind.

please help

OK, let us to check logs! You can find them in %Program Files%/StarWind Software/Starwind/logs and send to us. We`ll find what is causing the problem.

12/13 10:42:27.416 2f8 IMG: *** ImageDisk_LockVolumes: Volume '\\?\Volume{e987790f-ffea-11df-a32e-806e6f6e6963}' can not be locked (error 5)! The local system is using it.
12/13 10:42:27.416 2f8 IMG: *** ImageDisk_LockVolumes: '\\?\ide#diskwdc_wd2500bekt-60a25t1__________________02.01a02#5&320bde68&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}' can not be locked (error 5)!
12/13 10:42:27.416 2f8 IMG: *** ImageDisk_RegisterSession: Can't lock volumes for PhysicalDrive0!
12/13 10:42:27.416 2f8 Tgt: *ERROR* 'iqn.2008-08.com.starwindsoftware:legcai1041815.egcai.danet-vm4' can't register session. The device 'DiskBridge1' may be owned by a local process!
12/13 10:42:27.416 2f8 T[3,1]: *ERROR* Login request: device open failed.
12/13 10:42:27.416 17cc C[3], IN_LOGIN: Event - LOGIN_REJECT.

OK, I have edited your previous post a little bit and left only error messages. The reason of errors - you are trying to share system disk as is, while it`s by OS. Way out - use virtual disks aka images.

You are right.

i found the location of the problem.

i was adding a physical file not a virtual file as a target.

when i added a virtual one, vsphere detected it.

Thanks

Good. Thank you for keeping us updated.

tarekff wrote:You are right.

i found the location of the problem.

i was adding a physical file not a virtual file as a target.

when i added a virtual one, vsphere detected it.

Thanks