target and multipath

boris collin

unread,

Nov 12, 2018, 12:02:38 PM11/12/18

to esos-users

Hello,

I'am testing esos to expose some iscsi target to some solaris server.
All are vm for testing in virtual box isolated environment.

I try ctld of freebsd to.

I'm notice one difference that's seem missing in my esos target about multipath.

Under the solaris (11.4), I get disk information with the commande "prtconf -v".

With FreeBsd target, I have some usefull metadata about multipathing :

disk, instance #2

Driver properties:

name='ddi-dpofua-supported' type=boolean dev=none

name='ddi-failfast-supported' type=boolean dev=none

name='ddi-kernel-ioctl' type=boolean dev=none

name='fm-ereport-capable' type=boolean dev=none

name='inquiry-rpm' type=int items=1 dev=none

value=00000001

name='inquiry-serial-no' type=string items=1 dev=none

value='jbod1lun0'

name='pm-hardware-state' type=string items=1 dev=none

value='needs-suspend-resume'

name='device-nblocks' type=int64 items=1 dev=none

value=00000000006b3330

name='device-blksize' type=int items=1 dev=none

value=00000200

name='device-pblksize' type=int items=1 dev=none

value=00002000

name='device-optimal-io-granularity' type=int items=1 dev=none

value=00000000

name='device-lowest-aligned-lba' type=int items=1 dev=none

value=00000000

name='ddi-devid-registrant' type=int items=1

value=00000001

Hardware properties:

name='class' type=string items=1

value='scsi'

name='client-guid' type=string items=1

value='6a626f64312020204a424f4431206c756e30000000000000'

name='compatible' type=string items=4

value='scsiclass,00.vjbod1.plun-mix1-z1.r0001' + 'scsiclass,00.vjbod1.plun-mix1-z1' + 'scsiclass,00' + 'scsiclass'

name='ddi-retire-prevents' type=string items=1

value='open'

name='devid' type=string items=1

value='id1,sd@Tjbod1___JBOD1_lun0~~~~~~'

name='inquiry-device-type' type=int items=1

value=00000000

name='inquiry-product-id' type=string items=1

value='lun-mix1-z1'

name='inquiry-revision-id' type=string items=1

value='0001'

name='inquiry-source-pg' type=int items=1

value=00000000

name='inquiry-vendor-id' type=string items=1

value='jbod1'

Paths from multipath bus adapters:

Path 2: /iscsi/di...@0000iqn.2018-10.com.test:vbx.jbod10101,0

iscsi#0 (online)

name='wwn' type=string items=1

value='6a626f64312020204a424f4431206c756e30000000000000'

name='target' type=int items=1

value=00000029

name='lun' type=int items=1

value=00000000

name='target-port' type=string items=1

value='4000002a0000,iqn.2018-10.com.test:vbx.jbod1'

name='path-class' type=string items=1

value='primary'

Device Minor Nodes:

dev=(188,128)

dev_path=/scsi_vhci/disk@g6a626f64312020204a424f4431206c756e30000000000000:a

spectype=blk type=minor nodetype=ddi_block:fabric
...

But with an esos target, this is missing :

disk, instance #0

Driver properties:

name='ddi-dpofua-supported' type=boolean dev=none

name='ddi-failfast-supported' type=boolean dev=none

name='ddi-kernel-ioctl' type=boolean dev=none

name='fm-ereport-capable' type=boolean dev=none

name='inquiry-rpm' type=int items=1 dev=none

value=00003a98

name='inquiry-serial-no' type=string items=1 dev=none

value='1562b48f'

name='pm-hardware-state' type=string items=1 dev=none

value='needs-suspend-resume'

name='device-nblocks' type=int64 items=1 dev=none

value=00000000007fe000

name='device-blksize' type=int items=1 dev=none

value=00000200

name='device-pblksize' type=int items=1 dev=none

value=00000200

name='device-optimal-io-granularity' type=int items=1 dev=none

value=00000008

name='device-lowest-aligned-lba' type=int items=1 dev=none

value=00000000

name='ddi-devid-registrant' type=int items=1

value=00000001

Hardware properties:

name='class' type=string items=1

value='scsi'

name='client-guid' type=string items=1

value='0'

name='compatible' type=string items=4

value='scsiclass,00.vSCST_BIO.pesos1_raid.r330' + 'scsiclass,00.vSCST_BIO.pesos1_raid' + 'scsiclass,00' + 'scsiclass'

name='devid' type=string items=1

value='id1,sd@x3135363262343866'

name='inquiry-device-type' type=int items=1

value=00000000

name='inquiry-product-id' type=string items=1

value='esos1_raid'

name='inquiry-revision-id' type=string items=1

value='330'

name='inquiry-source-pg' type=int items=1

value=00000000

name='inquiry-vendor-id' type=string items=1

value='SCST_BIO'

name='lun' type=int items=1

value=00000000

name='target' type=int items=1

value=0000000e

name='target-port' type=string items=1

value='4000002a0000,iqn.2018-11.esos.san1:99f20'

Device Minor Nodes:

dev=(188,0)

dev_path=/iscsi/di...@0000iqn.2018-11.esos.san1%3A99f200001,0:a

spectype=blk type=minor nodetype=ddi_block:fabric

dev_link=/dev/dsk/c2t0d0s0

dev_path=/iscsi/di...@0000iqn.2018-11.esos.san1%3A99f200001,0:a,raw

spectype=chr type=minor nodetype=ddi_block:fabric

dev_link=/dev/rdsk/c2t0d0s0

I'am new about iscsi.

Is it possible to enable these information from an esos target ? How could I do ?

Marc Smith

unread,

Nov 12, 2018, 3:34:18 PM11/12/18

to esos-...@googlegroups.com

Hi,

FreeBSD was what started it all for me in my career, but I honestly
have no experience with using SAN volumes and multipath I/O in FreeBSD
(or any BSD). If you have only one path to the ESOS storage array,
then I probably wouldn't expect to see any multipath information...
but that is just a generalization. Sorry!

--Marc

> --
> You received this message because you are subscribed to the Google Groups "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

boris collin

unread,

Nov 13, 2018, 4:10:53 AM11/13/18

to esos-users

Ok, but how configure a multipath between to host.

In my demo environment, esos server has two ip : 192.168.10.11 and 192.168.56.11, and the initiator solaris server can access both.
But I don't succeed configure it to have the "multipath" block above...

How to configure a multipath in this case ?

dev_path=/iscsi/disk@0000iqn.2018-11.esos.san1%3A99f200001,0:a

spectype=blk type=minor nodetype=ddi_block:fabric
dev_link=/dev/dsk/c2t0d0s0

dev_path=/iscsi/disk@0000iqn.2018-11.esos.san1%3A99f200001,0:a,raw

spectype=chr type=minor nodetype=ddi_block:fabric
dev_link=/dev/rdsk/c2t0d0s0

Marc Smith

unread,

Nov 13, 2018, 9:59:36 AM11/13/18

to esos-...@googlegroups.com

I would create two iSCSI target interfaces. I would then configure
(from shell) the allowed_portals attribute in SCST which limits an
iSCSI target interface to a specific IP address (search list of
details on how to configure).

Then create a security group on both iSCSI targets, then map your SCST
device as a LUN to both groups. Then from your initiator, login to
both portals/targets.

--Marc

>> dev_path=/iscsi/di...@0000iqn.2018-11.esos.san1%3A99f200001,0:a

>> spectype=blk type=minor nodetype=ddi_block:fabric
>> dev_link=/dev/dsk/c2t0d0s0

>> dev_path=/iscsi/di...@0000iqn.2018-11.esos.san1%3A99f200001,0:a,raw

>> spectype=chr type=minor nodetype=ddi_block:fabric
>> dev_link=/dev/rdsk/c2t0d0s0
>>
>>
>>
>> I'am new about iscsi.
>>
>> Is it possible to enable these information from an esos target ? How could I do ?
>>
>>

Reply all

Reply to author

Forward