Re: Debian Lenny; Kernel 2.6.26, Iser, Mellanox : iser_cma_handler:event: 3, error: -110

2008-08-20 Thread Dr. Volker Jaenisch

Hello Mike!

Mike Christie schrieb:
>> I used the following commands:
>>
>> tgtadm --lld iscsi --op new --mode target --tid 1 -T
>> de.inqbus.poseidon:disk1
>> tgtadm --lld iscsi --op bind --mode target --tid 1 -I 10.6.0.1
>> tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b
>> /dev/vg1/test
>> 
>
> Could you try a
> tgtadm --lld fcoe --op bind --mode target --tid 1 -I ALL
>   
./tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL

results in exactly the same behavior

Aug 20 14:44:51 hades kernel: [97036.613263] iser:
iser_connect:connecting to: 10.6.0.2, port 0xbc0c
Aug 20 14:44:51 hades kernel: [97036.616516] iser:
iser_cma_handler:event 0 conn 81000c513080 id 81000d8d1800
Aug 20 14:44:51 hades kernel: [97036.871932] iser: iscsi_iser_ep_poll:ib
conn 81000c513080 rc = 0
Aug 20 14:44:51 hades kernel: [97037.179318] iser: iscsi_iser_ep_poll:ib
conn 81000c513080 rc = 0
Aug 20 14:44:51 hades kernel: [97037.439327] iser: iscsi_iser_ep_poll:ib
conn 81000c513080 rc = 0
Aug 20 14:44:52 hades kernel: [97037.663318] iser:
iser_cma_handler:event 3 conn 81000c513080 id 81000d8d1800
Aug 20 14:44:52 hades kernel: [97037.663318] iser:
iser_cma_handler:event: 3, error: -110
Aug 20 14:44:52 hades kernel: [97037.703064] iser: iscsi_iser_ep_poll:ib
conn 81000c513080 rc = -1
Aug 20 14:44:55 hades kernel: [97041.675045] iser:
iscsi_iser_ep_disconnect:ib conn 81000c513080 state 4
Aug 20 14:44:55 hades kernel: [97041.675076] iser:
iser_conn_terminate:Failed to disconnect, conn: 0x81000c513080 err -22
Aug 20 14:44:55 hades kernel: [97041.675121] iser:
iser_free_ib_conn_res:freeing conn 81000c513080 cma_id
81000d8d1800 fmr pool 0
000 qp 

Any other ideas ?

Best regards

Volker

-- 

   inqbus it-consulting  +49 ( 341 )  5643800
   Dr.  Volker Jaenisch  http://www.inqbus.de
   Herloßsohnstr.12  0 4 1 5 5Leipzig
   N  O  T -  F Ä L L E  +49 ( 170 )  3113748



--~--~-~--~~~---~--~~
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: Debian Lenny; Kernel 2.6.26, Iser, Mellanox : iser_cma_handler:event: 3, error: -110

2008-08-19 Thread Mike Christie
Dr. Volker Jaenisch wrote:
> Hello Mike! 
> 
> Thanks for the fast reply!
> 
> Mike Christie schrieb:
>> volkerJaenisch wrote:
>>   
>>> Aug 20 01:17:52 hades kernel: [45569.481501] iser:
>>> iser_cma_handler:event: 3, error: -110
>>> 
>> On the target side are you running tgt with iscsi and iser at the same 
>> time? Did you make sure to make it so both targets have the proper 
>> access lists?
>>   
> Is there a magical switch to give different ACLs for iser and TCP transport?
> 
> How can I seperate the iscsi and the iser target ACLs? They are accessed
> via the same IP (IPoIB)

I think you do not have to. See below.

> As I understood (poorly) the matter the initiiator open-iscsi at first
> tries to discover the target(s) via IP.
> Then if it is told to (via -t iser) it tries to negotiate via iser
> transport. If this fails it tries TCP transport.
>> Or what tgtadm commands did you use to create the iser target or did you 
>> use the config script?
>>   
> I used the following commands:
> 
> tgtadm --lld iscsi --op new --mode target --tid 1 -T
> de.inqbus.poseidon:disk1
> tgtadm --lld iscsi --op bind --mode target --tid 1 -I 10.6.0.1
> tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b
> /dev/vg1/test

Could you try a
tgtadm --lld fcoe --op bind --mode target --tid 1 -I ALL

This would allow any initiator to log in. If that works then you would 
want to check out the tgt README.iscsi (I do not know where debian 
installs READMEs for its packages so I attached the upstream one for you 
and I think the commands will be the same) to see how to set the acls 
based on whaterver you want to do. I do remember how to set other values 
off the top of my head.

> 
> The initiator IP is 10.6.0.1.
> 
> Best Regards
> 
> Volker
> 


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

Preface
-
This show a simple example to set up some targets.


Starting the daemon
-
Try the following commands:

host:~/tgt$ su
host:~/tgt# ./usr/tgtd


Configuration
-
Everyting is configured via the tgtadm management tool.

The following example creates a target with id 1 (the iqn is
iqn.2001-04.com.example:storage.disk2.amiens.sys1.xyz) and adds a
logical unit (backed by /dev/hdc1) with lun 1.

Let's create one target devce.

host:~/tgt$ su
host:~/tgt# ./usr/tgtadm --lld iscsi --op new --mode target --tid 1 -T 
iqn.2001-04.com.example:storage.disk2.amiens.sys1.xyz

You can get the current configuration:

host:~/tgt# ./usr/tgtadm --lld iscsi --op show --mode target
Target 1: iqn.2001-04.com.example:storage.disk2.amiens.sys1.xyz
System information:
Driver: iscsi
Status: running
I_T nexus information:
LUN information:
LUN: 0
Type: controller
SCSI ID: deadbeaf1:0
SCSI SN: beaf10
Size: 0
Backing store: No backing store
Account information:
ACL information:


The controller device for management with lun 0 was created
automatically. You can't remove it.

Now it's time to add a logical unit to the target:

host:~/tgt# ./usr/tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 
1 -b /dev/hdc1

You can get the current configuration:

host:~/tgt# ./usr/tgtadm --lld iscsi --op show --mode target
Target 1: iqn.2001-04.com.example:storage.disk2.amiens.sys1.xyz
System information:
Driver: iscsi
Status: running
I_T nexus information:
LUN information:
LUN: 0
Type: controller
SCSI ID: deadbeaf1:0
SCSI SN: beaf10
Size: 0
Backing store: No backing store
LUN: 1
Type: disk
SCSI ID: deadbeaf1:1
SCSI SN: beaf11
Size: 55G
Backing store: /dev/hdc1
Account information:
ACL information:


If you don't need to configure this target any more, enable the target
to accept any initiators:

host:~/tgt# ./usr/tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
host:~/tgt# ./usr/tgtadm --lld iscsi --op show --mode target
Target 1: iqn.2001-04.com.example:storage.disk2.amiens.sys1.xyz
System information:
Driver: iscsi
Status: running
I_T nexus information:
LUN information:
LUN: 0
Type: controller
SCSI ID: deadbeaf1:0
SCSI SN: beaf10
Size: 0
Backing store: No backing store
LUN: 1
Type: disk
SCSI ID: deadbeaf1:1
SCSI SN: beaf11
Size: 55G
Backing store: /dev/hdc1
Account information:
ACL information:

Re: Debian Lenny; Kernel 2.6.26, Iser, Mellanox : iser_cma_handler:event: 3, error: -110

2008-08-19 Thread Dr. Volker Jaenisch

Hello Mike! 

Thanks for the fast reply!

Mike Christie schrieb:
> volkerJaenisch wrote:
>   
>> Aug 20 01:17:52 hades kernel: [45569.481501] iser:
>> iser_cma_handler:event: 3, error: -110
>> 
> On the target side are you running tgt with iscsi and iser at the same 
> time? Did you make sure to make it so both targets have the proper 
> access lists?
>   
Is there a magical switch to give different ACLs for iser and TCP transport?

How can I seperate the iscsi and the iser target ACLs? They are accessed
via the same IP (IPoIB)
As I understood (poorly) the matter the initiiator open-iscsi at first
tries to discover the target(s) via IP.
Then if it is told to (via -t iser) it tries to negotiate via iser
transport. If this fails it tries TCP transport.
> Or what tgtadm commands did you use to create the iser target or did you 
> use the config script?
>   
I used the following commands:

tgtadm --lld iscsi --op new --mode target --tid 1 -T
de.inqbus.poseidon:disk1
tgtadm --lld iscsi --op bind --mode target --tid 1 -I 10.6.0.1
tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b
/dev/vg1/test

The initiator IP is 10.6.0.1.

Best Regards

Volker

-- 

   inqbus it-consulting  +49 ( 341 )  5643800
   Dr.  Volker Jaenisch  http://www.inqbus.de
   Herloßsohnstr.12  0 4 1 5 5Leipzig
   N  O  T -  F Ä L L E  +49 ( 170 )  3113748



--~--~-~--~~~---~--~~
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: Debian Lenny; Kernel 2.6.26, Iser, Mellanox : iser_cma_handler:event: 3, error: -110

2008-08-19 Thread Mike Christie

volkerJaenisch wrote:
> Hello open-iscsi-Group!
> 
> I have a running iSCSI over IPoIB setup with Mellanox Infiniband HCAs.
> 
> Now I like to run iSCSI over Iser.
> 
> hades:~# iscsi_discovery 10.6.0.2 -tiser
> iscsiadm: No active sessions.
> iscsiadm: Could not read node record for iqn.2001-04.com.poseidon-
> de.inqbus.poseidon:disk1 10.6.0.2 3260 default
> Cannot login over iser to portal 10.6.0.2:3260
> Set target de.inqbus.poseidon:disk1 to automatic login over tcp to
> portal 10.6.0.2:3260
> Logging out of session [sid: 6, target: de.inqbus.poseidon:disk1,
> portal: 10.6.0.2,3260]
> Logout of [sid: 6, target: de.inqbus.poseidon:disk1, portal:
> 10.6.0.2,3260]: successful
> discovered 1 targets at 10.6.0.2
> 
> The TCP path is found without problems and runs well. But the iser
> handshake fails and
> the following error is logged on the initiator side:
> 
> Aug 20 01:17:52 hades kernel: [45569.481501] iser:
> iser_cma_handler:event: 3, error: -110
> 
> Can anybody give me a hint which component is the problem? The kernel,
> the modules,
> the initiator or the target? Feeling a bit helpless. :-(
> 

On the target side are you running tgt with iscsi and iser at the same 
time? Did you make sure to make it so both targets have the proper 
access lists?

Or what tgtadm commands did you use to create the iser target or did you 
use the config script?

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



Debian Lenny; Kernel 2.6.26, Iser, Mellanox : iser_cma_handler:event: 3, error: -110

2008-08-19 Thread volkerJaenisch

Hello open-iscsi-Group!

I have a running iSCSI over IPoIB setup with Mellanox Infiniband HCAs.

Now I like to run iSCSI over Iser.

hades:~# iscsi_discovery 10.6.0.2 -tiser
iscsiadm: No active sessions.
iscsiadm: Could not read node record for iqn.2001-04.com.poseidon-
de.inqbus.poseidon:disk1 10.6.0.2 3260 default
Cannot login over iser to portal 10.6.0.2:3260
Set target de.inqbus.poseidon:disk1 to automatic login over tcp to
portal 10.6.0.2:3260
Logging out of session [sid: 6, target: de.inqbus.poseidon:disk1,
portal: 10.6.0.2,3260]
Logout of [sid: 6, target: de.inqbus.poseidon:disk1, portal:
10.6.0.2,3260]: successful
discovered 1 targets at 10.6.0.2

The TCP path is found without problems and runs well. But the iser
handshake fails and
the following error is logged on the initiator side:

Aug 20 01:17:52 hades kernel: [45569.481501] iser:
iser_cma_handler:event: 3, error: -110

Can anybody give me a hint which component is the problem? The kernel,
the modules,
the initiator or the target? Feeling a bit helpless. :-(

Any help welcome.

Best Regards

Volker

Here the log on  initiator and target:

Initiator: Stock debian Lenny open-iscsi 2.0.869.2-2.1, using the
modules from stock 2.6.26 debian lenny kernel.

Aug 20 01:17:51 hades kernel: [45568.433252] iser:
iser_connect:connecting to: 10.6.0.2, port 0xbc0c
Aug 20 01:17:51 hades kernel: [45568.436498] iser:
iser_cma_handler:event 0 conn 81000dc98280 id 81000dc8b200
Aug 20 01:17:51 hades kernel: [45568.689519] iser:
iscsi_iser_ep_poll:ib conn 81000dc98280 rc = 0
Aug 20 01:17:51 hades kernel: [45568.949516] iser:
iscsi_iser_ep_poll:ib conn 81000dc98280 rc = 0
Aug 20 01:17:51 hades kernel: [45569.209529] iser:
iscsi_iser_ep_poll:ib conn 81000dc98280 rc = 0
Aug 20 01:17:52 hades kernel: [45569.481501] iser:
iser_cma_handler:event 3 conn 81000dc98280 id 81000dc8b200
Aug 20 01:17:52 hades kernel: [45569.481501] iser:
iser_cma_handler:event: 3, error: -110
Aug 20 01:17:52 hades kernel: [45569.537493] iser:
iscsi_iser_ep_poll:ib conn 81000dc98280 rc = -1
Aug 20 01:17:55 hades kernel: [45572.869534] iser:
iscsi_iser_ep_disconnect:ib conn 81000dc98280 state 4
Aug 20 01:17:55 hades kernel: [45572.869565] iser:
iser_conn_terminate:Failed to disconnect, conn: 0x81000dc98280 err
-22
Aug 20 01:17:55 hades kernel: [45572.869617] iser:
iser_free_ib_conn_res:freeing conn 81000dc98280 cma_id
81000dc8b200 fmr pool  qp 0
000

==


Target : tgt 20080805 builded on debian lenny.

Aug 20 01:17:31 poseidon tgtd: Target daemon logger with pid=28900
started!
Aug 20 01:17:32 poseidon tgtd: accept_connection(99) 8
Aug 20 01:17:40 poseidon tgtd: tgt_mgmt(332) 155 0 1 0 1 0 0
targetname=de.inqbus.poseidon:disk1 28899
Aug 20 01:17:40 poseidon tgtd: tgt_device_create(421) 1 0
Aug 20 01:17:40 poseidon tgtd: tgt_device_create(540) Add a logical
unit 0 to the target 1
Aug 20 01:17:40 poseidon tgtd: tgt_target_create(1708) Succeed to
create a new target 1
Aug 20 01:17:48 poseidon tgtd: tgt_mgmt(332) 146 0 1 3 1 0 0 initiator-
address=10.6.0.1 28899
Aug 20 01:17:49 poseidon tgtd: accept_connection(99) 8
Aug 20 01:17:49 poseidon tgtd: cmnd_exec_login(631) Login request
(operational negotiation): 0
Aug 20 01:17:49 poseidon tgtd: login_start(491) exp_cmd_sn: 0,0
Aug 20 01:17:49 poseidon tgtd: it_nexus_create(231) 1 10
Aug 20 01:17:49 poseidon tgtd: session_create(135) session_create:
0x1063d0200
Aug 20 01:17:49 poseidon tgtd: conn_take_fd(178) 0 1 0 1063d0200
Aug 20 01:17:50 poseidon tgtd: iscsi_scsi_cmd_rx_start(1454) 1 12 0 0
36 1 1000
Aug 20 01:17:50 poseidon tgtd: iscsi_task_queue(1399) 0 0 1
Aug 20 01:17:50 poseidon tgtd: target_cmd_queue(818) 0x1235650 12 0
Aug 20 01:17:50 poseidon tgtd: target_cmd_queue(837) 0x1235650 12 0 1
Aug 20 01:17:50 poseidon tgtd: spc_inquiry(164) 0 0
Aug 20 01:17:50 poseidon tgtd: target_cmd_queue(848) 1000 12 (nil)
0x1236000 0 0 36 0 0
Aug 20 01:17:50 poseidon tgtd: iscsi_scsi_cmd_done(1092) shrunk too
big device read len 66 > 36
Aug 20 01:17:50 poseidon tgtd: iscsi_task_tx_start(1745) found a task
1000 36 0 0
Aug 20 01:17:50 poseidon tgtd: iscsi_data_rsp_build(962) 36 36 36 8192
1000
Aug 20 01:17:50 poseidon tgtd: __cmd_done(909) 0 (nil) 0x1236000 0 36
0
Aug 20 01:17:50 poseidon tgtd: iscsi_task_tx_start(1770) no more data
Aug 20 01:17:50 poseidon tgtd: iscsi_scsi_cmd_rx_start(1454) 1 12 0 0
68 1 1001
Aug 20 01:17:50 poseidon tgtd: iscsi_task_queue(1399) 1 1 1
Aug 20 01:17:50 poseidon tgtd: target_cmd_queue(818) 0x1235650 12 0
Aug 20 01:17:50 poseidon tgtd: target_cmd_queue(837) 0x1235650 12 0 1
Aug 20 01:17:50 poseidon tgtd: spc_inquiry(164) 0 0
Aug 20 01:17:50 poseidon tgtd: target_cmd_queue(848) 1001 12 (nil)
0x1236000 0 0 66 0 0
Aug 20 01:17:50 poseidon tgtd: iscsi_task_tx_start(1745) found a task
1001 66 0 0
Aug 20 01:17:50 poseidon tgtd: iscsi_data_rsp_build(962) 66 66 66 8192