From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 5 13:03:28 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D367916A419 for ; Fri, 5 Oct 2007 13:03:28 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com [72.36.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id 9C18D13C465 for ; Fri, 5 Oct 2007 13:03:28 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from proton.storspeed.com (209-163-168-124.static.twtelecom.net [209.163.168.124]) (authenticated bits=0) by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id l95D3ROe055236; Fri, 5 Oct 2007 08:03:28 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <4706361D.9030505@freebsd.org> Date: Fri, 05 Oct 2007 08:03:25 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Sharad Chandra References: <200710041725.00842.sharadc@in.niksun.com> <200710051646.17618.sharadc@in.niksun.com> <4706261B.1050202@freebsd.org> <200710051828.08343.sharadc@in.niksun.com> In-Reply-To: <200710051828.08343.sharadc@in.niksun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com Cc: freebsd-hackers@freebsd.org Subject: Re: SCSI and SAN X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2007 13:03:28 -0000 Sharad Chandra wrote: > On Friday 05 October 2007 5:25 pm, Eric Anderson wrote: >> Sharad Chandra wrote: >> > On Thursday 04 October 2007 6:51 pm, Eric Anderson wrote: >> >> Sharad Chandra wrote: >> >>> Hello, >> >>> >> >>> How to distinguish if /dev/da* devices are internal scsi drivers >> >> or LUNs >> >> >>> of external SAN? >> >> >> >> camcontrol devlist -v >> >> >> >> Might help you.. >> >> >> >> Eric >>> Yes, right by analyzing camcontrol devlist it can be told, but i guess >>> not always. >>> >>> [root@qa7 ~]# camcontrol devlist >>> at scbus0 target 0 lun 0 (da0,pass0) >>> at scbus0 target 0 lun 1 (da1,pass1) >>> at scbus0 target 0 lun 2 (da2,pass2) >>> at scbus0 target 0 lun 3 (da3,pass3) >>> >>> Here luns are increasing, so it is SAN confirmed by tool. Now my point is >>> if i have a SAN of less than 1TB and i make only 1 LUN. what should be >>> output? guessing: similar to >>> at scbus0 target 0 lun 0 (da0,pass0) >>> >>> Then it will be difficult to tell, whether it is regular SCSI drives or >>> SAN. Then we need a tool that can tell this da0 belongs to SAN/SCSI or >>> not >> Notice the -v to camcontrol. It will tell you which controller the >> device belongs to, and the controller will help you determine whether it >> is connected to a SAN or not. > > [root@qa7 ~]# camcontrol devlist -v > scbus0 on isp0 bus 0: > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 0 lun 1 (da1,pass1) > at scbus0 target 0 lun 2 (da2,pass2) > at scbus0 target 0 lun 3 (da3,pass3) > < > at scbus0 target -1 lun -1 () > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > > Does it? Well, isp0 is a QLogic fiber channel card, so that's as much as you will ever know. You could possibly use camcontrol to show WWN's (world wide names) which are present on fiber channel, but I don't think they are on other SCSI devices (oh boy, someone correct me if that is wrong - Scott Long, are you listening?). Eric