Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id h3HJlHQ01498 for ips-outgoing; Thu, 17 Apr 2003 15:47:17 -0400 (EDT) X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f Received: from palrel10.hp.com (palrel10.hp.com [156.153.255.245]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h3HJlB301488 for ; Thu, 17 Apr 2003 15:47:11 -0400 (EDT) Received: from xparelay2.ptp.hp.com (xparelay2.ptp.hp.com [15.1.28.65]) by palrel10.hp.com (Postfix) with ESMTP id 2E50A1C01A80; Thu, 17 Apr 2003 12:47:06 -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 E9D461C00A8D; Thu, 17 Apr 2003 12:47:05 -0700 (PDT) Received: by xpabh2.ptp.hp.com with Internet Mail Service (5.5.2655.55) id <2VKR8SN4>; Thu, 17 Apr 2003 12:47:05 -0700 Message-ID: <6BD67FFB937FD411A04F00D0B74FE878102F6103@xrose06.rose.hp.com> From: "KRUEGER,MARJORIE (HP-Roseville,ex1)" To: "'Eddy Quicksall'" , ips@ece.cmu.edu Subject: RE: use of ISID Date: Thu, 17 Apr 2003 12:46:58 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3051A.1B3B1010" 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_01C3051A.1B3B1010 Content-Type: text/plain See the iSCSI protocol document, Section 9.1.1 Conservative Reuse of ISIDs. Since the ISID is a component of the SCSI Port Name, presenting the same "initiator port name" consistently is a good thing to do. And if the SCSI applications make use of certain SCSI commands (persistant reservations, access controls), it might be a necessary thing to do. Marjorie -----Original Message----- From: Eddy Quicksall [mailto:eddy_quicksall@ivivity.com] Sent: Thursday, April 17, 2003 12:31 PM To: ips@ece.cmu.edu Subject: use of ISID 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? Eddy EMAIL: Eddy_Quicksall@iVivity.com ------_=_NextPart_001_01C3051A.1B3B1010 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Message
See=20 the iSCSI protocol document,  Section = 9.1.1=20 Conservative Reuse of ISIDs.  Since the ISID is a component = of the=20 SCSI Port Name, presenting the same "initiator port name" consistently = is a good=20 thing to do.  And if the SCSI applications make use of certain = SCSI=20 commands (persistant reservations, access controls), it might be =  a=20 necessary thing to do.
 
Marjorie 
-----Original Message-----
From: = Eddy Quicksall=20 [mailto:eddy_quicksall@ivivity.com]
Sent: Thursday, April = 17, 2003=20 12:31 PM
To: ips@ece.cmu.edu
Subject: use of=20 ISID

Suppose you are one = initiator=20 going to only one target. Suppose you also want to login, do some = I/O, logout,=20 and later do the same.

 

Should the initiator = use the same=20 ISID for the two logins?

 

Eddy

 

EMAIL:=20 Eddy_Quicksall@iVivity.com

 

------_=_NextPart_001_01C3051A.1B3B1010--