It would appear that I'm bumping the status sequence number and
Microsoft thinks that's wrong. This should be easy to trace since the
first time the error occurs is early in the connection.
On Jan 30, 2007, at 2:07 PM, Nigel Smith wrote:
I've just done a few simple tests with the new solaris iscsi target
code. I'm using Microsoft Server 2003 R2, and the debug version of
the Microsoft iscsi initiator (v2.03). I can mount and format the
target, and copy files across, and everything "seems" to work ok.
But when I look in the output window of 'DebugView', I see the
following messages:
# Time(s) Debug Print
000 0.00000000 [1316] 01/30/2007 20:18:57.00000249:[ 524.
348] iscsidsc: Did not find target portal 172.16.8.150/3260
0xefff000b
001 1.55681658 [1316] 01/30/2007 20:18:58.00000822:[ 524.
f64] iscsidsc: ReportTargets passed 0x0 buffer, needs 0x46
002 12.94111633 [1316] 01/30/2007 20:19:10.00000208:[ 524.
348] iscsidsc: Did not find target portal 172.16.8.150/3260
0xefff000b
003 84.54269409 Invalid status seq num 0x21. Current is 0x20
004 84.54283142 Premature Termination : Okay to remove connection
FA9E2598
005 84.54284668 Premature Termination : Okay to remove session
FAA6B000
006 84.54409027 [1316] 01/30/2007 20:20:21.00000811:[ 524.
348] iscsidsc: Did not find target portal 172.16.8.150/3260
0xefff000b
007 84.91815186 Relogin. Reconnect count - 1
008 151.48130798 Invalid status seq num 0xee. Current is 0xed
009 151.48144531 Premature Termination : Okay to remove connection
FAA36740
010 151.48146057 Premature Termination : Okay to remove session
FAA6B000
011 151.48594666 [1316] 01/30/2007 20:21:28.00000747:[ 524.
348] iscsidsc: Did not find target portal 172.16.8.150/3260
0xefff000b
012 151.83351135 Relogin. Reconnect count - 1
013 920.03717041 Invalid status seq num 0x9a4. Current is 0x990
014 920.04486084 Premature Termination : Okay to remove connection
FB9A2220
015 920.04486084 Premature Termination : Okay to remove session
FAA6B000
016 920.52783203 Relogin. Reconnect count - 1
017 920.55249023 [1316] 01/30/2007 20:34:17.00000422:[ 524.
348] iscsidsc: Did not find target portal 172.16.8.150/3260
0xefff000b
So it does look like it thinks there is something not quite right
in the status sequence numbering, which causes a dropped
connection, but followed immediately by a successful re-login. It
recovers so quickly that you would not think a problem had
occurred. And I don't understand why it say's "Did not find target
portal", because it obviously can find it, or it would not be working!
It's almost as if something is timing out. Every time I do an
operation on the target, it repeats the termination, then re-login
cycle. I've not done any Ethereal traces yet, but thought it best
to confirm that I can see the 'problem'.
Thanks
Nigel Smith
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
----
Rick McNeal
"If ignorance is bliss, this lesson would appear to be a deliberate
attempt on your part to deprive me of happiness, the pursuit of which
is my unalienable right according to the Declaration of
Independence. I therefore assert my patriotic prerogative not to
know this material. I'll be out on the playground." -- Calvin
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
