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 h33MMAg01362
	for ips-outgoing; Thu, 3 Apr 2003 17:22:10 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from mail.ivivity.com ([64.238.111.99])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h33MM6301353
	for <ips@ece.cmu.edu>; Thu, 3 Apr 2003 17:22:06 -0500 (EST)
Received: by ATLOPS with Internet Mail Service (5.5.2653.19)
	id <2CY0SCG6>; Thu, 3 Apr 2003 17:22:05 -0500
Message-ID: <AEC4671C8179D61194DE0002B328BDD262B574@ATLOPS>
From: Eddy Quicksall <eddy_quicksall@ivivity.com>
To: Kevin Gibbons <kgibbons@NishanSystems.com>
Cc: "'John Hufferd'" <hufferd@us.ibm.com>, ips@ece.cmu.edu
Subject: RE: iSCSI: Portal Group clarification
Date: Thu, 3 Apr 2003 17:22:04 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2FA2F.747F4560"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2FA2F.747F4560
Content-Type: text/plain

I commented to the 1st part but I don't understand the 2nd part. I didn't
specify the "type" of integer in the Portal Tags. Please clear this up.
 
Eddy
 
-----Original Message-----
From: Kevin Gibbons [mailto:kgibbons@NishanSystems.com] 
Sent: Thursday, April 03, 2003 4:17 PM
To: ips@ece.cmu.edu
Cc: 'John Hufferd'; Eddy Quicksall
Subject: RE: iSCSI: Portal Group clarification
 
I have been reviewing the iSCSI Model examples on
<http://www.haifa.il.ibm.com/satran/ips>
http://www.haifa.il.ibm.com/satran/ips , and am trying to get them straight
in my head.  I was hoping someone can help.
Network Entity: Can different entities provide access to the same iSCSI
Node? In 1) "iSCSI Configuration Examples",
<http://www.haifa.il.ibm.com/satran/ips/iSCSIConfigurationExamples.pdf>
http://www.haifa.il.ibm.com/satran/ips/iSCSIConfigurationExamples.pdf, the
iSCSI Network Entity contains iSCSI Nodes and Network Portals. Each Network
Portal has a TCP/IP network address. This limits access to an iSCSI Node to
one Entity, and seems to agree with the architecture model in the iSCSI
draft.  But 2) "Portal Groups",
<http://www.haifa.il.ibm.com/satran/ips/EddyQuicksall-iSCSI-in-diagrams/port
al_groups.pdf>
http://www.haifa.il.ibm.com/satran/ips/EddyQuicksall-iSCSI-in-diagrams/porta
l_groups.pdf, shows Network Entities that provide access to, but do not
contain, Network Portals and iSCSI Nodes.  These feed into Portal Groups and
then iSCSI Nodes.  This would mean multiple Entities can provide access to
the same iSCSI Node, and the example (2) shows this. This seems to disagree
with (1). I tried but could not map this into the iSCSI draft architecture
model.
Portal Tags: Are they uniquely defined using 16 bit integers?  In 1) "iSCSI
Configuration Examples" figures, the Portal Tags are specified using UTF-8
characters.  But the included Send Targets examples use integer values.  In
2) "Portal Groups", integer values are used for defining Portal Tags. This
seems to agree with the iSCSI draft.
Is there a UML/entity-relationship model for the iSCSI architecture?  This
would help me a lot.  I am aware of one for the iSCSI MIB model, but not the
iSCSI Architecture. 
    Many Regards, Kevin
-----Original Message-----
From: John Hufferd [mailto:hufferd@us.ibm.com] 
Sent: Tuesday, April 01, 2003 11:04 PM
To: Eddy Quicksall
Cc: ips@ece.cmu.edu; Kevin Gibbons; owner-ips@ece.cmu.edu
Subject: RE: iSCSI: Portal Group clarification

Eddy, 
Your point is exactly correct! 

The key point that was being missed was the words at the bottom of the
figure on page 40 which says "(within Network Entity, not shown)". 

When one has more than one target (node) within a Network Entity, the portal
(IP Address:Port) can be part of any of the enclosed Targets.  That is
because the path to the Target is defined by the portal (IP Address:Port)
and the Target Name.  This is reasonable since nothing is ambiguous about
the description of the path that is intended.   

Having said that, there is also NO requirement that all portals need be
connectable to all targets within the Network Entity.  This is an
implementation decision.  (Just thought I would through that in.) 

Your point is also supported by the figure in section 3.4  and also the
following example that describes what is returned by SendTargets for a
Network Entity that has two iSCSI targets: 

- iSCSI Draft20 Appendix D : SendTargets Operation 
 "The next example has two internal iSCSI targets, each accessible via
  two different ports with different IP addresses.  The following is
  the text response:

        TargetName=iqn.1993-11.com.example:diskarray.sn.8675309
        TargetAddress=10.1.0.45:3000,1
        TargetAddress=10.1.1.45:3000,2
        TargetName=iqn.1993-11.com.example:diskarray.sn.1234567
        TargetAddress=10.1.0.45:3000,1
        TargetAddress=10.1.1.45:3000,2   " 
        

.
.
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
Home Office: (408) 997-6136, Cell: (408) 499-9702
Internet Address: hufferd@us.ibm.com 



 
Eddy Quicksall <eddy_quicksall@ivivity.com> 
Sent by: owner-ips@ece.cmu.edu 
04/01/2003 05:13 PM 
        
        To:        Kevin Gibbons <kgibbons@NishanSystems.com>,
ips@ece.cmu.edu 
        cc:         
        Subject:        RE: iSCSI: Portal Group clarification 



Yes.

Note however that a Network Portal can belong to more than one Target Portal
Group but only one Target Portal Group within a single node (which is a
target in this context).

Eddy

-----Original Message-----
From: Kevin Gibbons [mailto:kgibbons@NishanSystems.com] 
Sent: Tuesday, April 01, 2003 6:39 PM
To: ips@ece.cmu.edu
Subject: iSCSI: Portal Group clarification

Hi, I would like to make sure I understand the iSCSI model correctly.  Can
anyone confirm that a Portal, providing access to a target, is part of
exactly one Portal Group at a time?  My reading of the spec indicates this
is true.  That each Portal has a 16 bit Portal Group tag.  But I would like
to make sure.

I believe that in iSCSI draft 20, it states that a Portal can be part of
exactly one Portal Group.  Please see page 15:

  - Portal Groups: iSCSI supports multiple connections within the same
  session; some implementations will have the ability to combine
  connections in a session across multiple Network Portals. A Portal
  Group defines a set of Network Portals within an iSCSI Network
  Entity that collectively supports the capability of coordinating a
  session with connections spanning these portals. Not all Network
  Portals within a Portal Group need participate in every session
  connected through that Portal Group. One or more Portal Groups may
  provide access to an iSCSI Node. Each Network Portal, as utilized by
  a given iSCSI Node, belongs to exactly one portal group within that
  node.

                Also, please see page 39 for similar wording.  There is also
a
figure on page 40:

    ----------------------------IP Network---------------------
           |               |                    |
      +----|---------------|-----+         +----|---------+
      | +---------+  +---------+ |         | +---------+  |
      | | Network |  | Network | |         | | Network |  |
      | | Portal  |  | Portal  | |         | | Portal  |  |
      | +--|------+  +---------+ |         | +---------+  |
      |    |               |     |         |    |         |
      |    |    Portal     |     |         |    | Portal  |
      |    |    Group 1    |     |         |    | Group 2 |
      +--------------------------+         +--------------+
           |               |                    |
  +--------|---------------|--------------------|--------------------+
  |        |               |                    |                    |
  |  +----------------------------+  +-----------------------------+ |
  |  | iSCSI Session (Target side)|  | iSCSI Session (Target side) | |
  |  |                            |  |                             | |
  |  |       (TSIH = 56)          |  |       (TSIH = 48)           | |
  |  +----------------------------+  +-----------------------------+ |
  |                                                                  |
  |                     iSCSI Target Node                            |
  |             (within Network Entity, not shown)                   |
  +------------------------------------------------------------------+


Please let me know if I am in error.
                Thanks very much! Kevin

-------------------------------------------------
Kevin Gibbons
Nishan Systems, Inc.
kgibbons@NishanSystems.com
(408) 519-3756
-------------------------------------------------



------_=_NextPart_001_01C2FA2F.747F4560
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C2FA05.8A7A0C30">
<title>Message</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:"Times New Roman";
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:auto;
	mso-font-signature:0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I commented to the 1<sup>st</sup> =
part but
I don't understand the 2<sup>nd</sup> part. I didn't specify the "type"
of integer in the Portal Tags. Please clear this =
up.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Eddy<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Kevin Gibbons
[mailto:kgibbons@NishanSystems.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, April =
03, 2003
4:17 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> ips@ece.cmu.edu<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'John Hufferd'; Eddy =
Quicksall<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: iSCSI: =
Portal Group
clarification</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>I have been reviewing the iSCSI Model =
examples on </span></font><a
href=3D"http://www.haifa.il.ibm.com/satran/ips"><font size=3D2><span
style=3D'font-size:10.0pt'>http://www.haifa.il.ibm.com/satran/ips</span>=
</font></a><font
size=3D2><span style=3D'font-size:10.0pt'>&nbsp;, and am trying&nbsp;to
get&nbsp;them straight in&nbsp;my head.&nbsp; I was hoping someone can =
help.</span></font><o:p></o:p></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Network Entity:&nbsp;Can different entities =
provide
access to the same iSCSI Node? In 1) &quot;iSCSI Configuration =
Examples&quot;, </span></font><a
href=3D"http://www.haifa.il.ibm.com/satran/ips/iSCSIConfigurationExample=
s.pdf"><font
size=3D2><span =
style=3D'font-size:10.0pt'>http://www.haifa.il.ibm.com/satran/ips/iSCSIC=
onfigurationExamples.pdf</span></font></a><font
size=3D2><span style=3D'font-size:10.0pt'>, the iSCSI Network Entity =
contains iSCSI
Nodes and Network Portals.&nbsp;Each Network Portal has a TCP/IP =
network
address. This limits access to an iSCSI Node to one Entity, and seems =
to agree
with the architecture model in the iSCSI draft.&nbsp; But 2) =
&quot;Portal
Groups&quot;, </span></font><a
href=3D"http://www.haifa.il.ibm.com/satran/ips/EddyQuicksall-iSCSI-in-di=
agrams/portal_groups.pdf"><font
size=3D2><span =
style=3D'font-size:10.0pt'>http://www.haifa.il.ibm.com/satran/ips/EddyQu=
icksall-iSCSI-in-diagrams/portal_groups.pdf</span></font></a><font
size=3D2><span style=3D'font-size:10.0pt'>, shows Network =
Entities&nbsp;that
provide access to, but do not contain, Network Portals and iSCSI =
Nodes.&nbsp;
These feed into Portal Groups and then iSCSI Nodes.&nbsp; =
This&nbsp;would mean
multiple&nbsp;Entities can provide access to the same iSCSI Node, and =
the
example (2)&nbsp;shows&nbsp;this. This seems to disagree with (1). I =
tried but
could not map this into the iSCSI draft architecture =
model.</span></font><o:p></o:p></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Portal Tags:&nbsp;Are&nbsp;they uniquely =
defined using
16 bit integers?&nbsp; In 1) &quot;iSCSI Configuration Examples&quot; =
figures,
the Portal Tags are specified using UTF-8 characters.&nbsp; But
the&nbsp;included Send Targets examples use integer values.&nbsp; In 2)
&quot;Portal Groups&quot;, integer values&nbsp;are used for defining =
Portal
Tags. This&nbsp;seems to agree with the iSCSI =
draft.</span></font><o:p></o:p></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>Is there a UML/entity-relationship model for =
the iSCSI
architecture?&nbsp; This would help me a lot.&nbsp; I am aware of one =
for the
iSCSI MIB model, but not the iSCSI =
Architecture.&nbsp;</span></font><o:p></o:p></p>

<p style=3D'margin-left:.5in'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; Many Regards, =
Kevin</span></font><o:p></o:p></p>

</div>

</div>

<blockquote =
style=3D'margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:0in;margin-right:0in;ma=
rgin-bottom:
12.0pt;margin-left:.5in'><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> John Hufferd
[mailto:hufferd@us.ibm.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 01, =
2003
11:04 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Eddy Quicksall<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> ips@ece.cmu.edu; =
Kevin
Gibbons; owner-ips@ece.cmu.edu<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: iSCSI: =
Portal Group
clarification</span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
</span></font><font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;
font-family:sans-serif'>Eddy,</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Your
point is exactly correct!</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>The
key point that was being missed was the words at the bottom of the =
figure on
page 40 </span></font><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;font-family:"Courier New"'>which says &quot;(within Network =
Entity, not
shown)&quot;.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>When
one has more than one target (node) within a Network Entity, the portal =
(IP
Address:Port) can be part of any of the enclosed Targets. &nbsp;That is =
because
the path to the Target is defined by the portal (IP Address:Port) and =
the
Target Name. &nbsp;This is reasonable since nothing is ambiguous about =
the
description of the path that is intended. &nbsp;</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Having
said that, there is also NO requirement that all portals need be =
connectable to
all targets within the Network Entity. &nbsp;This is an implementation
decision. &nbsp;(Just thought I would through that in.)</span></font> =
<br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Your
point is also supported by the figure in section 3.4 &nbsp;and also the
following example that describes what is returned by SendTargets for a =
Network
Entity that has two iSCSI targets:</span></font> <br>
<br>
<font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>-
iSCSI Draft20 Appendix D : SendTargets Operation <br>
&nbsp;&quot;The next example has two internal iSCSI targets, each =
accessible
via<br>
&nbsp; two different ports with different IP addresses. &nbsp;The =
following is<br>
&nbsp; the text response:<br>
<br>
&nbsp; &nbsp; &nbsp; &nbsp;
TargetName=3Diqn.1993-11.com.example:diskarray.sn.8675309<br>
&nbsp; &nbsp; &nbsp; &nbsp; TargetAddress=3D10.1.0.45:3000,1<br>
&nbsp; &nbsp; &nbsp; &nbsp; TargetAddress=3D10.1.1.45:3000,2<br>
&nbsp; &nbsp; &nbsp; &nbsp;
TargetName=3Diqn.1993-11.com.example:diskarray.sn.1234567<br>
&nbsp; &nbsp; &nbsp; &nbsp; TargetAddress=3D10.1.0.45:3000,1<br>
&nbsp; &nbsp; &nbsp; &nbsp; TargetAddress=3D10.1.1.45:3000,2 &nbsp; =
&quot;</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp; &nbsp; &nbsp;</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>.<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>
Home Office: (408) 997-6136, Cell: (408) 499-9702<br>
Internet Address: hufferd@us.ibm.com</span></font> <br =
style=3D'mso-special-character:
line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
 style=3D'width:100.0%;mso-cellspacing:1.5pt;margin-left:.5in'>
 <tr style=3D'mso-yfti-irow:0;mso-yfti-lastrow:yes'>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal><b><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:
  7.5pt;font-family:sans-serif;font-weight:bold'>Eddy Quicksall
  &lt;eddy_quicksall@ivivity.com&gt;</span></font></b> <br>
  <font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>Sent
  by: owner-ips@ece.cmu.edu</span></font> <o:p></o:p></p>
  <p><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:
  sans-serif'>04/01/2003 05:13 PM</span></font> <o:p></o:p></p>
  </td>
  <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:7.5pt;
  font-family:Arial'>&nbsp; &nbsp; &nbsp; &nbsp; </span></font><br>
  <font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>&nbsp;
  &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;Kevin Gibbons
  &lt;kgibbons@NishanSystems.com&gt;, ips@ece.cmu.edu</span></font> =
<br>
  <font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>&nbsp;
  &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</span></font> =
<br>
  <font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>&nbsp;
  &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;RE: iSCSI: =
Portal
  Group clarification</span></font> <o:p></o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
<br>
<br>
</span></font><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Yes.<br>
<br>
Note however that a Network Portal can belong to more than one Target =
Portal<br>
Group but only one Target Portal Group within a single node (which is =
a<br>
target in this context).<br>
<br>
Eddy<br>
<br>
-----Original Message-----<br>
From: Kevin Gibbons [mailto:kgibbons@NishanSystems.com] <br>
Sent: Tuesday, April 01, 2003 6:39 PM<br>
To: ips@ece.cmu.edu<br>
Subject: iSCSI: Portal Group clarification<br>
<br>
Hi, I would like to make sure I understand the iSCSI model correctly. =
&nbsp;Can<br>
anyone confirm that a Portal, providing access to a target, is part =
of<br>
exactly one Portal Group at a time? &nbsp;My reading of the spec =
indicates this<br>
is true. &nbsp;That each Portal has a 16 bit Portal Group tag. =
&nbsp;But I
would like<br>
to make sure.<br>
<br>
I believe that in iSCSI draft 20, it states that a Portal can be part =
of<br>
exactly one Portal Group. &nbsp;Please see page 15:<br>
<br>
&nbsp; - Portal Groups: iSCSI supports multiple connections within the =
same<br>
&nbsp; session; some implementations will have the ability to =
combine<br>
&nbsp; connections in a session across multiple Network Portals. A =
Portal<br>
&nbsp; Group defines a set of Network Portals within an iSCSI =
Network<br>
&nbsp; Entity that collectively supports the capability of coordinating =
a<br>
&nbsp; session with connections spanning these portals. Not all =
Network<br>
&nbsp; Portals within a Portal Group need participate in every =
session<br>
&nbsp; connected through that Portal Group. One or more Portal Groups =
may<br>
&nbsp; provide access to an iSCSI Node. Each Network Portal, as =
utilized by<br>
&nbsp; a given iSCSI Node, belongs to exactly one portal group within =
that<br>
&nbsp; node.<br>
<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Also, please =
see page
39 for similar wording. &nbsp;There is also a<br>
figure on page 40:<br>
<br>
&nbsp; &nbsp; ----------------------------IP =
Network---------------------<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp;|<br>
&nbsp; &nbsp; &nbsp; +----|---------------|-----+ &nbsp; &nbsp; &nbsp; =
&nbsp;
+----|---------+<br>
&nbsp; &nbsp; &nbsp; | +---------+ &nbsp;+---------+ | &nbsp; &nbsp; =
&nbsp;
&nbsp; | +---------+ &nbsp;|<br>
&nbsp; &nbsp; &nbsp; | | Network | &nbsp;| Network | | &nbsp; &nbsp; =
&nbsp;
&nbsp; | | Network | &nbsp;|<br>
&nbsp; &nbsp; &nbsp; | | Portal &nbsp;| &nbsp;| Portal &nbsp;| | &nbsp; =
&nbsp;
&nbsp; &nbsp; | | Portal &nbsp;| &nbsp;|<br>
&nbsp; &nbsp; &nbsp; | +--|------+ &nbsp;+---------+ | &nbsp; &nbsp; =
&nbsp;
&nbsp; | +---------+ &nbsp;|<br>
&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;
&nbsp; | &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;| =
&nbsp;
&nbsp; &nbsp; &nbsp; |<br>
&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;| &nbsp; &nbsp;Portal &nbsp; &nbsp; =
|
&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;| Portal =
&nbsp;|<br>
&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;| &nbsp; &nbsp;Group 1 &nbsp; =
&nbsp;|
&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;| Group 2 =
|<br>
&nbsp; &nbsp; &nbsp; +--------------------------+ &nbsp; &nbsp; &nbsp; =
&nbsp;
+--------------+<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp;|<br>
&nbsp; =
+--------|---------------|--------------------|--------------------+<br>=

&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;
&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;|
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;|<br>
&nbsp; | &nbsp;+----------------------------+
&nbsp;+-----------------------------+ |<br>
&nbsp; | &nbsp;| iSCSI Session (Target side)| &nbsp;| iSCSI Session =
(Target
side) | |<br>
&nbsp; | &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | |<br>
&nbsp; | &nbsp;| &nbsp; &nbsp; &nbsp; (TSIH =3D 56) &nbsp; &nbsp; =
&nbsp; &nbsp;
&nbsp;| &nbsp;| &nbsp; &nbsp; &nbsp; (TSIH =3D 48) &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; | |<br>
&nbsp; | &nbsp;+----------------------------+
&nbsp;+-----------------------------+ |<br>
&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp;|<br>
&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
iSCSI Target Node &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|<br>
&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (within Network =
Entity, not
shown) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
|<br>
&nbsp; =
+------------------------------------------------------------------+<br>=

<br>
<br>
Please let me know if I am in error.<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Thanks very =
much! Kevin<br>
<br>
-------------------------------------------------<br>
Kevin Gibbons<br>
Nishan Systems, Inc.<br>
kgibbons@NishanSystems.com<br>
(408) 519-3756<br>
-------------------------------------------------<br =
style=3D'mso-special-character:
line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]></span></font><o:p></o:p></p>

</blockquote>

</div>

</body>

</html>

------_=_NextPart_001_01C2FA2F.747F4560--
