More on this... so, I've got the channel connection and buffer  
alignment issues resolved, I am not getting to login response on my  
target, without error, but I'm seeing this on the console of the  
OpeniSCSI / OFED iSER initiator:

iser: iser_connect:connecting to: 10.8.0.101, port 0xbc0c
iser: iser_cma_handler:event 0 conn ffff81023cf07480 id ffff810230a30e00
iser: iser_cma_handler:event 2 conn ffff81023cf07480 id ffff810230a30e00
iser: iser_create_ib_conn_res:setting conn ffff81023cf07480 cma_id  
ffff810230a30e00: fmr_pool ffff810247172340 qp ffff8102471c5400
iser: iscsi_iser_ep_poll:ib conn ffff81023cf07480 rc = 0
iser: iser_cma_handler:event 9 conn ffff81023cf07480 id ffff810230a30e00
iser: iscsi_iser_ep_poll:ib conn ffff81023cf07480 rc = 1
iser: iscsi_iser_conn_bind:binding iscsi conn ffff81022ec13290 to  
iser_conn ffff81023cf07480
iscsi_iser: datalen 262144 (hdr) != 5044 (IB)

It looks roughly to me that the initiator is not pleased with a  
datalen coming back from the target.  Is there some context to this,  
or shall I start looking at the code?

Thanks
Jesse


On Aug 20, 2008, at 11:21 AM, Jesse Butler wrote:

>
>
>
> Mike Christie wrote:
>> Jesse Butler wrote:
>>
>>> Erez Zilber wrote:
>>>
>>>> On Wed, Aug 20, 2008 at 12:04 AM, Jesse Butler <[EMAIL PROTECTED] 
>>>> > wrote:
>>>>
>>>>
>>>>> Ok, I've tried the configuration and login now whilst specifying  
>>>>> the
>>>>> TPGT.  I don't hit the same error now, but I do see this:
>>>>>
>>>>> # iscsiadm -m node -T
>>>>> iqn.1986-03.com.sun:02:aff22998-3466-4bf4-ee3c-958fd4b5d346 -p
>>>>> 10.8.0.6:3260 -l
>>>>> Login session [iface: default, target:
>>>>> iqn.1986-03.com.sun:02:aff22998-3466-4bf4-ee3c-958fd4b5d346,  
>>>>> portal:
>>>>> 10.8.0.6,3260]
>>>>> iscsiadm: initiator reported error (14 - iSCSI driver does not  
>>>>> support
>>>>> requested capability.)
>>>>> iscsiadm: Could not execute operation on all records. Err 107.
>>>>>
>>>>> So, progress!
>>>>>
>>>>> Here is the set of operations I performed.
>>>>>
>>>>> Thanks
>>>>> Jesse
>>>>>
>>>>>
>>>>> # iscsiadm -m node -T
>>>>> iqn.1986-03.com.sun:02:aff22998-3466-4bf4-ee3c-958fd4b5d346 -p
>>>>> 10.8.0.6:3260,1 -o new
>>>>> New iSCSI node [tcp: 
>>>>> [hw=default,ip=,net_if=default,iscsi_if=default]
>>>>> 10.8.0.6,3260,1
>>>>> iqn.1986-03.com.sun:02:aff22998-3466-4bf4-ee3c-958fd4b5d346] added
>>>>>
>>>>> # iscsiadm -m node -T
>>>>> iqn.1986-03.com.sun:02:aff22998-3466-4bf4-ee3c-958fd4b5d346 -p
>>>>> 10.8.0.6:3260,1
>>>>> node.name = iqn.1986-03.com.sun:02:aff22998-3466-4bf4- 
>>>>> ee3c-958fd4b5d346
>>>>> node.tpgt = 1
>>>>> node.startup = manual
>>>>> iface.hwaddress = default
>>>>> iface.iscsi_ifacename = default
>>>>> iface.net_ifacename = default
>>>>> iface.transport_name = tcp
>>>>> node.discovery_address = <empty>
>>>>> node.discovery_port = 0
>>>>> node.discovery_type = static
>>>>> node.session.initial_cmdsn = 0
>>>>> node.session.initial_login_retry_max = 4
>>>>> node.session.cmds_max = 128
>>>>> node.session.queue_depth = 32
>>>>> node.session.auth.authmethod = None
>>>>> node.session.auth.username = <empty>
>>>>> node.session.auth.password = <empty>
>>>>> node.session.auth.username_in = <empty>
>>>>> node.session.auth.password_in = <empty>
>>>>> node.session.timeo.replacement_timeout = 120
>>>>> node.session.err_timeo.abort_timeout = 10
>>>>> node.session.err_timeo.reset_timeout = 30
>>>>> node.session.iscsi.FastAbort = Yes
>>>>> node.session.iscsi.InitialR2T = No
>>>>> node.session.iscsi.ImmediateData = Yes
>>>>> node.session.iscsi.FirstBurstLength = 262144
>>>>> node.session.iscsi.MaxBurstLength = 16776192
>>>>> node.session.iscsi.DefaultTime2Retain = 0
>>>>> node.session.iscsi.DefaultTime2Wait = 2
>>>>> node.session.iscsi.MaxConnections = 1
>>>>> node.session.iscsi.MaxOutstandingR2T = 1
>>>>> node.session.iscsi.ERL = 0
>>>>> node.conn[0].address = 10.8.0.6
>>>>> node.conn[0].port = 3260
>>>>> node.conn[0].startup = manual
>>>>> node.conn[0].tcp.window_size = 524288
>>>>> node.conn[0].tcp.type_of_service = 0
>>>>> node.conn[0].timeo.logout_timeout = 15
>>>>> node.conn[0].timeo.login_timeout = 15
>>>>> node.conn[0].timeo.auth_timeout = 45
>>>>> node.conn[0].timeo.active_timeout = 5
>>>>> node.conn[0].timeo.idle_timeout = 60
>>>>> node.conn[0].timeo.ping_timeout = 5
>>>>> node.conn[0].timeo.noop_out_interval = 10
>>>>> node.conn[0].timeo.noop_out_timeout = 15
>>>>> node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072
>>>>> node.conn[0].iscsi.HeaderDigest = None,CRC32C
>>>>>
>>>>>
>>>> I think that this is the problem. iSER doesn't use
>>>> HeaderDigest/DataDigest. I strongly suggest that you use
>>>> iscsi_discovery which does all the work for you (including setting
>>>> HeaderDigest/DataDigest to "None").
>>>>
>>>> Erez
>>>>
>>>>
>>>>
>>> Hello Erez-
>>>
>>> The HeaderDigest setting here indicates a list of options [None,
>>> CRC32C].  If running on iSER, we'll negotiate to "None", and all  
>>> will be
>>> well.
>>>
>>> I would like to take your advice, but the distribution that I am  
>>> using
>>> does not have the iscsi_discovery with the "-t" option, so I just  
>>> used
>>> static.  It could be that what I'm running just won't work (we have
>>> discussed offline a known-to-work configuration, I will try  
>>> that).  As
>>> an aside, I think it's kinda nutty that there's a chance that the  
>>> RHEL
>>> 5.2 config doesn't work... since, eh, well it's ship
>>>
>>> There may be something else in the config, though.  I'm just  
>>> trying to
>>> figure out what this is:
>>>
>>> # iscsiadm -m node -T
>>> iqn.1986-03.com.sun:02:aff22998-3466-4bf4-ee3c-958fd4b5d346 -p
>>> 10.8.0.6:3260 -l
>>> Login session [iface: default, target:
>>> iqn.1986-03.com.sun:02:aff22998-3466-4bf4-ee3c-958fd4b5d346, portal:
>>> 10.8.0.6,3260]
>>> iscsiadm: initiator reported error (14 - iSCSI driver does not  
>>> support
>>> requested capability.)
>>> iscsiadm: Could not execute operation on all records. Err 107.
>>> #
>>>
>>
>> I think what Erez was saying, besides use iscsi_discovery, was that  
>> you
>> should set this to None and it should work. In the /var/log/ 
>> messages do
>> you also see:
>>
>>                 log_error("transport '%s' does not support "
>>                           "HeaderDigest != None", t->name);
>>
>> The iser driver does not support digests so we do not even try to
>> negotiate. We do not even try to login because the driver said it  
>> does
>> not support them. I guess a better option would be to just drop the  
>> user
>> requested param and do None for the user - will do that later.
>>
>> But you have to do that manually now by doing:
>>
>> iscsiadm -m node -T target -p ip:port -o update -n
>> node.conn[0].iscsi.HeaderDigest  -v None
>>
>> then retry and that error above will go away.
>>
>>>
>>
>
> Oh, Ok.  Yeah, that seems like a bug.  He should just pick the first
> acceptable value off the list ("None", in this case).
>
> This worked.  Thanks Erez for the suggestion, and Mike for the
> clarification.  I'm back to debugging now...
>
> Best
> Jesse
>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to