Re: detected conn error (1011) on login with open-iscsi-2.0-869
On 23 Apr, 20:29, Mike Christie <[EMAIL PROTECTED]> wrote: > DaMn wrote: > > Hi, > > > despite the Subject, i've not found a solution to my problem in others > > threads. > > I'm having trouble connecting a target with two LUN: > > > # iscsiadm -m discovery -t st -p 192.168.29.13 > > puts out: > > > 192.168.29.13:3260,1 iqn.1991-05.com.microsoft:atlante-vm-shared-disk- > > vm2-target > > 192.168.29.13:3260,1 iqn.1991-05.com.microsoft:atlante-vm-shared-disk- > > vm1-target > > > # iscsiadm -m node -T iqn.1991-05.com.microsoft:atlante-vm-shared- > > disk-vm1-target > > print out: > > > node.name = iqn.1991-05.com.microsoft:atlante-vm-shared-disk-vm1- > > target > > node.tpgt = 1 > > node.startup = manual > > iface.hwaddress = default > > iface.iscsi_ifacename = default > > iface.net_ifacename = default > > iface.transport_name = tcp > > node.discovery_address = 192.168.29.13 > > node.discovery_port = 3260 > > node.discovery_type = send_targets > > 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 = > > node.session.auth.password = > > node.session.auth.username_in = > > node.session.auth.password_in = > > node.session.timeo.replacement_timeout = 120 > > node.session.err_timeo.abort_timeout = 15 > > node.session.err_timeo.lu_reset_timeout = 20 > > node.session.err_timeo.host_reset_timeout = 60 > > 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 = 192.168.29.13 > > 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.noop_out_interval = 5 > > node.conn[0].timeo.noop_out_timeout = 5 > > 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 > > > then, when i try to connect: > > > # iscsiadm -m node -T iqn.1991-05.com.microsoft:atlante-vm-shared- > > disk-vm1-target -l > > prints out: > > > Logging in to [iface: default, target: iqn. > > 1991-05.com.microsoft:atlante-vm-shared-disk-vm1-target, portal: > > 192.168.29.13,3260] > > Login to [iface: default, target: iqn.1991-05.com.microsoft:atlante-vm- > > shared-disk-vm1-target, portal: 192.168.29.13,3260]: successful > > > but in /var/log/messages prints out: > > > Apr 23 12:32:42 virtualserv1 kernel: scsi69 : iSCSI Initiator over TCP/ > > IP > > Apr 23 12:32:42 virtualserv1 kernel: connection4:0: detected conn > > error (1011) > > Apr 23 12:32:42 virtualserv1 iscsid: connection4:0 is operational now > > Apr 23 12:32:43 virtualserv1 iscsid: Kernel reported iSCSI connection > > 4:0 error (1011) state (3) > > Apr 23 12:32:46 virtualserv1 kernel: session4: host reset succeeded > > Apr 23 12:32:46 virtualserv1 iscsid: connection4:0 is operational > > after recovery (1 attempts) > > Apr 23 12:32:56 virtualserv1 kernel: 69:0:0:0: scsi: Device offlined > > - not ready after error recovery > > It looks the target is not liking something. Are there any target logs? You are damn right Mike, and the matter is quite embarassing... Actually, who set up the target forgotten to added an available virtual disk. So, open-iscsi logged on the target but no device was detected. I've required the necessary changes in SAN/NAS configuration and now all work fine. Best regards, DaMn. --~--~-~--~~~---~--~~ 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: detected conn error (1011) on login with open-iscsi-2.0-869
DaMn wrote: > Hi, > > despite the Subject, i've not found a solution to my problem in others > threads. > I'm having trouble connecting a target with two LUN: > > # iscsiadm -m discovery -t st -p 192.168.29.13 > puts out: > > 192.168.29.13:3260,1 iqn.1991-05.com.microsoft:atlante-vm-shared-disk- > vm2-target > 192.168.29.13:3260,1 iqn.1991-05.com.microsoft:atlante-vm-shared-disk- > vm1-target > > # iscsiadm -m node -T iqn.1991-05.com.microsoft:atlante-vm-shared- > disk-vm1-target > print out: > > node.name = iqn.1991-05.com.microsoft:atlante-vm-shared-disk-vm1- > target > node.tpgt = 1 > node.startup = manual > iface.hwaddress = default > iface.iscsi_ifacename = default > iface.net_ifacename = default > iface.transport_name = tcp > node.discovery_address = 192.168.29.13 > node.discovery_port = 3260 > node.discovery_type = send_targets > 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 = > node.session.auth.password = > node.session.auth.username_in = > node.session.auth.password_in = > node.session.timeo.replacement_timeout = 120 > node.session.err_timeo.abort_timeout = 15 > node.session.err_timeo.lu_reset_timeout = 20 > node.session.err_timeo.host_reset_timeout = 60 > 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 = 192.168.29.13 > 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.noop_out_interval = 5 > node.conn[0].timeo.noop_out_timeout = 5 > 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 > > then, when i try to connect: > > # iscsiadm -m node -T iqn.1991-05.com.microsoft:atlante-vm-shared- > disk-vm1-target -l > prints out: > > Logging in to [iface: default, target: iqn. > 1991-05.com.microsoft:atlante-vm-shared-disk-vm1-target, portal: > 192.168.29.13,3260] > Login to [iface: default, target: iqn.1991-05.com.microsoft:atlante-vm- > shared-disk-vm1-target, portal: 192.168.29.13,3260]: successful > > but in /var/log/messages prints out: > > Apr 23 12:32:42 virtualserv1 kernel: scsi69 : iSCSI Initiator over TCP/ > IP > Apr 23 12:32:42 virtualserv1 kernel: connection4:0: detected conn > error (1011) > Apr 23 12:32:42 virtualserv1 iscsid: connection4:0 is operational now > Apr 23 12:32:43 virtualserv1 iscsid: Kernel reported iSCSI connection > 4:0 error (1011) state (3) > Apr 23 12:32:46 virtualserv1 kernel: session4: host reset succeeded > Apr 23 12:32:46 virtualserv1 iscsid: connection4:0 is operational > after recovery (1 attempts) > Apr 23 12:32:56 virtualserv1 kernel: 69:0:0:0: scsi: Device offlined > - not ready after error recovery > It looks the target is not liking something. Are there any target logs? --~--~-~--~~~---~--~~ 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: detected conn error (1011) on login with open-iscsi-2.0-869
> > and lsscsi don't detect anything. > > Problems comes out after we deleted a previous LUN and added the two > new LUNs. Try 'iscsiadm -m node -R'. If you are re-using the LUN number (which some iSCSI targets do), it is strongly recommended you logout and then re-login. There are some more fancy ways of dealing with this, but it might cause havoc on your system if you are not careful: 1). Delete the block device using the sysfs operation. 2). Re-scan the generic scsi-device to kick-off the kernel re-scan routine 3). Viola, new two block devices appear. Or you can try to logout and then re-login in back - what happens then? > With only one LUN i had no problem... very strange! > > Any help is welcomed. > > DaMn. > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
