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 h1SFXiD29490
	for ips-outgoing; Fri, 28 Feb 2003 10:33:44 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from dmz1.silverbacksystems.com (dmz1.silverbacksystems.com [65.172.158.82])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h1S1lwW15141
	for <ips@ece.cmu.edu>; Thu, 27 Feb 2003 20:47:58 -0500 (EST)
Received: from ns.silverbacksystems.com (gate-camp-hme0.silverbacksystems.com [65.172.158.93])
	by dmz1.silverbacksystems.com (Postfix on SuSE Linux 7.3 (i386)) with ESMTP id 365C7D1B8
	for <ips@ece.cmu.edu>; Thu, 27 Feb 2003 17:47:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by ns.silverbacksystems.com (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id CC3EC1A221
	for <ips@ece.cmu.edu>; Thu, 27 Feb 2003 17:47:39 -0800 (PST)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"
Date: Thu, 27 Feb 2003 17:47:34 -0800
From: "Alex Aizman" <aaizman@silverbacksystems.com>
Importance: Normal
Message-ID: <000e01c2decb$5d3dbe10$2c10000a@corp.silverbacksystems.com>
MIME-Version: 1.0
Received: from ns.silverbacksystems.com (localhost [127.0.0.1])
	by localhost (AvMailGate-2.0.0.6) id 24880-5782B054;
	Thu, 27 Feb 2003 17:47:21 -0800
Received: from ALEX (ALEX.corp.silverbacksystems.com [10.0.16.44])
	by ns.silverbacksystems.com (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 7B27735C9
	for <ips@ece.cmu.edu>; Thu, 27 Feb 2003 17:47:21 -0800 (PST)
Subject: iSCSI: connection failure in a multii-connection session
To: <ips@ece.cmu.edu>
X-AntiVirus: OK! AntiVir MailGate Version 2.0.0.6
	 at ns.silverbacksystems.com has not found any known virus in this email.
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-MSMail-Priority: Normal
X-Priority: 3 (Normal)
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

Let's say, Error Recovery Level = 0 and one connection in a
multi-connection session has failed. The first question is, could
Initiator retain the functioning session with fewer connections (and the
ERL being zero)? Assuming the answer is 'yes', here's some of the
follow-up questions:

Initiator sends Logout(1, CID) on one of the remaining good connections
to cleanup the failed connection, ID=CID.

Initiator then either:

1) Sends Task Abort for every unacknowledged command. This process will
eventually synchronize *this* session sequence numbers. The problem is,
once all Aborts are executed, the Target will proceed executing
outstanding CmdSNs received on good connection(s), which may cause
re-ordering on the SCSI level.

2) Alternatively, the Initiator re-issues all outstanding commands on
the good connection(s), without changing their ITTs and CmdSNs. Target
receives these commands (some of which may have been already executed),
and continues normal processing in the order of CmdSNs. The question is
whether Initiator is permitted to retry  commands using the same ITT and
CmdSN pair on another connection after successful Logout but without
explicit re-assignment. Section 6.2.1 in the spec seems to allow that.

3) Finally, is it a hard requirement that Initiator uses the same ITT
that was used to send the original command? What's the logic behind this
requirement?

Alex
