Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from newbox.ece.cmu.edu (localhost [127.0.0.1])
	by newbox.ece.cmu.edu (Cyrus v2.1.12) with LMTP; Tue, 15 Jul 2003 19:50:52 -0400
X-Sieve: CMU Sieve 2.2
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by newbox.ece.cmu.edu (Postfix) with ESMTP id E169C30F1
	for <ipsml@ece.cmu.edu>; Tue, 15 Jul 2003 19:50:51 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 9EDDF1B0; Tue, 15 Jul 2003 19:50:50 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by hazard.ece.cmu.edu (Postfix) with ESMTP
	id 9007C11F; Tue, 15 Jul 2003 19:50:39 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id ADD1389DE; Tue, 15 Jul 2003 19:50:23 -0400 (EDT)
Delivered-To: ips-outgoing@sos.ece.cmu.edu
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by sos.ece.cmu.edu (Postfix) with ESMTP id A147B89D6
	for <ips-outgoing@sos.ece.cmu.edu>; Tue, 15 Jul 2003 19:50:23 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 804F5115; Tue, 15 Jul 2003 19:50:23 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 5726211F; Tue, 15 Jul 2003 19:50:23 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id 7A00C115
	for <ips-outgoing@ece.cmu.edu>; Tue, 15 Jul 2003 19:50:21 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 65AED89DF; Tue, 15 Jul 2003 19:50:21 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Delivered-To: ips@sos.ece.cmu.edu
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 9CB5A89D6
	for <ips@sos.ece.cmu.edu>; Tue, 15 Jul 2003 19:50:19 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 769F2117; Tue, 15 Jul 2003 19:50:19 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 50E1E19D; Tue, 15 Jul 2003 19:50:19 -0400 (EDT)
Received: from thebe.your-site.com (thebe.your-site.com [140.186.45.26])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id 2FD87117
	for <ips@ece.cmu.edu>; Tue, 15 Jul 2003 19:50:15 -0400 (EDT)
Received: from 192.168.0.2 (64-144-5-25.client.dsl.net [64.144.5.25])
	by thebe.your-site.com (Postfix) with ESMTP
	id C7E9E2448EE; Tue, 15 Jul 2003 19:50:15 -0400 (EDT)
Date: Tue, 15 Jul 2003 18:50:07 -0500
From: Caitlin Bestler <cait@asomi.com>
Subject: Re: iSCSI: Login Redirect
To: Bob Gilligan <gilligan@intransa.com>
Cc: "Mallikarjun C." <cbm@rose.hp.com>, ips@ece.cmu.edu
X-Priority: 3
In-Reply-To: <3F149165.70900@intransa.com>
Message-ID: <r02000000-1026-10EB71C6B71F11D791D3003065D48EE0@[192.168.0.2]>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailer: Mailsmith 2.0 (Blindsider)
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-16.3 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

On Tuesday, July 15, 2003, gilligan@intransa.com wrote:

>Hi - If you are using redirect to implement fault
>tolerance/load balancing as we sketched out in
>draft-gilligan-iscsi-fault-tolerance-00.txt, there may be
>transients when an initiator gets  redirected multiple times. 
>For example, say A redirects the initiator to B.  But say B has
>more recent information about the actual location of the
>target, so it redirects the initiator to C.  Eventually A
>learns the same information as B and then redirects initiators
>directly to C.  So the initiator should be prepared to accept
>some number of consecutive redirects.
>
>Of course, if the redirection goes on indefinitely or loops - say A 
>redirects to B, which redirects to C, which redirects to A, etc. - that 
>probably does represent either a configuration error or a bug.  So the 
>initiator may wish to detect a redirection loop or an excessive number 
>of  redirections.
>
>But, as you point out, what represents "excessive redirection"
>is in the eye of the initiator.  So, I don't think that the
>main iSCSI spec needs to call out a specific hard limit.
>

In order to cover the type of fault-tolerance scenario you cited
wouldn't it make sense to set a minimum that the initiator SHOULD
be willing to accept?

That way cluster builders would have a base that they could assume
would not result in iniator failures (only delays).
