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 09:06:12 -0400
X-Sieve: CMU Sieve 2.2
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by newbox.ece.cmu.edu (Postfix) with ESMTP id B46B23206
	for <ipsml@ece.cmu.edu>; Wed, 16 Jul 2003 09:06:12 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 3D3FAB1; Wed, 16 Jul 2003 09:06:12 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by osgood.ece.cmu.edu (Postfix) with ESMTP
	id 4B26E91; Wed, 16 Jul 2003 09:06:00 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id A85C889DB; Wed, 16 Jul 2003 09:05:41 -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 97C7089D6
	for <ips-outgoing@sos.ece.cmu.edu>; Wed, 16 Jul 2003 09:05:41 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 645AA111; Wed, 16 Jul 2003 09:05:41 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 365A1138; Wed, 16 Jul 2003 09:05:41 -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 1EBCA111
	for <ips-outgoing@ece.cmu.edu>; Wed, 16 Jul 2003 09:05:36 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 058FE89DD; Wed, 16 Jul 2003 09:05:36 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Delivered-To: ips@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 4245C89D6
	for <ips@sos.ece.cmu.edu>; Wed, 16 Jul 2003 09:05:34 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id 738DD9A; Wed, 16 Jul 2003 09:05:33 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id 340C57B; Wed, 16 Jul 2003 09:05:33 -0400 (EDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.131])
	by bache.ece.cmu.edu (Postfix) with ESMTP
	id D12B89A; Wed, 16 Jul 2003 09:05:25 -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 h6GD5Dj3173168;
	Wed, 16 Jul 2003 09:05:14 -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 h6GD57Mb163190;
	Wed, 16 Jul 2003 07:05:07 -0600
To: ips@ece.cmu.edu
Cc: "Mallikarjun C." <cbm@rose.hp.com>,
	"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: <OF6D1BD911.CFF612E9-ON88256D65.0046C0CD-88256D65.0047DC4A@us.ibm.com>
Date: Wed, 16 Jul 2003 06:05:06 -0700
X-MIMETrack: Serialize by Router on D03NM115/03/M/IBM(Release 6.0.1 [IBM]|June 10, 2003) at
 07/16/2003 07:05:12,
	Serialize complete at 07/16/2003 07:05:12
Content-Type: multipart/alternative; boundary="=_alternative 0047DA3488256D65_="
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-4.2 required=5.0
	tests=BAYES_10,HTML_20_30
	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 0047DA3488256D65_=
Content-Type: text/plain; charset="us-ascii"

Extending my own note... I also believe it would be wrong to set a minimum 
number of guaranteed redirects.  This is because, I expect several system 
vendors to use iSCSI as a DAS technology as well as SAN technology. 
(Similar to the way a number of vendors "Racked" their FC external Raid 
controllers together with the server as a Direct Connection.)  When used 
in this manner the customer does not even need to think about the system 
being on a SAN.  Yet the Storage/System Vendor could use the very same 
Raid controller, which they use in a SAN, as a direct attachment to the 
Server in a RACK.  In this environment if any redirect occur, it might be 
considered a error.

So in the above DAS environment having a minimum is, IMHO, not approprate.

Instead, the permissible number of redirects is an administrative or 
implementation setting. 
.
.
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




John Hufferd/San Jose/IBM@IBMUS
Sent by: owner-ips@ece.cmu.edu
07/16/2003 05:07 AM

 
        To:     "Mallikarjun C." <cbm@rose.hp.com>
        cc:     ips@ece.cmu.edu, "Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>, 
owner-ips@ece.cmu.edu
        Subject:        Re: iSCSI: Login Redirect




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 0047DA3488256D65_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Extending my own note... I also believe it would be wrong to set a minimum number of guaranteed redirects. &nbsp;This is because, I expect several system vendors to use iSCSI as a DAS technology as well as SAN technology. &nbsp;(Similar to the way a number of vendors &quot;Racked&quot; their FC external Raid controllers together with the server as a Direct Connection.) &nbsp;When used in this manner the customer does not even need to think about the system being on a SAN. &nbsp;Yet the Storage/System Vendor could use the very same Raid controller, which they use in a SAN, as a direct attachment to the Server in a RACK. &nbsp;In this environment if any redirect occur, it might be considered a error.</font>
<br>
<br><font size=2 face="sans-serif">So in the above DAS environment having a minimum is, IMHO, not approprate.</font>
<br>
<br><font size=2 face="sans-serif">Instead, the permissible number of redirects is an administrative or implementation setting. <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>John Hufferd/San Jose/IBM@IBMUS</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/16/2003 05:07 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;Mallikarjun C.&quot; &lt;cbm@rose.hp.com&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;ips@ece.cmu.edu, &quot;Lakshmi Ramasubramanian&quot; &lt;nramas@windows.microsoft.com&gt;, owner-ips@ece.cmu.edu</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="sans-serif"><br>
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><font size=3 face="Times New Roman"> <br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=1%>
<td width=30%><font size=1 face="sans-serif"><b>&quot;Mallikarjun C.&quot; &lt;cbm@rose.hp.com&gt;</b></font><font size=3 face="Times New Roman"> </font><font size=1 face="sans-serif"><br>
Sent by: owner-ips@ece.cmu.edu</font><font size=3 face="Times New Roman"> </font>
<p><font size=1 face="sans-serif">07/15/2003 10:14 AM</font><font size=3 face="Times New Roman"> </font>
<td width=67%><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font><font size=1 face="sans-serif"><br>
 &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><font size=3 face="Times New Roman"> </font><font size=1 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;cc: &nbsp; &nbsp; &nbsp; &nbsp;</font><font size=3 face="Times New Roman"> </font><font size=1 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;Subject: &nbsp; &nbsp; &nbsp; &nbsp;Re: iSCSI: Login Redirect</font><font size=3 face="Times New Roman"> </font></table>
<br><font size=3 face="Times New Roman"><br>
<br>
</font><font size=2 face="Courier New"><br>
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; Initiator logs into Portal A. </font>
<br><font size=2 face="Courier New">&nbsp; &nbsp;Target redirects to Portal B.<br>
 &nbsp; Initiator logs into Portal B. <br>
 &nbsp; Target now redirects to Portal C.<br>
 &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>
</font><font size=3 face="Times New Roman"><br>
<br>
</font>
<br>
<br>
--=_alternative 0047DA3488256D65_=--
