From owner-freebsd-hackers@FreeBSD.ORG  Fri Oct  5 13:01:18 2007
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 BA46F16A417;
	Fri,  5 Oct 2007 13:01:18 +0000 (UTC)
	(envelope-from sharadc@in.niksun.com)
Received: from in.niksun.com (210.18.76.166.sify.net [210.18.76.166])
	by mx1.freebsd.org (Postfix) with ESMTP id 5278E13C48E;
	Fri,  5 Oct 2007 13:01:18 +0000 (UTC)
	(envelope-from sharadc@in.niksun.com)
Received: from sharadc.in.niksun.com (unknown [10.60.5.27])
	by in.niksun.com (Postfix) with ESMTP id 6A7795CC0;
	Fri,  5 Oct 2007 18:39:20 +0530 (IST)
From: Sharad Chandra <sharadc@in.niksun.com>
Organization: NIKSUN
To: Eric Anderson <anderson@freebsd.org>
Date: Fri, 5 Oct 2007 18:28:08 +0530
User-Agent: KMail/1.9.4
References: <200710041725.00842.sharadc@in.niksun.com>
	<200710051646.17618.sharadc@in.niksun.com>
	<4706261B.1050202@freebsd.org>
In-Reply-To: <4706261B.1050202@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200710051828.08343.sharadc@in.niksun.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
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2007 13:01:18 -0000

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
> > <IFT A16F-G2422 348C>              at scbus0 target 0 lun 0 (da0,pass0)
> > <IFT A16F-G2422 348C>              at scbus0 target 0 lun 1 (da1,pass1)
> > <IFT A16F-G2422 348C>              at scbus0 target 0 lun 2 (da2,pass2)
> > <IFT A16F-G2422 348C>              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
> > <IFT A16F-G2422 348C>              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:
<IFT A16F-G2422 348C>              at scbus0 target 0 lun 0 (da0,pass0)
<IFT A16F-G2422 348C>              at scbus0 target 0 lun 1 (da1,pass1)
<IFT A16F-G2422 348C>              at scbus0 target 0 lun 2 (da2,pass2)
<IFT A16F-G2422 348C>              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?

>
> Other than that, I'm not sure of the distinction that could be made
> between the devices whether it is on a SAN or not.  It could be a
> directly connected fiber channel device, in which case, it isn't quite a
> SAN, yet the FreeBSD system doesn't know (or care) how it's connected.
>
> Eric