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 h3PMAvL23606
	for ips-outgoing; Fri, 25 Apr 2003 18:10:57 -0400 (EDT)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from maho3msx2.corp.emc.com (maho3msx2.corp.emc.com [128.221.11.32])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h3PMAuF23602
	for <ips@ece.cmu.edu>; Fri, 25 Apr 2003 18:10:56 -0400 (EDT)
Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <JN87J0WV>; Fri, 25 Apr 2003 18:10:36 -0400
Message-ID: <277DD60FB639D511AC0400B0D068B71E0564CB92@corpmx14.corp.emc.com>
From: Black_David@emc.com
To: eddy_quicksall@ivivity.com, ips@ece.cmu.edu
Subject: RE: use of ISID
Date: Fri, 25 Apr 2003 18:04:58 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

Back to Eddy's original message to add an important comment:

> Suppose you are one initiator going to only one target.
> Suppose you also want to login, do some I/O, logout, and
> later do the same.
>  
> Should the initiator use the same ISID for the two logins?

One situation in which this is crucial is when one expects
SCSI persistent reservations to behave consistently across the
logins. SCSI persistent reservations are associated with the
SCSI initiator port, so changing the ISID changes the port
and hence changes the behavior of the second session with
respect to any persistent reservations made by the first
session.

Thanks,
--David
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------