Re: iSCSI: multiple sessions b/n a pair of WWUIs.

["John Hufferd" <hufferd@us.ibm.com>]

Santosh,
In the attached you are getting you wishes in the way of what is Required.
The Hard requirement is that the iSCSI Initiator Port have a ISID that is
unique to a specific target Node (actually Target iSCSI Port).  It is nice
that you want to used it (the ISID in the way you suggest, however, there
may be several iSCSI Initiator Ports on any iSCSI Initiator Node and that
means that you must find a way to allocate out the ISID value range to each
iSCSI Initiator  Port.   Quite frankly I believe you should probably should
use another indexing method, and let a single ISID be used by each iSCSI
Initiator Port.

However, I am getting the feeling that we are talking past each other, and
some how not communicating.  Not sure if it is my fault or not.

.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/SSG San Jose Ca
(408) 256-0403, Tie: 276-0403,  eFax: (408) 904-4688
Internet address: hufferd@us.ibm.com


Santosh Rao <santoshr@cup.hp.com>@ece.cmu.edu on 05/08/2001 11:03:27 AM

Sent by:  owner-ips@ece.cmu.edu


To:   ips@ece.cmu.edu
cc:
Subject:  Re: iSCSI: multiple sessions b/n a pair of WWUIs.



Douglas Otis wrote:

>  The usefulness of ISID is also
> diminished if the client is not expected to maintain this value as unique
> across all Targets.

I agree with the above and have stated to similar effect in my response
to Matt. A practical usage of ISID within an initiator node name space
is to assign it as unique across all targets, allowing the same ISID to
be used as a lookup key of the session for any given target port/node.

Not applying uniqueness in ISID assignment across all targets would then
require initiators to implement a second key mechanism for target
lookup.

- Santosh