I do not see ping/nop timeout message in the logs
(probably that's why changing the noop timeouts did not work).
Simply starting the session does not cause these errors.
On starting the second session, I start a daemon
that does SCSI commands like INQUIRY on all the paths.
After that I see these messages, and the daemon gets stuck
for a very long time waiting for SCSI commands to finish.
At the backend I have EMC CLARiiON.
# iscsiadm -m node -P 1
Target: iqn.1992-04.com.emc:cx.ckm00091100683.a2
Portal: 192.168.10.1:3260,1
Iface Name: iface0
Target: iqn.1992-04.com.emc:cx.ckm00091100683.b2
Portal: 192.168.12.1:3260,3
Iface Name: iface1
# iscsiadm --mode node --targetname iqn.
1992-04.com.emc:cx.ckm00091100683.a2
node.name = iqn.1992-04.com.emc:cx.ckm00091100683.a2
node.tpgt = 1
node.startup = automatic
iface.hwaddress = 00:15:17:A8:A9:0A
iface.iscsi_ifacename = iface0
iface.net_ifacename = eth4
iface.transport_name = tcp
node.discovery_address = 192.168.10.1
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 = <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 = 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.10.1
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
On Dec 7, 10:31 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
> avora wrote:
> > With SLES10 SP3 x86_64,
> > as soon as I start the second iscsi session2, I am very frequently
> > getting the connection errors/
> > I do not see this with SLES10 SP2 x86_64 on the same setup.
>
> > Dec 7 18:42:05 cdc-r710s1 kernel: connection2:0:detectedconnerror
> > (1011)
> > Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after
> > recovery (1 attempts)
> > Dec 7 18:42:06 cdc-r710s1 iscsid: Kernel reported iSCSI connection
> > 2:0error(1011) state (3)
> > Dec 7 18:42:08 cdc-r710s1 kernel: connection2:0:detectedconnerror
> > (1011)
>
> > I have tried changing noop_out_interval and noop_out_timeout to
> > 120/120 and 0/0 but did not help.
>
> Did you see a ping/nop timeout message in the logs or just what you
> included above with theconnerror1011? The ping/nop message would be a
> little before the conerror1011.
>
> What target is this with and are you doing any IO tests when this
> happens or are you just logging into the second session and then you
> start to get these errors?
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
