[stgt] iSER over iWARP

[Or Gerlitz]

On 01/10/2013 09:46, Sushma wrote:
> Yes, I'm able to ping/rping the target.
> I can also run tcp_bw and rc_bw tests using qperf.
> However, I'm not sure about the initiator. Does CentOS 6.4 OFED distribution have iSER initiator or open-iscsi with iSER support for iWARP?
>
> Thanks,
> Sushma
>
> On Sep 30, 2013, at 10:53 PM, Or Gerlitz <ogerlitz at mellanox.com> wrote:
>
>> On 30/09/2013 23:16, Sushma R wrote:
>>> Hi,
>>>
>>> We have two systems with Chelsio T3 RNICs configured for iWARP. We are
>>> able to run qperf tests to measure TCP and RC bandwidth/latencies.
>>> Now we are trying to configure iSER using iscsiadm and tgtadm.
>>>
>>> I configured a target as per the instructions in README.iser document.
>>>
>>> ./tgtadm --lld iser -m target -o new --tid 3 -T
>>> iqn.2013-10.com.example:chelsio.test3
>>> ./tgtadm --lld iser -m logicalunit -o new --tid 3 --lun 1 -b /dev/ram0
>>> ./tgtadm --lld iser -m target -o bind --tid 3 -I ALL
>>>
>>> However, when the initiator does the discovery, I get the following error:
>>> iscsiadm -m discovery -t sendtargets -p 10.196.86.102 -d 2
>>> iscsiadm: Max file limits 1024 4096
>>> iscsiadm: starting sendtargets discovery, address 10.196.86.102:3260,
>>> iscsiadm: connecting to 10.196.86.102:3260
>>> iscsiadm: connected local port 45758 to 10.196.86.102:3260
>>> iscsiadm: connected to discovery address 10.196.86.102
>>> iscsiadm: Connection to Discovery Address 10.196.86.102 failed
>>> iscsiadm: Login I/O error, failed to receive a PDU
>>>
>>>
>>> Could someone please provide inputs on what could be the issue?
>> You're failing on the discovery phase, which is conducted over plain tcp/ip, can you ping that address?
>>
>>

>> Yes, I'm able to ping/rping the target.

I see, can you run TCP (iperf/netperf) with address  10.196.86.102?! these two prints

> iscsiadm: Connection to Discovery Address 10.196.86.102 failed
> iscsiadm: Login I/O error, failed to receive a PDU

means that the iSCSI discovery session which was done over TCP failed, it has nothing to do with iser.

To understand more what is the exact failure from the initiator viewpoint, run iscsid in forground and ask it
to be verbose, e.g on one console do the following

$ killall -KILL iscsid
$ iscsid -f -d 127

and on a second  console do

$ iscsiadm -m discovery -t sendtargets -p 10.196.86.102 -d 2

Do you manage to work OK when the configured TGT target is TCP and not iSER e.g with --lld iscsi ?!

Or.


--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html