Seth,
The CQ Error 13 is done mostly when a Fin is received. If the same problem
can be repro'd on iet , can you pl capture the wireshark trace on the target.
That would be very helpful.
Also, if NOP's are being sent ,then, I would assume the traffic is low and
wireshark would not drop packets..
Thanks
Jay
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Mike Christie
Sent: Wednesday, July 06, 2011 7:54 PM
To: [email protected]
Cc: Seth Simons
Subject: Re: unable to login to targets with be2iscsi
On 07/04/2011 08:34 AM, Seth Simons wrote:
> Yep, I do see those. I figured they were from the iscsi layer. Is it
> worth validating the configuration first *without* using multipath?
> It's fairly trivial to disable. The only reason i've not tried this
> yet is that the same problem happened when using a non-multipath
> target (single target on a linux box using ietd). I'm starting to
I was re-reading this and saw this. So you have tried be2iscsi with iet
and it was showing the same problem? Or at least it had the problem
where you see:
[ 2811.027636] (beiscsi_process_cq():1953):CQ Error 13, reset CID 0x40...
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
