From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 22 15:32:49 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91A9B16A4CE for ; Tue, 22 Feb 2005 15:32:49 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2307043D48 for ; Tue, 22 Feb 2005 15:32:49 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1D3c1n-0003af-O4; Tue, 22 Feb 2005 17:32:47 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Scott In-reply-to: Your message of Mon, 21 Feb 2005 08:50:32 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Feb 2005 17:32:47 +0200 From: Danny Braniss Message-ID: cc: scsi@freebsd.org Subject: Re: and now it's walking! Re: iSCSI first steps! X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2005 15:32:49 -0000 so now it's a maraton? scbus3 is the iscsi: shuttle-2# camcontrol devlist at scbus2 target 0 lun 0 (cd0,pass0) at scbus3 target 0 lun 0 (pass1,da0) < > at scbus3 target 0 lun 1 (pass2) < > at scbus3 target 0 lun 2 (pass3) < > at scbus3 target 0 lun 3 (pass4) at scbus3 target 1 lun 0 (pass5,da1) at scbus3 target 2 lun 0 (pass6,da2) at scbus3 target 2 lun 1 (pass7,da3) at scbus3 target 2 lun 2 (pass8,da4) at scbus3 target 2 lun 3 (pass9,da5) and shuttle-2# ls -ls /dev/da* 0 crw-r----- 1 root operator 4, 25 Feb 22 16:30 /dev/da0 0 crw-r----- 1 root operator 4, 26 Feb 22 16:30 /dev/da1 0 crw-r----- 1 root operator 4, 27 Feb 22 16:30 /dev/da2 0 crw-r----- 1 root operator 4, 28 Feb 22 16:30 /dev/da3 0 crw-r----- 1 root operator 4, 29 Feb 22 16:30 /dev/da4 0 crw-r----- 1 root operator 4, 30 Feb 22 16:30 /dev/da5 so here is my question/dilema: from the 'camcontrol devlist' one can find out some info as to the target, but not the targetaddress/targetname, which were used to stablish the connection. this info is passed to the iscsi driver, but it has no idea at to what kind of devices are being attached - it can be a disk/tape/scanner/etc. in short, the CAM has no idea about targetname/targetaddress, the iscsi driver has no idea as to targets. Any ideas? danny