How To Configure Multiple Targets from Same iSCSI Host

[GoDanno]

Hello,

I have set up two targets from an iSCSI host using E-Open iSCSI R3 (150 & 100 GB).

In the VI Client (Host | Configuration | Storage Adapters), if I rescan the iSCSI Software Adapter after adding the second target at a later date, the details for the iSCSI Software adapter indicates that the capacity for both targets is 149.91 GB even though the second target is only 100 GB.

These are the details:

SCSI Target 1:

iSCSI Name - iqn.2007-03:iscsi.vmhost01

TargetLUNs - 1

Path - vmhba40:1:0

Canonical Path - vmhba40:1:0

Capacity - 149.91 GB

Lun - 0

SCSI Target 5:

iSCSI Name - iqn.2007-08:iscsi.target0

TargetLUNs - 1

Path - vmhba40:5:0

Canonical Path - vmhba40:1:0

Capacity - 149.91 GB

Lun - 0

The thing that I see as odd is that the Canonical Paths are identical. Is this normal? The problem is that when I go to the Storage (SCSI, SAN, and NFS) section and attempt to add storage, there is nothing listed on the Select Disk/LUN page of the Add Storage Wizard.

I cannot add the second target as storage. How can I do this?

I have a standalone ESX Server 3.0.2 Standard Edition (upgraded from 3.0.1) and CHAP Authentication is enabled.

Thanks,

Dan

[oreeh · Accepted solution]

Try presenting the second LUN as LUN 1 and not LUN 0.

(with some iSCSI implementations ESX needs different LUN numbers)

[cemetric]

Something is wrong in the setup.

iSCSI should have unique names containing reversed domain name...

iqn.2007-08.com.vmware:store1

for example, otherwise you'll get what I think you're seeing now ?

[GoDanno]

Try presenting the second LUN as LUN 1 and not LUN

0.

(with some iSCSI implementations ESX needs different

LUN numbers)

Thank you... This worked perfectly!

[oreeh]

You're welcome

[GoDanno]

Something is wrong in the setup.

iSCSI should have unique names containing reversed

domain name...

iqn.2007-08.com.vmware:store1

for example, otherwise you'll get what I think you're

seeing now ?

I forgot to mention in my earlier post the details for the adapter itself (vmhba40):

Model: iSCSI Software Adapter

iSCSI Name: iqn.1998-01.com.vmware:vmhost-73deaf28

This is in line with what you indicated. The problem was that I needed to present it as LUN 1 instead of LUN 0.

Thanks

[cemetric]

No problem, after taking another look at the config I kinda figured you'd probably had it setup correctly ...

I learned something new about iSCSI so it's a win win situation

[oreeh]

FYI: here's the reason for this.

If an iSCSI target doesn't present unique serials or invalid VPD pages you need different LUN numbers.

There's a good discussion about this ESX behavior on the iSCSI Enterprise Target mailing list.

[GoDanno]

Do you know where I can access this discussion? I didn't find any references to it on the Open-E web site. I reviewed their forum, but didn't find any such discussion.

[oreeh]

Try this one http://www.nabble.com/iSCSI-Enterprise-Target-f4401.html

or this one http://www.nabble.com/iscsitarget-devel-f4402.html