Ant wrote:
> On 22 апр, 19:30, Mike Christie <[EMAIL PROTECTED]> wrote:
>> Is there anything in the target logs about an error at this time?
>>
> 
> Hmm, i found something, but i'am not shure that it's correct log from
> reo. May be it is, but just have wrong timestamp:


This looks like it is our problem.


> 
> Mar 22 21:11:04.521 3040529328 INFO:iSCSI Logout, Host IP:
> '192.168.1.1', target: 'reo.target', initiator: 'reo.initiator'
> Mar 22 21:11:04.770 3085727424 INFO:connection accepted on port 3260
> (local IP 192.168.1.10, remote IP 192.168.1.1)
> Mar 22 21:11:05.021 3040529328 INFO:Successful Normal iSCSI login from
> Host IP: 192.168.1.1 initiator: 'reo.initiator' to target:
> 'reo.target'
> Mar 22 21:21:56.325 3040529328 ERROR:Expected CmdSN 17674434, got
> 17674435. (breaking connection)
> Mar 22 21:21:56.325 3040529328 ERROR:nop_out_t() failed

I do not think the reo box likes obeys the immedate bit and probably 
thinks we should be incrementing the cmdsn.

If you set
node.conn[0].timeo.noop_out_interval = 0
node.conn[0].timeo.noop_out_timeout = 0

Does this 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-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
-~----------~----~----~----~------~----~------~--~---

Reply via email to