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 h0LM7TW12619
	for ips-outgoing; Tue, 21 Jan 2003 17:07:29 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from mail.ivivity.com ([64.238.111.99])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0LM7RW12615
	for <ips@ece.cmu.edu>; Tue, 21 Jan 2003 17:07:27 -0500 (EST)
Received: by ATLOPS with Internet Mail Service (5.5.2653.19)
	id <Y12VHWW9>; Tue, 21 Jan 2003 17:07:26 -0500
Message-ID: <AEC4671C8179D61194DE0002B328BDD20BCF@ATLOPS>
From: Eddy Quicksall <eddy_quicksall@ivivity.com>
To: ips@ece.cmu.edu
Subject: iSCSI: LUN in a ping
Date: Tue, 21 Jan 2003 17:07:20 -0500
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

Does anyone know why we added "the LUN must be valid" for a target initiated
ping? It would seem that it is N/A when the ping is just being used to
checkup on the connection.
 
What will the initiator do with the LUN anyway?
 
10.19.3 LUN
A LUN MUST be set to a correct value when the Target Transfer Tag is
valid (not the reserved value 0xffffffff).
 
Eddy
mailto: Eddy_Quicksall@iVivity.com