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 h33LGnV27148
	for ips-outgoing; Thu, 3 Apr 2003 16:16:49 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from ariel.nishansystems.com (ultrex.nishansystems.com [12.36.127.195])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h33LGk327144
	for <ips@ece.cmu.edu>; Thu, 3 Apr 2003 16:16:46 -0500 (EST)
Received: by ariel.nishansystems.com with Internet Mail Service (5.5.2653.19)
	id <2GHLJF90>; Thu, 3 Apr 2003 13:16:40 -0800
Message-ID: <B300BD9620BCD411A366009027C21D9B01F5DC85@ariel.nishansystems.com>
From: Kevin Gibbons <kgibbons@NishanSystems.com>
To: ips@ece.cmu.edu
Cc: "'John Hufferd'" <hufferd@us.ibm.com>,
   Eddy Quicksall
	 <eddy_quicksall@ivivity.com>
Subject: RE: iSCSI: Portal Group clarification
Date: Thu, 3 Apr 2003 13:16:37 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2FA26.4F960C10"
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_01C2FA26.4F960C10
Content-Type: text/plain

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_01C2FA26.4F960C10
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1141" name=GENERATOR></HEAD>
<BODY>
<DIV>
<DIV>
<P><FONT size=2>I have been reviewing the iSCSI Model examples on </FONT><A 
href="http://www.haifa.il.ibm.com/satran/ips"><U><FONT color=#0000ff><FONT 
size=2>http://www.haifa.il.ibm.com/satran/ips</FONT></U></FONT></A><FONT 
size=2>&nbsp;<SPAN class=535550021-03042003>, and am trying&nbsp;<SPAN 
class=016481221-03042003>to </SPAN>get&nbsp;<SPAN class=016481221-03042003>them 
straight in&nbsp;</SPAN>my head.&nbsp; I was hoping someone can 
help.</SPAN></FONT></P>
<P><FONT size=2>Network Entity:&nbsp;<SPAN class=535550021-03042003>C</SPAN>an 
different entities provide access to the same iSCSI Node?<SPAN 
class=535550021-03042003> In </SPAN>1) "iSCSI Configuration Examples", </FONT><A 
href="http://www.haifa.il.ibm.com/satran/ips/iSCSIConfigurationExamples.pdf"><U><FONT 
color=#0000ff><FONT 
size=2>http://www.haifa.il.ibm.com/satran/ips/iSCSIConfigurationExamples.pdf</FONT></U></FONT></A><FONT 
size=2>, the iSCSI Network Entity contain<SPAN class=535550021-03042003>s</SPAN> 
iSCSI Nodes and Network Portals.&nbsp;<SPAN class=535550021-03042003>E</SPAN>ach 
Network Portal has a TCP/IP network address. This limit<SPAN 
class=535550021-03042003>s</SPAN> access to an iSCSI Node to one Entity<SPAN 
class=535550021-03042003>, and</SPAN> seems to agree with the architecture model 
in the iSCSI draft.<SPAN class=535550021-03042003>&nbsp; But </SPAN></FONT><FONT 
size=2>2) "Portal Groups", </FONT><A 
href="http://www.haifa.il.ibm.com/satran/ips/EddyQuicksall-iSCSI-in-diagrams/portal_groups.pdf"><U><FONT 
color=#0000ff><FONT 
size=2>http://www.haifa.il.ibm.com/satran/ips/EddyQuicksall-iSCSI-in-diagrams/portal_groups.pdf</FONT></U></FONT></A><FONT 
size=2>, shows Network Entities&nbsp;<SPAN class=535550021-03042003>that 
</SPAN>provide access to, but do not contain, Network Portals and iSCSI 
Nodes.<SPAN class=535550021-03042003>&nbsp; </SPAN>These feed into Portal Groups 
and then iSCSI Nodes.<SPAN class=535550021-03042003>&nbsp; 
</SPAN>This&nbsp;<SPAN class=535550021-03042003>would </SPAN>mean<SPAN 
class=535550021-03042003> multiple&nbsp;</SPAN>Entities can provide access to 
the same iSCSI Node<SPAN class=535550021-03042003>, and the</SPAN> example<SPAN 
class=535550021-03042003> (2)</SPAN>&nbsp;shows&nbsp;<SPAN 
class=535550021-03042003>this</SPAN>. This seems to disagree with (1). I tried 
but could not map this into the iSCSI draft architecture model.</FONT></P>
<P><FONT size=2>Portal Tags:&nbsp;<SPAN 
class=535550021-03042003>A</SPAN>re&nbsp;<SPAN class=535550021-03042003>they 
</SPAN><SPAN class=535550021-03042003>uniquely </SPAN>defined using 16 bit 
integers?<SPAN class=535550021-03042003>&nbsp; In 1</SPAN>) "iSCSI Configuration 
Examples" figures<SPAN class=535550021-03042003>, the </SPAN>Portal Tags are 
specified using UTF-8 characters.<SPAN class=535550021-03042003>&nbsp; But 
t</SPAN>he&nbsp;<SPAN class=016481221-03042003>included </SPAN>Send Targets 
examples use integer values.<SPAN class=535550021-03042003>&nbsp; In </SPAN>2) 
"Portal Groups"<SPAN class=535550021-03042003>,</SPAN> integer values&nbsp;<SPAN 
class=535550021-03042003>are used </SPAN>for defining Portal Tags. 
This&nbsp;<SPAN class=535550021-03042003>seems to </SPAN>agree with the iSCSI 
draft.</FONT></P>
<P><FONT size=2>Is there a UML/entity-relationship model for the iSCSI 
architecture?<SPAN class=535550021-03042003>&nbsp; This would help me a 
lot.&nbsp; </SPAN>I am aware of one for the iSCSI MIB model, but not the iSCSI 
Architecture.<SPAN class=535550021-03042003>&nbsp;</SPAN></FONT></P>
<P><FONT size=2><SPAN class=535550021-03042003>&nbsp;&nbsp;&nbsp; Many 
</SPAN>Regards, Kevin</FONT></P></DIV></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> John Hufferd 
  [mailto:hufferd@us.ibm.com] <BR><B>Sent:</B> Tuesday, April 01, 2003 11:04 
  PM<BR><B>To:</B> Eddy Quicksall<BR><B>Cc:</B> ips@ece.cmu.edu; Kevin Gibbons; 
  owner-ips@ece.cmu.edu<BR><B>Subject:</B> RE: iSCSI: Portal Group 
  clarification<BR><BR></FONT></DIV><BR><FONT face=sans-serif 
  size=2>Eddy,</FONT> <BR><FONT face=sans-serif size=2>Your point is exactly 
  correct!</FONT> <BR><BR><FONT face=sans-serif size=2>The key point that was 
  being missed was the words at the bottom of the figure on page 40 </FONT><FONT 
  face="Courier New" size=2>which says "(within Network Entity, not 
  shown)".</FONT> <BR><BR><FONT face=sans-serif size=2>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;</FONT> <BR><BR><FONT face=sans-serif 
  size=2>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.)</FONT> 
  <BR><BR><FONT face=sans-serif size=2>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:</FONT> <BR><BR><FONT face="Courier New" size=2>- iSCSI Draft20 
  Appendix D : SendTargets Operation <BR>&nbsp;"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=iqn.1993-11.com.example:diskarray.sn.8675309<BR>&nbsp; &nbsp; 
  &nbsp; &nbsp; TargetAddress=10.1.0.45:3000,1<BR>&nbsp; &nbsp; &nbsp; &nbsp; 
  TargetAddress=10.1.1.45:3000,2<BR>&nbsp; &nbsp; &nbsp; &nbsp; 
  TargetName=iqn.1993-11.com.example:diskarray.sn.1234567<BR>&nbsp; &nbsp; 
  &nbsp; &nbsp; TargetAddress=10.1.0.45:3000,1<BR>&nbsp; &nbsp; &nbsp; &nbsp; 
  TargetAddress=10.1.1.45:3000,2 &nbsp; "</FONT> <BR><FONT face=sans-serif 
  size=2>&nbsp; &nbsp; &nbsp; &nbsp;</FONT> <BR><BR><FONT face=sans-serif 
  size=2>.<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</FONT> <BR><BR><BR>
  <TABLE width="100%">
    <TBODY>
    <TR vAlign=top>
      <TD>
      <TD><FONT face=sans-serif size=1><B>Eddy Quicksall 
        &lt;eddy_quicksall@ivivity.com&gt;</B></FONT> <BR><FONT face=sans-serif 
        size=1>Sent by: owner-ips@ece.cmu.edu</FONT> 
        <P><FONT face=sans-serif size=1>04/01/2003 05:13 PM</FONT> <BR></P>
      <TD><FONT face=Arial size=1>&nbsp; &nbsp; &nbsp; &nbsp; </FONT><BR><FONT 
        face=sans-serif size=1>&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; 
        &nbsp; &nbsp;Kevin Gibbons &lt;kgibbons@NishanSystems.com&gt;, 
        ips@ece.cmu.edu</FONT> <BR><FONT face=sans-serif size=1>&nbsp; &nbsp; 
        &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</FONT> <BR><FONT 
        face=sans-serif size=1>&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; 
        &nbsp; &nbsp; &nbsp;RE: iSCSI: Portal Group clarification</FONT> 
    <BR></TR></TBODY></TABLE><BR><BR><BR><FONT face="Courier New" 
  size=2>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 = 56) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| 
  &nbsp; &nbsp; &nbsp; (TSIH = 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></FONT><BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2FA26.4F960C10--
