Re: iSER login process

2008-10-17 Thread Jesse Butler

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 81023cf07480 id 810230a30e00
iser: iser_cma_handler:event 2 conn 81023cf07480 id 810230a30e00
iser: iser_create_ib_conn_res:setting conn 81023cf07480 cma_id  
810230a30e00: fmr_pool 810247172340 qp 8102471c5400
iser: iscsi_iser_ep_poll:ib conn 81023cf07480 rc = 0
iser: iser_cma_handler:event 9 conn 81023cf07480 id 810230a30e00
iser: iscsi_iser_ep_poll:ib conn 81023cf07480 rc = 1
iser: iscsi_iser_conn_bind:binding iscsi conn 81022ec13290 to  
iser_conn 81023cf07480
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
 

Re: iSER login process

2008-08-20 Thread Erez Zilber

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

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



Re: iSER login process

2008-08-20 Thread Jesse Butler



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 have yet to find it in the code (but I do have my day job).  If I 
don't hear anything, I'll just roll back to RHEL 5.2.

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
-~--~~~~--~~--~--~---



Re: iSER login process

2008-08-19 Thread Jesse Butler

I decided to go on ahead and update to these latest OpeniSCSI bits, but 
am having build issues.  Looks like redefines, which leads me to think 
I've maybe got things in the wrong order, or I'm pulling the wrong 
headers... but, I've no idea.

Know what to do about this?

make -C kernel
make[1]: Entering directory `/root/open-iscsi-2.0-870-rc1/kernel'
make -C /lib/modules/2.6.18-92.el5/build M=`pwd` KBUILD_OUTPUT=  V=0 modules
make[2]: Entering directory `/usr/src/kernels/2.6.18-92.el5-x86_64'
  CC [M]  /root/open-iscsi-2.0-870-rc1/kernel/scsi_transport_iscsi.o
In file included from 
/root/open-iscsi-2.0-870-rc1/kernel/scsi_transport_iscsi.h:34,
 from 
/root/open-iscsi-2.0-870-rc1/kernel/scsi_transport_iscsi.c:33:
/root/open-iscsi-2.0-870-rc1/kernel/open_iscsi_compat.h:156: error: 
conflicting types for 'is_power_of_2'
include/linux/log2.h:53: error: previous definition of 'is_power_of_2' 
was here
/root/open-iscsi-2.0-870-rc1/kernel/open_iscsi_compat.h:173: error: 
redefinition of 'shost_priv'
include/scsi/scsi_host.h:651: error: previous definition of 'shost_priv' 
was here
/root/open-iscsi-2.0-870-rc1/kernel/open_iscsi_compat.h:186: error: 
redefinition of 'scsi_set_resid'
include/scsi/scsi_cmnd.h:150: error: previous definition of 
'scsi_set_resid' was here
/root/open-iscsi-2.0-870-rc1/kernel/open_iscsi_compat.h:191: error: 
redefinition of 'scsi_get_resid'
include/scsi/scsi_cmnd.h:155: error: previous definition of 
'scsi_get_resid' was here
/root/open-iscsi-2.0-870-rc1/kernel/scsi_transport_iscsi.c: In function 
'__iscsi_unblock_session':
/root/open-iscsi-2.0-870-rc1/kernel/scsi_transport_iscsi.c:543: warning: 
unused variable 'ihost'
make[3]: *** 
[/root/open-iscsi-2.0-870-rc1/kernel/scsi_transport_iscsi.o] Error 1
make[2]: *** [_module_/root/open-iscsi-2.0-870-rc1/kernel] Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.18-92.el5-x86_64'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/open-iscsi-2.0-870-rc1/kernel'
make: *** [all] Error 2


Thanks!
Jesse


Mike Christie wrote:
 Jesse Butler wrote:
   
 (This could be a duplicate post, not sure.  I posted Friday, but am  
 not seeing it on the archive online, so resending.)

 Hello-

 We have an iSER implementation under way for Solaris, and have reached  
 the point where we are working on Open iSCSI and OFED  
 interoperability.  I am starting with testing the Linux initiator  
 (RHEL 5.2, OFED 1.3.1) against our Solaris iSER-enabled target, and  
 I'm not getting very far.

 Most of our testing thusfar has been via StaticConfig discovery.  I  
 see that OpeniSCSI does not support this, and thus I am attempting to  
 

 It does. You do
 iscsiadm -m node -T your_target -p ip:port -o new
 to create the basic config.
 Then do
 iscsiadm -m node -T your_target -p ip:port
 to see the settings.

 Then do:
 iscsiadm -m node -T your_target -p ip:port -o update -n name_of_setting 
 -v value_of_setting.

 I think you will at least want to change the transport and the digest 
 settings for iser.

   
 use SendTargets; I am running a SendTargets discovery session, and  
 then logging in manually to that node (iscsiadm -l).

 The connection is on IPoIB between the two nodes, but once discovery  
 is completed, it appears that the Linux node is configured to just use  
 the tcp transport - he is not attempting to use iSER at all.   
 Looking at the /etc/iscsi/nodes entry, iface.transport_name is tcp.

 

 Run
 iscsiadm -m node -T your_target -p ip:port -o update -n 
 iface.transport_name -v iser

 The transport_name setting may be different in different releases. We 
 have not got it set it yet.

 In
 http://www.open-iscsi.org/bits/open-iscsi-2.0-870-rc1.tar.gz
 you can just do
 iscsiadm -m discovery -t st -p ip:port -I iser

 and we assume you want to use the iser transport for all portals found. 
 In that release you can also pass in iser to
 iscsiadm -m node -T your_target -p ip:port -I iser -o new

 And a way to avoid all this, is using the method Erez suggested and use 
 the iscsi_discovery script which will do some magic probing and config 
 udpates for you.

 
   

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



Re: iSER login process

2008-08-18 Thread Jesse Butler


This is, if not exactly what I need, at least a lot of new info for  
me.  I haven't seen any of this in any of the Wiki's, READMEs or other  
sundry documents out there that describe configuring iSER.  Thanks  
very much, I'll see if this gets me going.

Best
Jesse

On Aug 17, 2008, at 1:40 PM, Mike Christie wrote:


 Jesse Butler wrote:

 (This could be a duplicate post, not sure.  I posted Friday, but am
 not seeing it on the archive online, so resending.)

 Hello-

 We have an iSER implementation under way for Solaris, and have  
 reached
 the point where we are working on Open iSCSI and OFED
 interoperability.  I am starting with testing the Linux initiator
 (RHEL 5.2, OFED 1.3.1) against our Solaris iSER-enabled target, and
 I'm not getting very far.

 Most of our testing thusfar has been via StaticConfig discovery.  I
 see that OpeniSCSI does not support this, and thus I am attempting to

 It does. You do
 iscsiadm -m node -T your_target -p ip:port -o new
 to create the basic config.
 Then do
 iscsiadm -m node -T your_target -p ip:port
 to see the settings.

 Then do:
 iscsiadm -m node -T your_target -p ip:port -o update -n  
 name_of_setting
 -v value_of_setting.

 I think you will at least want to change the transport and the digest
 settings for iser.

 use SendTargets; I am running a SendTargets discovery session, and
 then logging in manually to that node (iscsiadm -l).

 The connection is on IPoIB between the two nodes, but once discovery
 is completed, it appears that the Linux node is configured to just  
 use
 the tcp transport - he is not attempting to use iSER at all.
 Looking at the /etc/iscsi/nodes entry, iface.transport_name is tcp.


 Run
 iscsiadm -m node -T your_target -p ip:port -o update -n
 iface.transport_name -v iser

 The transport_name setting may be different in different releases. We
 have not got it set it yet.

 In
 http://www.open-iscsi.org/bits/open-iscsi-2.0-870-rc1.tar.gz
 you can just do
 iscsiadm -m discovery -t st -p ip:port -I iser

 and we assume you want to use the iser transport for all portals  
 found.
 In that release you can also pass in iser to
 iscsiadm -m node -T your_target -p ip:port -I iser -o new

 And a way to avoid all this, is using the method Erez suggested and  
 use
 the iscsi_discovery script which will do some magic probing and config
 udpates for you.

 


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



Re: iSER login process

2008-08-18 Thread Jesse Butler


Having some issues with SendTargets, so I've gone with this first  
example (static config), and am seeing some issues with the modify.

I am running the OpeniSCSI that comes with OFED 1.3.1. Should I move  
to another release, maybe?

/* create, no error */
# iscsiadm -m node -T iqn.1986-03.com.sun:02:aff22998-3466-4bf4- 
ee3c-958fd4b5d346 -p 10.8.0.6:3260 -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

/* dump the config */
# iscsiadm -m node -T iqn.1986-03.com.sun:02:aff22998-3466-4bf4- 
ee3c-958fd4b5d346 -p 10.8.0.6:3260
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
node.conn[0].iscsi.DataDigest = None
node.conn[0].iscsi.IFMarker = No
node.conn[0].iscsi.OFMarker = No

/* now, modify the transport (tcp to iser) */
# iscsiadm -m node -T iqn.1986-03.com.sun:02:aff22998-3466-4bf4- 
ee3c-958fd4b5d346 -p 10.8.0.6:3260 -o update -n iface.transport_name - 
v iser

/* no error, dump the config */
# iscsiadm -m node -T iqn.1986-03.com.sun:02:aff22998-3466-4bf4- 
ee3c-958fd4b5d346 -p 10.8.0.6:3260
iscsiadm: iface iter could not stat /etc/iscsi/nodes/iqn. 
1986-03.com.sun:02:aff22998-3466-4bf4-ee3c-958fd4b5d346/10.8.0.6,3260.
iscsiadm: Could not execute operation on all records. Err 19.

/* not sure what happened, but my 1 entry is now -1... with iser  
set as the transport_name */
# grep transport_name /etc/iscsi/nodes/iqn.1986-03.com.sun\: 
02\:aff22998-3466-4bf4-ee3c-958fd4b5d346/10.8.0.6\,3260\,-1/default
iface.transport_name = iser



On Aug 17, 2008, at 1:40 PM, Mike Christie wrote:


 Jesse Butler wrote:

 (This could be a duplicate post, not sure.  I posted Friday, but am
 not seeing it on the archive online, so resending.)

 Hello-

 We have an iSER implementation under way for Solaris, and have  
 reached
 the point where we are working on Open iSCSI and OFED
 interoperability.  I am starting with testing the Linux initiator
 (RHEL 5.2, OFED 1.3.1) against our Solaris iSER-enabled target, and
 I'm not getting very far.

 Most of our testing thusfar has been via StaticConfig discovery.  I
 see that OpeniSCSI does not support this, and thus I am attempting to

 It does. You do
 iscsiadm -m node -T your_target -p ip:port -o new
 to create the basic config.
 Then do
 iscsiadm -m node -T your_target -p ip:port
 to see the settings.

 Then do:
 iscsiadm -m node -T your_target -p ip:port -o update -n  
 name_of_setting
 -v value_of_setting.

 I think you will at least want to change the transport and the digest
 settings for iser.

 use SendTargets; I am running a SendTargets discovery session, and
 then logging in manually to that node (iscsiadm -l).

 The connection is on IPoIB between the two nodes, but once discovery
 is completed, it appears that the Linux node is configured to just  
 use
 the tcp transport - he is not attempting to use iSER at all.
 Looking at the /etc/iscsi/nodes entry, iface.transport_name is tcp.


 Run
 iscsiadm -m node -T your_target -p ip:port -o update -n
 iface.transport_name -v iser

 The transport_name setting may be different in different releases. We
 have not got it set it yet.

 In
 http://www.open-iscsi.org/bits/open-iscsi-2.0-870-rc1.tar.gz
 you can just do
 iscsiadm -m discovery -t st -p ip:port -I iser

 and we assume you