Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h25E7c121754
	for ips-outgoing; Wed, 5 Mar 2003 09:07:38 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from fep2.012.net.il (fep2.goldenlines.net.il [212.117.129.202])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h25E7YM21749
	for <ips@ece.cmu.edu>; Wed, 5 Mar 2003 09:07:34 -0500 (EST)
Received: from JA31 ([12.65.150.199]) by fep2.012.net.il with ESMTP
          id <20030305140726.RCGM11908.fep2@JA31>;
          Wed, 5 Mar 2003 16:07:26 +0200
From: "Julian Satran" <satran@haifasphere.co.il>
To: <kevin_lemay@agilent.com>, <Julian_Satran@il.ibm.com>
Cc: <ips@ece.cmu.edu>, <Julian_Satran@il.ibm.com>
Subject: RE: Error recovery level 2 Question
Date: Wed, 5 Mar 2003 16:07:20 +0200
Message-ID: <000c01c2e320$8d710c50$c796410c@JA31>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <1BEBA5E8600DD4119A50009027AF54A010FAE103@axcs04.cos.agilent.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ece.cmu.edu id h25E7ZM21750
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

sorry for the delay - I was away from my desk.

The target will have to send a recovery R2T based on what it has (part
or all of the data)..
An overzealous initiator may start sending data right away - but it
should keep track of the changes in PDU size in any and the rules
associated with it.

Julo




kevin_lemay@agilent.com 
05/03/03 01:14	
To
Julian Satran/Haifa/IBM@IBMIL
cc
ips@ece.cmu.edu
Subject
Error recovery level 2 Question
	

	


Julian,
 
Assume that I have a multi-connection session to a target when one of
the connections fails.
 
What is the completion of the following diagram (assume 8K PDUs and
maxBurst = 64K):
 
Initiator                          Target
----------                        ---------
Write Cmd (64K no Immediate) --->
                             <---  R2T Offset 0, len=64K
Data PDU (8K DataSN 0)       --->
Data PDU (8K DataSN 1)       ---> 
   --- Connection Lost ---
 
 
On 2nd connection:
Logout (for recovery)        --->
                             <---  Logout Response
Task Mgnt (Reassign)         --->
                             <--- Task Mgnt Response - OK
 
What Comes Next?
 
Is a recovery R2T expected from the target?
or does the Initiator continue to send data PDUs to the target?
 
If the initiator continues to send, what is the proper place to
continue. I may have submitted several PDUs to the stack that were never
received before the connection loss was detected. 
 
The read request seems fairly straight forward, but the write case is
not clear (at least to me...)
 
Thanks for any help,
 
Kevin Lemay


Regards,
Julo


-----Original Message-----
From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu] On Behalf Of
kevin_lemay@agilent.com
Sent: 05 March, 2003 01:14
To: Julian_Satran@il.ibm.com
Cc: ips@ece.cmu.edu
Subject: Error recovery level 2 Question


Julian,
 
Assume that I have a multi-connection session to a target when one of
the connections fails.
 
What is the completion of the following diagram (assume 8K PDUs and
maxBurst = 64K):
 
Initiator                          Target
----------                        ---------
Write Cmd (64K no Immediate) --->
                             <---  R2T Offset 0, len=64K
Data PDU (8K DataSN 0)       --->
Data PDU (8K DataSN 1)       ---> 
   --- Connection Lost ---
 
 
On 2nd connection:
Logout (for recovery)        --->
                             <---  Logout Response
Task Mgnt (Reassign)         --->
                             <--- Task Mgnt Response - OK
 
What Comes Next?
 
Is a recovery R2T expected from the target?
or does the Initiator continue to send data PDUs to the target?
 
If the initiator continues to send, what is the proper place to
continue. I may have submitted several PDUs to the stack that were never
received before the connection loss was detected. 
 
The read request seems fairly straight forward, but the write case is
not clear (at least to me...)
 
Thanks for any help,
 
Kevin Lemay

