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 h0NJ1wJ13253
	for ips-outgoing; Thu, 23 Jan 2003 14:01:58 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from mail1irv.inside.istor.com (host28.istor.com [66.134.214.28])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0NJ1uW13244
	for <ips@ece.cmu.edu>; Thu, 23 Jan 2003 14:01:56 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2C311.CC1BE8D5"
Subject: RE: iSCSI: LUN in a ping
Date: Thu, 23 Jan 2003 11:01:12 -0800
Message-ID: <7D036BD3216A084DB1BD9D62BCEAF290166784@mail1irv.inside.istor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: iSCSI: LUN in a ping
Thread-Index: AcLDEMsFsqO+L51DTW2ik+NJkmE07wAAI1/g
From: "Ken Craig" <kcraig@istor.com>
To: "Julian Satran" <Julian_Satran@il.ibm.com>
Cc: <ips@ece.cmu.edu>
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C2C311.CC1BE8D5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Julo,
=20
For those of us that weren't here 18 months ago can you refresh
us on your explanation or point us to where it is since I too
wonder why a SCSI Target would not use the mechanisms it
already has in place to notify an initiator of a LUN inventory
change?
=20
Thanks,
Ken Craig

	-----Original Message-----
	From: Julian Satran [mailto:Julian_Satran@il.ibm.com]=20
	Sent: Thursday, January 23, 2003 8:47 AM
	To: Eddy Quicksall
	Cc: ips@ece.cmu.edu; Julian Satran; owner-ips@ece.cmu.edu; Rod
Harrison
	Subject: RE: iSCSI: LUN in a ping
=09
=09

	Eddy,=20
=09
	We all appreciate you opinion - but this has been hotly debated
more than 18 months ago.=20
	And I recall sending you an explanation regarding the middle
boxes and how they handle the LUN for routing in a "clustered" target.=20
	And your comment about a "requirement with no good reason"
besides being derogatory does not add any value to the discussion.=20
=09
	Julo=20
=09
=09
=09
Eddy Quicksall <eddy_quicksall@ivivity.com>=20
Sent by: owner-ips@ece.cmu.edu=20

23/01/03 17:19=20

To
Rod Harrison <rod.harrison@windriver.com>, Julian Satran
<julian@cs.haifa.ac.il>, ips@ece.cmu.edu=20
cc
Subject
RE: iSCSI: LUN in a ping

=09




	For that, wouldn't the target generate REPORTED LUNS DATA HAS
CHANGED
	(3F/0E)?
=09
	It is my opinion that this is just another requirement that has
been put on
	the target for no good reason.
=09
	It should be up to the target as to if the LUN field has meaning
and the
	initiator should be the one that has a requirement to echo the
value.
=09
	Eddy
=09
	-----Original Message-----
	From: Rod Harrison [mailto:rod.harrison@windriver.com]
	Sent: Wednesday, January 22, 2003 1:52 PM
	To: Eddy Quicksall; Julian Satran; ips@ece.cmu.edu
	Subject: RE: iSCSI: LUN in a ping
=09
=09
=09
	The initiator might try to rediscover the LUN topology if it
sees a NOP from
	a
	LUN that it previously thought was not present.
=09
	- Rod
=09
	-----Original Message-----
	From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On
Behalf Of
	Eddy Quicksall
	Sent: Wednesday, January 22, 2003 10:28 AM
	To: Julian Satran; Eddy Quicksall; ips@ece.cmu.edu
	Subject: RE: iSCSI: LUN in a ping
=09
=09
	Yes, I remember that but the necessity for the target to set it
should be up
	to the target because the initiator should not be trying to
interpret it (it
	should only be required to echo it).
=09
	Is there a case where the initiator will interpret the LUN?
=09
	Eddy
=09
	-----Original Message-----
	From: Julian Satran [mailto:julian@cs.haifa.ac.il]
	Sent: Wednesday, January 22, 2003 12:43 AM
	To: 'Eddy Quicksall'; ips@ece.cmu.edu
	Subject: RE: iSCSI: LUN in a ping
=09
=09
	TTT & LUN uniquely identify the "origin" (if target is a
"composite"
	each of the parts can issue their own TTTs - no coordination
needed).
=09
	Regards,
	Julo
=09
=09
	-----Original Message-----
	From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu] On
Behalf Of
	Eddy Quicksall
	Sent: 22 January, 2003 00:07
	To: ips@ece.cmu.edu
	Subject: iSCSI: LUN in a ping
=09
=09
	Does anyone know why we added "the LUN must be valid" for a
target
	initiated ping? It would seem that it is N/A when the ping is
just being
	used to checkup on the connection.
=09
	What will the initiator do with the LUN anyway?
=09
	10.19.3 LUN
	A LUN MUST be set to a correct value when the Target Transfer
Tag is
	valid (not the reserved value 0xffffffff).
=09
	Eddy
	mailto: Eddy_Quicksall@iVivity.com
=09
=09
=09


------_=_NextPart_001_01C2C311.CC1BE8D5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D682585718-23012003>Hello=20
Julo,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D682585718-23012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D682585718-23012003>For=20
those of us that weren't here 18 months ago can you =
refresh</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D682585718-23012003>us on=20
your explanation or point us to where it is since I =
too</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D682585718-23012003>wonder=20
why a SCSI Target would not use the mechanisms it</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D682585718-23012003>already has in place to notify an initiator =
of a LUN=20
inventory</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D682585718-23012003>change?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D682585718-23012003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D682585718-23012003>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D682585718-23012003>Ken=20
Craig</SPAN></FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Julian Satran=20
  [mailto:Julian_Satran@il.ibm.com] <BR><B>Sent:</B> Thursday, January =
23, 2003=20
  8:47 AM<BR><B>To:</B> Eddy Quicksall<BR><B>Cc:</B> ips@ece.cmu.edu; =
Julian=20
  Satran; owner-ips@ece.cmu.edu; Rod Harrison<BR><B>Subject:</B> RE: =
iSCSI: LUN=20
  in a ping<BR><BR></FONT></DIV><BR><FONT face=3Dsans-serif =
size=3D2>Eddy,</FONT>=20
  <BR><BR><FONT face=3Dsans-serif size=3D2>We all appreciate you opinion =
- but this=20
  has been hotly debated more than 18 months ago.</FONT> <BR><FONT=20
  face=3Dsans-serif size=3D2>And I recall sending you an explanation =
regarding the=20
  middle boxes and how they handle the LUN for routing in a "clustered"=20
  target.</FONT> <BR><FONT face=3Dsans-serif size=3D2>And your comment =
about a=20
  "requirement with no good reason" besides being derogatory does not =
add any=20
  value to the discussion.</FONT> <BR><BR><FONT face=3Dsans-serif=20
  size=3D2>Julo</FONT> <BR><BR><BR>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD width=3D"40%"><FONT face=3Dsans-serif size=3D1><B>Eddy =
Quicksall=20
        &lt;eddy_quicksall@ivivity.com&gt;</B> </FONT><BR><FONT =
face=3Dsans-serif=20
        size=3D1>Sent by: owner-ips@ece.cmu.edu</FONT>=20
        <P><FONT face=3Dsans-serif size=3D1>23/01/03 17:19</FONT> </P>
      <TD width=3D"59%">
        <TABLE width=3D"100%">
          <TBODY>
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
            <TD vAlign=3Dtop><FONT face=3Dsans-serif size=3D1>Rod =
Harrison=20
              &lt;rod.harrison@windriver.com&gt;, Julian Satran=20
              &lt;julian@cs.haifa.ac.il&gt;, ips@ece.cmu.edu</FONT>=20
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
            <TD vAlign=3Dtop>
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
            <TD vAlign=3Dtop><FONT face=3Dsans-serif size=3D1>RE: iSCSI: =
LUN in a=20
              ping</FONT></TR></TBODY></TABLE><BR>
        <TABLE>
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
            =
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT=20
  size=3D2><TT>For that, wouldn't the target generate REPORTED LUNS DATA =
HAS=20
  CHANGED<BR>(3F/0E)?<BR><BR>It is my opinion that this is just another=20
  requirement that has been put on<BR>the target for no good =
reason.<BR><BR>It=20
  should be up to the target as to if the LUN field has meaning and=20
  the<BR>initiator should be the one that has a requirement to echo the=20
  value.<BR><BR>Eddy<BR><BR>-----Original Message-----<BR>From: Rod =
Harrison=20
  [mailto:rod.harrison@windriver.com]<BR>Sent: Wednesday, January 22, =
2003 1:52=20
  PM<BR>To: Eddy Quicksall; Julian Satran; ips@ece.cmu.edu<BR>Subject: =
RE:=20
  iSCSI: LUN in a ping<BR><BR><BR><BR>The initiator might try to =
rediscover the=20
  LUN topology if it sees a NOP from<BR>a<BR>LUN that it previously =
thought was=20
  not present.<BR><BR>- Rod<BR><BR>-----Original Message-----<BR>From:=20
  owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On Behalf =
Of<BR>Eddy=20
  Quicksall<BR>Sent: Wednesday, January 22, 2003 10:28 AM<BR>To: Julian =
Satran;=20
  Eddy Quicksall; ips@ece.cmu.edu<BR>Subject: RE: iSCSI: LUN in a=20
  ping<BR><BR><BR>Yes, I remember that but the necessity for the target =
to set=20
  it should be up<BR>to the target because the initiator should not be =
trying to=20
  interpret it (it<BR>should only be required to echo it).<BR><BR>Is =
there a=20
  case where the initiator will interpret the=20
  LUN?<BR><BR>Eddy<BR><BR>-----Original Message-----<BR>From: Julian =
Satran=20
  [mailto:julian@cs.haifa.ac.il]<BR>Sent: Wednesday, January 22, 2003 =
12:43=20
  AM<BR>To: 'Eddy Quicksall'; ips@ece.cmu.edu<BR>Subject: RE: iSCSI: LUN =
in a=20
  ping<BR><BR><BR>TTT &amp; LUN uniquely identify the "origin" (if =
target is a=20
  "composite"<BR>each of the parts can issue their own TTTs - no =
coordination=20
  needed).<BR><BR>Regards,<BR>Julo<BR><BR><BR>-----Original=20
  Message-----<BR>From: owner-ips@ece.cmu.edu =
[mailto:owner-ips@ece.cmu.edu] On=20
  Behalf Of<BR>Eddy Quicksall<BR>Sent: 22 January, 2003 00:07<BR>To:=20
  ips@ece.cmu.edu<BR>Subject: iSCSI: LUN in a ping<BR><BR><BR>Does =
anyone know=20
  why we added "the LUN must be valid" for a target<BR>initiated ping? =
It would=20
  seem that it is N/A when the ping is just being<BR>used to checkup on =
the=20
  connection.<BR><BR>What will the initiator do with the LUN=20
  anyway?<BR><BR>10.19.3 LUN<BR>A LUN MUST be set to a correct value =
when the=20
  Target Transfer Tag is<BR>valid (not the reserved value=20
  0xffffffff).<BR><BR>Eddy<BR>mailto:=20
  =
Eddy_Quicksall@iVivity.com<BR><BR></TT></FONT><BR></BLOCKQUOTE></BODY></H=
TML>
=00
------_=_NextPart_001_01C2C311.CC1BE8D5--
