VMware see 2 targets as Multipath when they are not

[dahlia]

VMware see 2 targets as Multipath when they are not
I have install StarWind 5.4 trial version, and test with ESXi 4.1, I create 2 targets with "Disk Bridge" on both of them. The targets come from the same controller. When I add the server into ESXi, I can see only 1 device but 2 paths. ESXi think that the 2 targets are the same, but they are not. They are 2 different drive. They are even different size. Please give me any suggestion if I have set anything wrong.
Thank you very much.

[anton (staff)]

1) You play with the outdated version. We have published 5.5 gold quite a time ago (with 5.6 replacing it soon). So doing anything with 5.4 is far from the best idea.

2) You create two devices (different) with identical IDs. That's why VMware ESX (and anybody else on Earth) will think it's actually one device and multiplath configured. So you can either set device serial ID manually or just send us StarWind configuration files so we could check why it happened (b/c serials should not be the same).

[hans.zel]

Hola!

Have the same problem: two disks are being seen as one with different paths in ESX 4.1

Hardware: hp MSA1000 connected to a hp dl380g3 with win2008x86 by fc; one array with 14 physical drives and two logical drives. Starwind 5.5.1638
Logical drives are configured by native hp array configuration utility:
first one

Status OK
Drive Number 1
Drive Unique ID 600805F300078B70AD7E73BBD6750018
Size 871192 MB
Fault Tolerance RAID 1+0
Heads 255
Sectors/Track 32
Cylinders 65535
Strip Size 128 KB
Array Accelerator Temporarily Disabled
Disk Name \\.\PhysicalDrive1

second one

Logical Drive
Status OK
Drive Number 3
Drive Unique ID 600805F300078B70AE27716CF720001D
Size 890880 MB
Fault Tolerance RAID 5
Heads 255
Sectors/Track 32
Cylinders 65535
Strip Size 64 KB
Array Accelerator Temporarily Disabled
Parity Initialization Status In Progress
Disk Name \\.\PhysicalDrive3

target one:
target name = iqn.2008-08.com.starwindsoftware:127.0.0.1-vmclu1
device name = \\?\scsi#disk&ven_compaq&prod_msa1000_volume#4&232fafe&0&000001#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
target two:
target name = iqn.2008-08.com.starwindsoftware:127.0.0.1-stages
device name = \\?\scsi#disk&ven_compaq&prod_msa1000_volume#4&232fafe&0&000003#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

ESX works perfectly with the first one. But when I try to add one more disk, I have disks with the same device eui: eui.1e313422a9e9f99f

iqn.1998-01.com.vmware:vs07-43ab4c47-00023d000001,iqn.2008-08.com.starwindsoftware:127.0.0.1-stages,t,-1-eui.1e313422a9e9f99f
Runtime Name: vmhba34:C0:T1:L0
Device: eui.1e313422a9e9f99f
Device Display Name: COMPAQ iSCSI Disk (eui.1e313422a9e9f99f)
Adapter: vmhba34 Channel: 0 Target: 1 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:vs07-43ab4c47
Target Identifier: 00023d000001,iqn.2008-08.com.starwindsoftware:127.0.0.1-stages,t,-1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:vs07-43ab4c47
Target Transport Details: IQN=iqn.2008-08.com.starwindsoftware:127.0.0.1-stages Alias= Session=00023d000001 PortalTag=1

iqn.1998-01.com.vmware:vs07-43ab4c47-00023d000001,iqn.2008-08.com.starwindsoftware:127.0.0.1-vmclu1,t,-1-eui.1e313422a9e9f99f
Runtime Name: vmhba34:C0:T0:L0
Device: eui.1e313422a9e9f99f
Device Display Name: COMPAQ iSCSI Disk (eui.1e313422a9e9f99f)
Adapter: vmhba34 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: iqn.1998-01.com.vmware:vs07-43ab4c47
Target Identifier: 00023d000001,iqn.2008-08.com.starwindsoftware:127.0.0.1-vmclu1,t,-1
Plugin: NMP
State: active
Transport: iscsi
Adapter Transport Details: iqn.1998-01.com.vmware:vs07-43ab4c47
Target Transport Details: IQN=iqn.2008-08.com.starwindsoftware:127.0.0.1-vmclu1 Alias= Session=00023d000001 PortalTag=1

[Max (staff)]

This is a VMware "feature"
You need to go to the starwind.cfg file (in the installation folder), find the devices you've created
(Will look like <device name="ImageFile0" target="img" file="My Computer\D\test.img" asyncmode="yes" clustered="no" readonly="no" CacheMode="wt" CacheSizeMB="300" CacheBlockExpiryPeriodMS="5000"/>)
and add a SerialId="1111111111111111" (sixteen dights) to the first device and SerialId="2222222222222222" to the second one.
should look like .........CacheMode="wt" Serial Id="1111111111111111" CacheSizeMB="300"........
After this save the cfg file, restart the starwindservice and do a rescan on the VMware side.