Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 05 Oct 2007 08:03:25 -0500
From:      Eric Anderson <anderson@freebsd.org>
To:        Sharad Chandra <sharadc@in.niksun.com>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: SCSI and SAN
Message-ID:  <4706361D.9030505@freebsd.org>
In-Reply-To: <200710051828.08343.sharadc@in.niksun.com>
References:  <200710041725.00842.sharadc@in.niksun.com> <200710051646.17618.sharadc@in.niksun.com> <4706261B.1050202@freebsd.org> <200710051828.08343.sharadc@in.niksun.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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
>>> <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?

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





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4706361D.9030505>