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 22:07:30 -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 7B03030E8
	for <ipsml@ece.cmu.edu>; Tue, 15 Jul 2003 22:07:30 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 30C2B1AB; Tue, 15 Jul 2003 22:07:30 -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 7856C142; Tue, 15 Jul 2003 22:07:27 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 6749589DF; Tue, 15 Jul 2003 22:07:15 -0400 (EDT)
Delivered-To: ips-outgoing@sos.ece.cmu.edu
Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 5017589D6
	for <ips-outgoing@sos.ece.cmu.edu>; Tue, 15 Jul 2003 22:07:15 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id EFC907F; Tue, 15 Jul 2003 22:07:15 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id C03537C; Tue, 15 Jul 2003 22:07:14 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by bache.ece.cmu.edu (Postfix) with ESMTP id 1E0929D
	for <ips-outgoing@ece.cmu.edu>; Tue, 15 Jul 2003 22:07:10 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id BD9DA89DF; Tue, 15 Jul 2003 22:07:10 -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 6771089D6
	for <ips@sos.ece.cmu.edu>; Tue, 15 Jul 2003 22:07:09 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 46DF8136; Tue, 15 Jul 2003 22:07:09 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id F01D81A7; Tue, 15 Jul 2003 22:07:08 -0400 (EDT)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id 769BA136
	for <ips@ece.cmu.edu>; Tue, 15 Jul 2003 22:06:56 -0400 (EDT)
Received: from RLTEMPLE ([147.11.233.1])
	by mail.wrs.com (8.9.3/8.9.1) with SMTP id TAA17659;
	Tue, 15 Jul 2003 19:06:12 -0700 (PDT)
From: "Rod Harrison" <rod.harrison@windriver.com>
To: "Caitlin Bestler" <cait@asomi.com>,
	"Bob Gilligan" <gilligan@intransa.com>
Cc: "Mallikarjun C." <cbm@rose.hp.com>, <ips@ece.cmu.edu>
Subject: RE: iSCSI: Login Redirect
Date: Tue, 15 Jul 2003 21:06:21 -0500
Message-ID: <NEBBKMMOEMCINPLCHKGMOEFKEEAA.rod.harrison@windriver.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <r02000000-1026-10EB71C6B71F11D791D3003065D48EE0@[192.168.0.2]>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-28.3 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,MSGID_GOOD_EXCHANGE,
	      ORIGINAL_MESSAGE
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)


FYI, we have an arbitrary limit of 100 redirects before we give
up.

- Rod

-----Original Message-----
From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On
Behalf Of
Caitlin Bestler
Sent: Tuesday, July 15, 2003 6:50 PM
To: Bob Gilligan
Cc: Mallikarjun C.; ips@ece.cmu.edu
Subject: Re: iSCSI: Login Redirect


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).

