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; Wed, 16 Jul 2003 08:08:18 -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 B067531DC
	for <ipsml@ece.cmu.edu>; Wed, 16 Jul 2003 08:08:18 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 4E0C413F; Wed, 16 Jul 2003 08:08:18 -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 7AD30C8; Wed, 16 Jul 2003 08:08:13 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id B719A89DB; Wed, 16 Jul 2003 08:07:59 -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 A891589D6
	for <ips-outgoing@sos.ece.cmu.edu>; Wed, 16 Jul 2003 08:07:59 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id 81E7888; Wed, 16 Jul 2003 08:07:59 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id 4E4C09A; Wed, 16 Jul 2003 08:07:59 -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 C037A8B
	for <ips-outgoing@ece.cmu.edu>; Wed, 16 Jul 2003 08:07:54 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 9596D89DD; Wed, 16 Jul 2003 08:07:54 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Delivered-To: ips@sos.ece.cmu.edu
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by sos.ece.cmu.edu (Postfix) with ESMTP id CA3E689DB
	for <ips@sos.ece.cmu.edu>; Wed, 16 Jul 2003 08:07:52 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id C3864A5; Wed, 16 Jul 2003 08:07:51 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 86F37AF; Wed, 16 Jul 2003 08:07:51 -0400 (EDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.131])
	by osgood.ece.cmu.edu (Postfix) with ESMTP
	id 5A0559A; Wed, 16 Jul 2003 08:07:47 -0400 (EDT)
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11])
	by e33.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h6GC7kj3303352;
	Wed, 16 Jul 2003 08:07:46 -0400
Received: from d03nm115.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay02.boulder.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h6GC7ew5165056;
	Wed, 16 Jul 2003 06:07:40 -0600
To: "Mallikarjun C." <cbm@rose.hp.com>
Cc: ips@ece.cmu.edu,
	"Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>,
	owner-ips@ece.cmu.edu
MIME-Version: 1.0
Subject: Re: iSCSI: Login Redirect
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
From: John Hufferd <hufferd@us.ibm.com>
Message-ID: <OF514EA493.1B2A5F95-ON88256D65.00425A6C-88256D65.00429A0B@us.ibm.com>
Date: Wed, 16 Jul 2003 05:07:40 -0700
X-MIMETrack: Serialize by Router on D03NM115/03/M/IBM(Release 6.0.1 [IBM]|June 10, 2003) at
 07/16/2003 06:07:45,
	Serialize complete at 07/16/2003 06:07:45
Content-Type: multipart/alternative; boundary="=_alternative 0042984988256D65_="
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-4.8 required=5.0
	tests=BAYES_10,HTML_10_20
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

This is a multipart message in MIME format.
--=_alternative 0042984988256D65_=
Content-Type: text/plain; charset="us-ascii"

I think that Mallikarjun, has correctly stated what should/should not be 
done here.  The number of times that an initiator may permit its 
connection request to be redirected is an initiator design consideration. 
It is inappropriate to have a hard limit built into the protocol.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/System Group, San Jose CA
Main Office: (408) 256-0403, Tie: 276-0403, eFax: (408) 904-4688
Alt Office: (408) 997-6136, Cell: (408) 499-9702
Internet Address: hufferd@us.ibm.com




"Mallikarjun C." <cbm@rose.hp.com>
Sent by: owner-ips@ece.cmu.edu
07/15/2003 10:14 AM

 
        To:     "Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>, 
<ips@ece.cmu.edu>
        cc: 
        Subject:        Re: iSCSI: Login Redirect



If this mis-direction is going on to different portals within
the same target node, I would think that it implies a serious
configuration issue within the target node because it either
does not have a global node-level view of the iSCSI service
it offers, or the situation is changing too rapidly to be correct.

If on the other hand, this mis-direction is forcing an 
initiator to shuttle to different target nodes, it usually implies a
lack of a consistent SAN-level view among the target nodes
that are supposed to be doing cooperative redirection (which
is what the feature was meant for).

In either case, I tend to think that the issue is one of implementation/
configuration and placing hard limits on the # of redirections in
the spec is neither reasonable nor enforceable.   I believe that the 
spec doesn't preclude implementations from having a limit (for ex., the 
initiator iSCSI may decide to give up the chase after X attempts and 
report a failure to its ULP).
--
Mallikarjun

Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions
Hewlett-Packard MS 5668 
Roseville CA 95747
cbm@rose.hp.com

----- Original Message ----- 
From: "Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>
To: <ips@ece.cmu.edu>
Sent: Tuesday, July 15, 2003 8:51 AM
Subject: iSCSI: Login Redirect


When a target is moved (Temporary or Permanent), target
sends an appropriate status code and gives the new target
address. Is there a limit on the number of times a target
can redirect login? If not, should we have one?
 
    Initiator logs into Portal A. 
    Target redirects to Portal B.
    Initiator logs into Portal B. 
    Target now redirects to Portal C.
    And so on...
 
Should we have an upper limit on the number of times a target
can redirect the login?
 
thanks!
 -lakshmi





--=_alternative 0042984988256D65_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">I think that Mallikarjun, has correctly stated what should/should not be done here. &nbsp;The number of times that an initiator may permit its connection request to be redirected is an initiator design consideration. &nbsp;It is inappropriate to have a hard limit built into the protocol.<br>
.<br>
.<br>
John L. Hufferd<br>
Senior Technical Staff Member (STSM)<br>
IBM/System Group, San Jose CA<br>
Main Office: (408) 256-0403, Tie: 276-0403, eFax: (408) 904-4688<br>
Alt Office: (408) 997-6136, Cell: (408) 499-9702<br>
Internet Address: hufferd@us.ibm.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>&quot;Mallikarjun C.&quot; &lt;cbm@rose.hp.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: owner-ips@ece.cmu.edu</font>
<p><font size=1 face="sans-serif">07/15/2003 10:14 AM</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&quot;Lakshmi Ramasubramanian&quot; &lt;nramas@windows.microsoft.com&gt;, &lt;ips@ece.cmu.edu&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: iSCSI: Login Redirect</font>
<br></table>
<br>
<br>
<br><font size=2 face="Courier New">If this mis-direction is going on to different portals within<br>
the same target node, I would think that it implies a serious<br>
configuration issue within the target node because it either<br>
does not have a global node-level view of the iSCSI service<br>
it offers, or the situation is changing too rapidly to be correct.<br>
<br>
If on the other hand, this mis-direction is forcing an <br>
initiator to shuttle to different target nodes, it usually implies a<br>
lack of a consistent SAN-level view among the target nodes<br>
that are supposed to be doing cooperative redirection (which<br>
is what the feature was meant for).<br>
<br>
In either case, I tend to think that the issue is one of implementation/<br>
configuration and placing hard limits on the # of redirections in<br>
the spec is neither reasonable nor enforceable. &nbsp; I believe that the <br>
spec doesn't preclude implementations from having a limit (for ex., the <br>
initiator iSCSI may decide to give up the chase after X attempts and <br>
report a failure to its ULP).<br>
--<br>
Mallikarjun<br>
<br>
Mallikarjun Chadalapaka<br>
Networked Storage Architecture<br>
Network Storage Solutions<br>
Hewlett-Packard MS 5668 <br>
Roseville CA 95747<br>
cbm@rose.hp.com<br>
<br>
----- Original Message ----- <br>
From: &quot;Lakshmi Ramasubramanian&quot; &lt;nramas@windows.microsoft.com&gt;<br>
To: &lt;ips@ece.cmu.edu&gt;<br>
Sent: Tuesday, July 15, 2003 8:51 AM<br>
Subject: iSCSI: Login Redirect<br>
<br>
<br>
When a target is moved (Temporary or Permanent), target<br>
sends an appropriate status code and gives the new target<br>
address. Is there a limit on the number of times a target<br>
can redirect login? If not, should we have one?<br>
 <br>
 &nbsp; &nbsp;Initiator logs into Portal A. <br>
 &nbsp; &nbsp;Target redirects to Portal B.<br>
 &nbsp; &nbsp;Initiator logs into Portal B. <br>
 &nbsp; &nbsp;Target now redirects to Portal C.<br>
 &nbsp; &nbsp;And so on...<br>
 <br>
Should we have an upper limit on the number of times a target<br>
can redirect the login?<br>
 <br>
thanks!<br>
 -lakshmi<br>
<br>
<br>
</font>
<br>
<br>
--=_alternative 0042984988256D65_=--
