Alastair D'Silva schrieb: > Hi, > > I am experiencing a somewhat bizzare problem. When I try and access an > iSCSI device (Target is ISCSI Enterprise Target - > http://iscsitarget.sourceforge.net) on a target with multiple LUNs, the > requested LUN appears to be ignored, and I always end up accessing LUN 0 > (which is the lowest published LUN - I haven't tried yet removing it to > see what happens). > > I have tested the same server using Xen and the Linux open-iscsi > initiator successfully. > > Do you have any advice?
Just double-checked our implementation. We set the LUN correctly in the iSCSI PDUs (this is where it should be placed according to RFC3720 and the SCSI Architecture Model 2). However note that our LUN configuration parameter is a 64 bit number which is the encoded LUN value according to SAM-2. The reason for this is that we don't know which of the 4 addressing mathods defined in SAM-2 is supported/required by the target. For example the iSCSI Enterprise Target supports only 2 of the 4 addressing schemes. Simple rule of thumb (which works for most iSCSI targets, as they have less than 256 LUNs) is to multiply the desired LUN number with 256 to get the encoded LUN number. For details see section 4.9 in SAM-2 (draft version available for free on www.t10.org). Maybe we'll add support for specifying the unencoded LUN and the desired addressing method. But won't happen soon. -- Klaus Espenlaub InnoTek Systemberatung GmbH, http://www.innotek.de _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
