Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Aug 2016 13:36:20 +0200
From:      Ben RUBSON <ben.rubson@gmail.com>
To:        "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org>
Cc:        Max Gurtovoy <maxg@mellanox.com>, Oren Duer <oren@mellanox.com>, Oded Shanoon <odeds@mellanox.com>, Meny Yossefi <menyy@mellanox.com>, Roy Shterman <roysh@mellanox.com>, Hans Petter Selasky <hanss@mellanox.com>
Subject:   Re: Help to make iSER working
Message-ID:  <AC9F5113-0909-4B90-9E89-8841F4060E2F@gmail.com>
In-Reply-To: <AM5PR0501MB2580F57429494795D97005E3C21F0@AM5PR0501MB2580.eurprd05.prod.outlook.com>
References:  <71E4886B-61C3-4091-A7FF-E5A4F59AEACE@gmail.com> <64d8bc44-b6a3-4c0a-6d13-f919bf26685a@mellanox.com> <41CCC244-A781-4087-A811-B33847EDEC01@gmail.com> <6a464f2c-c048-d29c-e602-c129b35a5d4a@mellanox.com> <B3B47B30-D253-4543-A813-1AEDD3EE2656@gmail.com> <a8b1cd70-3e96-2dd6-20ae-1bf3b315ff89@mellanox.com> <621BCC32-4612-410F-B658-D1086A7A3A09@gmail.com> <8207D6A0-3647-48B4-A4E0-3F1FCF3A6723@gmail.com> <beeb0b05-98a0-6c9b-cc37-fd9876477558@mellanox.com> <AM5PR0501MB2580F57429494795D97005E3C21F0@AM5PR0501MB2580.eurprd05.prod.outlook.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

I went with a fresh new install to have a clean status.

What I did :

// FreeBSD 11-RC1 installation
# echo "WITH_OFED=3DYES" > /etc/make.conf
# cd /usr/src/ ; make buildkernel KERNCONF=3DGENERIC ; make =
installkernel KERNCONF=3DGENERIC
# cd /usr/src/sys/modules/mlx4 ; make ; make install
# cd /usr/src/sys/modules/mlxen ; make ; make install
# cd /usr/src/sys/modules/iser ; make ; make install
# echo "mlx4_load=3DYES" >> /boot/loader.conf
# echo "mlxen_load=3DYES" >> /boot/loader.conf
# echo "iser_load=3DYES" >> /boot/loader.conf
# reboot

Everything went fine, no code modition needed or whatever, perfect.

# iscsictl -A -t iqn.2012-06.com.test:target1 -p 192.168.2.2
On the target, I get :
tgtd[1912]: tgtd: login_start(502) Target iqn.2012-06.com.test:target1 =
is RDMA, but conn cid:0 from iqn.1994-09.org.freebsd:srv1 is TCP
Perfect, the target is correctly iSER enabled.

# iscsictl -A -t iqn.2012-06.com.test:target1 -p 192.168.2.2 -r
I still get the following error :
iscsid[1062]: 192.168.2.2 (iqn.2012-06.com.test:target1): failed to =
connect to 192.168.2.2 using ICL kernel proxy: ISCSIDCONNECT: =
Input/output error
kernel: INFO: iser_free_ib_conn_res: freeing conn 0xfffff80147771000 =
cma_id 0 qp 0
kernel: DEBUG: iser_conn_connect: before cv_wait: 0xfffff80147771000
kernel: INFO: iser_cma_handler: event 1 status -19 conn =
0xfffff80147771000 id 0xfffff8005f0e5400
kernel: ERROR: iser_connect_error: conn 0xfffff80147771000
kernel: DEBUG: iser_conn_connect: after cv_wait: 0xfffff80147771000
iscsid[853]: child process 1062 terminated with exit status 1

Waiting for your instructions, would really be nice to have it working =
for 11 release.

Many thanks !

Best regards,

Ben



> On 12 Aug 2016, at 09:38, Hans Petter Selasky <hanss@mellanox.com> =
wrote:
>=20
> Hi,
>=20
> Error 19 means ENODEV. Possibly something is not supported.
>=20
> Meny: I wonder if it is better if Ben install our infiniband patches =
to bring the IB code up to v3.2?
>=20
> --HPS
>=20
> -----Original Message-----
> From: Max Gurtovoy=20
> Sent: Friday, August 12, 2016 1:51 AM
> To: Ben RUBSON <ben.rubson@gmail.com>; freebsd-scsi@freebsd.org
> Cc: Oren Duer <oren@mellanox.com>; Oded Shanoon <odeds@mellanox.com>; =
Meny Yossefi <menyy@mellanox.com>; Hans Petter Selasky =
<hanss@mellanox.com>; Roy Shterman <roysh@mellanox.com>
> Subject: Re: Help to make iSER working
>=20
> Hi,
>=20
> On 8/11/2016 11:43 PM, Ben RUBSON wrote:
>> Here are the tests with udaddy from FreeBSD, trying to connect to =
Linux :
>>=20
>> # udaddy -s 192.168.2.2
>> libibverbs: Warning: couldn't open config directory '/etc/ibverbs/'.
>> libibverbs: Warning: couldn't open config directory '/etc/ibverbs/'.
>> udaddy: starting client
>> udaddy: connecting
>> libibverbs: Warning: couldn't open config directory '/etc/ibverbs/'.
>> udaddy: event: RDMA_CM_EVENT_ADDR_ERROR, error: -19
>=20
> yes, you got the same event in iser (event 1).
> There is a configuration issue with your setup.
> Once you overcome this, iSER should work for you.
>=20
> Meny/Hans,
> can you assist here ?
>=20
> Thanks,
> Max.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AC9F5113-0909-4B90-9E89-8841F4060E2F>