How to connect more than one target with same iscsi device?

[raytracy]

I have an iscsi NAS connected with ESX 4.0. It works fine when I have only one iscsi target (named LUN0).

Now I created another target named LUN1 in same NAS, but found there is no way to connect it from ESX.

ESX command vmkiscsi-tool -D vmhba36 listed the following:

=========Discovery Properties for Adapter vmhba36=========

iSnsDiscoverySettable : 0

iSnsDiscoveryEnabled : 0

iSnsDiscoveryMethod : 0

iSnsHost.ipAddress : ::

staticDiscoverySettable : 0

staticDiscoveryEnabled : 1

sendTargetsDiscoverySettable : 0

sendTargetsDiscoveryEnabled : 1

slpDiscoverySettable : 0

DISCOVERY ADDRESS : syno.point.com.tw

DISCOVERY ADDRESS : 192.168.15.252

STATIC DISCOVERY TARGET

NAME : LUN0-50G

ADDRESS : 192.168.15.252:3260

STATIC DISCOVERY TARGET

NAME : LUN1-50G

ADDRESS : 192.168.15.252:3260

===============================

I add new storage via VC Client by following click:

Configuration > Storage > Add Storage

It listed only LUN0, there is no LUN1.

in VC Client:

Configuration > Storage Adapters > vmhba36 (iSCSI software adapter) > Detail

It listed only one device which bond to my LUN0, but listed two paths: LUN0 and LUN1.

Is there any way to access LUN0 and LUN1 targets at the same time? or, Can I designate which target can be bind with vmhb36?

[AndreTheGiant]

Under iSCSI device in Storage Adapters, how much LUN do you see?

Andre

[raytracy]

I attached two picture, one shown the device tab, one shown path.

The second LUN are shown under path tab.

[AndreTheGiant]

Very strange.

You must see also LUN1.

Have you make a rescan on the ESX?

Andre

[raytracy]

It's truly strange as you said. I have it seems happened due to my low cost NAS (Synology) did not support full feature of iSCSI. Although I could create many iSCSI target with this NAS, but it looks like to report all targets as LUN number 0 or some thing similar as it. This implement has no problem with Windows iSCSI initiator, but become difference PATH with same LUN in ESX.

I have compare the implementation with another iSCSI target which implemented by Centos Linux platform. Since I may assign different LUN number in config file of Linux, ESX can identify it as difference devices without any problem.

[mouradb]

Heyy, Got the same Problem,

are you using Openfiler for storage? did you get around this?

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".