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 iSCSIconnection1: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 connerrors? If so then you
> should upgrade to 5.4.
>
> It looks like what is happening is that the target is just dropping 
> theconnection. The initiator tries to reconnect and in one case gets
> iscsid: connect failed (111)  ======> "Connectionrefused"
>
> 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 do not see anything about ping/nop timeouts in /var/log/messages. I
did a tcpdump during a failed connection and a successful connection.
Unfortunately, I am not certain how to interpret the results. However,
I do see "nop" in these results for the failed connection. This
tcpdump was done when I know the connection was not working:

Failed:

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>


This is the tcpdump from when the connection seemed to be working
fine:

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>

We have one dedicated network adapter on the linux machine connected
to the network. We have one network adapter/iscsi port on the Promise
array connected to the network. If this means "1 session" , then yes.
The promise array and the linux machine are on different subnets (is
this what you mean by the same network?") No other machines should be
accessing the raid array.
As far as "target portal" I assume this means the Promise array?

thank you for your help.

-Jonathan



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