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 h3OLG5l20359
	for ips-outgoing; Thu, 24 Apr 2003 17:16:05 -0400 (EDT)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from palrel11.hp.com (palrel11.hp.com [156.153.255.246])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h3OLG2F20354
	for <ips@ece.cmu.edu>; Thu, 24 Apr 2003 17:16:02 -0400 (EDT)
Received: from xparelay2.ptp.hp.com (xparelay2.ptp.hp.com [15.1.28.65])
	by palrel11.hp.com (Postfix) with ESMTP
	id A57371C00BEE; Thu, 24 Apr 2003 14:15:56 -0700 (PDT)
Received: from xpabh2.ptp.hp.com (xpabh2.ptp.hp.com [15.1.28.61])
	by xparelay2.ptp.hp.com (Postfix) with ESMTP
	id C18391C000B6; Thu, 24 Apr 2003 14:15:54 -0700 (PDT)
Received: by xpabh2.ptp.hp.com with Internet Mail Service (5.5.2655.55)
	id <JMVGX0AL>; Thu, 24 Apr 2003 14:15:54 -0700
Message-ID: <6BD67FFB937FD411A04F00D0B74FE878102F6142@xrose06.rose.hp.com>
From: "KRUEGER,MARJORIE (HP-Roseville,ex1)" <marjorie.krueger@hp.com>
To: "'Eddy Quicksall'" <eddy_quicksall@ivivity.com>
Cc: ips@ece.cmu.edu
Subject: RE: use of ISID
Date: Thu, 24 Apr 2003 14:15:50 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

The precise use of terms would be to say "each login would be from a
different initiator port".  The term "initiator" is ambiguous until you
qualify it by "device" or "port".  The same initiator device may instantiate
multiple sessions to the same target device by either using one initiator
port and different target ports, or multiple initiator ports to multiple
target ports, etc.

> -----Original Message-----
> From: Eddy Quicksall [mailto:eddy_quicksall@ivivity.com] 
> Sent: Tuesday, April 22, 2003 5:48 PM
> To: wrstuden@wasabisystems.com; mphaneen
> Cc: KRUEGER,MARJORIE (HP-Roseville,ex1); ips@ece.cmu.edu
> Subject: RE: use of ISID
> 
> 
> The new login I was talking about was when it is the same 
> "initiator". The client may do several login/logouts during 
> its initialization. If it uses a different ISID each time, 
> each login will be a different "initiator".
> 
> Eddy
> 
> -----Original Message-----
> From: wrstuden@wasabisystems.com [mailto:wrstuden@wasabisystems.com] 
> Sent: Tuesday, April 22, 2003 1:19 PM
> To: mphaneen
> Cc: KRUEGER,MARJORIE (HP-Roseville,ex1); 'Eddy Quicksall'; 
> ips@ece.cmu.edu
> Subject: Re: use of ISID
> 
> On Fri, 18 Apr 2003, mphaneen wrote:
> 
> > MessageHi,
> >     Though it is a good pratice to show up same SCSI 
> initiator port to 
> > the target wherever possible, a little caution should be exercised 
> > while conservatively re-using ISID.
> >     A session reinstatement would occur if the same ISID is 
> used with 
> > TSIH=0, assuming multiple connections per session in the 
> scenario that 
> > Eddy mentioned.
> 
> True, but that's the point, isn't it? Initiator Name + ISID 
> is the initiator designator (the I in I_T nexus), and an 
> initiator can only have one connection to a given target via 
> a given portal. So you shouldn't try to make a new login that 
> re-uses the ISID, if you already have an existing session.
> 
> Take care,
> 
> Bill
> 
