On Feb 24, 2:19 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
> On 02/23/2010 02:04 PM, Jonathan Murray wrote:
>
> > after about 24 hours, we see the following in /var/log/messages (not in
> > order)
>
> > iscsid: connect failed (111)
> > iscsi: cmd 0x28 is not queued (8)
> > iscsi: cmd 0x2a is not queued (8)
> > iscsi: detected conn error (1011)
> > Kernel reported iSCSI connection 1:0 error (1011) state (3)
> > iscsid: connect failed (113)
>
> In /var/log/messages or in the iscsid logs do you see something about a
> ping/nop timing out and then see the 1011 conn errors? If so then you
> should upgrade to 5.4.
>
> It looks like what is happening is that the target is just dropping the
> connection. The initiator tries to reconnect and in one case gets
> iscsid: connect failed (111)  ======> "Connection refused"
>
> but then in another retry we get
>
> iscsid: connect failed (113)  ====> "No route to host".
>
> Are you running with 1 session or multiple ones and are all sessions
> going through the same network and to the same target portal?

I tried to post earlier, so please disregard if this is a repeat.

We have one linux machine with one of two network interfaces dedicated
to the iscsi stuff. The Promise array(portal?) has 2 interfaces,
however we are just using one. If that is what you mean by "1
session", I think that's what we have. There should only be one device
connecting to the array. However I have not actively blocked other
machines from connecting to it.

I do not see any reference to ping/nop timeouts in any log files. It
seems the iscsi log is "brcm-iscsi.log" I searched all the logs for
ping/nop references, but I didn't find any.

I did a tcpdump and watched both failed and successful connections.

failed:

tcpdump of failed connection attempt:

1:56:48.597941 IP ndsfdh1-iscsi.whoi.edu.47753 >
ndsfnar1p2.whoi.edu.iscsi-target: S 1049711648:1049711648(0) win 5840
<mss 1460,sackOK,timestamp 963221000 0,nop,wscale 7>
21:56:51.597508 IP ndsfdh1-iscsi.whoi.edu.47753 >
ndsfnar1p2.whoi.edu.iscsi-target: S 1049711648:1049711648(0) win 5840
<mss 1460,sackOK,timestamp 963224000 0,nop,wscale 7>
21:56:57.597808 IP ndsfdh1-iscsi.whoi.edu.47753 >
ndsfnar1p2.whoi.edu.iscsi-target: S 1049711648:1049711648(0) win 5840
<mss 1460,sackOK,timestamp 963230000 0,nop,wscale 7>
21:57:03.658197 IP ndsfdh1-iscsi.whoi.edu.47754 >
ndsfnar1p2.whoi.edu.iscsi-target: S 1069029545:1069029545(0) win 5840
<mss 1460,sackOK,timestamp 963236060 0,nop,wscale 7>
21:57:06.657769 IP ndsfdh1-iscsi.whoi.edu.47754 >
ndsfnar1p2.whoi.edu.iscsi-target: S 1069029545:1069029545(0) win 5840
<mss 1460,sackOK,timestamp 963239060 0,nop,wscale 7>
21:57:12.658069 IP ndsfdh1-iscsi.whoi.edu.47754 >
ndsfnar1p2.whoi.edu.iscsi-target: S 1069029545:1069029545(0) win 5840
<mss 1460,sackOK,timestamp 963245060 0,nop,wscale 7>

Successful connection attempt:

22:00:00.648924 IP ndsfnar1p2.whoi.edu.iscsi-target > ndsfdh1-
iscsi.whoi.edu.45937: . 365633:367081(1448) ack 5901 win 49438
<nop,nop,timestamp 220290 963413046>
22:00:00.648931 IP ndsfnar1p2.whoi.edu.iscsi-target > ndsfdh1-
iscsi.whoi.edu.45937: . 367081:368529(1448) ack 5901 win 49438
<nop,nop,timestamp 220290 963413046>
22:00:00.648935 IP ndsfdh1-iscsi.whoi.edu.45937 >
ndsfnar1p2.whoi.edu.iscsi-target: . ack 368529 win 1525
<nop,nop,timestamp 963413047 220290>
22:00:00.648940 IP ndsfnar1p2.whoi.edu.iscsi-target > ndsfdh1-
iscsi.whoi.edu.45937: . 368529:369977(1448) ack 5901 win 49438
<nop,nop,timestamp 220290 963413046>
22:00:00.648946 IP ndsfnar1p2.whoi.edu.iscsi-target > ndsfdh1-
iscsi.whoi.edu.45937: . 369977:371425(1448) ack 5901 win 49438
<nop,nop,timestamp 220290 963413046>
22:00:00.648950 IP ndsfdh1-iscsi.whoi.edu.45937 >
ndsfnar1p2.whoi.edu.iscsi-target: . ack 371425 win 1525
<nop,nop,timestamp 963413047 220290>
22:00:00.648955 IP ndsfnar1p2.whoi.edu.iscsi-target > ndsfdh1-
iscsi.whoi.edu.45937: . 371425:372873(1448) ack 5901 win 49438
<nop,nop,timestamp 220290 963413046>
22:00:00.648972 IP ndsfnar1p2.whoi.edu.iscsi-target > ndsfdh1-
iscsi.whoi.edu.45937: . 372873:374321(1448) ack 5901 win 49438
<nop,nop,timestamp 220290 963413046>

I don't really know how to interpret the tcpdump data. Maybe it's
useful?

thanks for your help.

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

Reply via email to