From owner-freebsd-hardware Tue Jul 13 23: 5: 0 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id C781214DFC for ; Tue, 13 Jul 1999 23:04:47 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id BAA12296; Wed, 14 Jul 1999 01:04:40 -0500 (CDT) Date: Wed, 14 Jul 1999 01:04:40 -0500 From: Tim Tsai To: Matthew Jacob Cc: hardware@FreeBSD.ORG Subject: Re: Fibre Channel Controller [ LONG RESPONSE ] Message-ID: <19990714010440.A11885@futuresouth.com> References: <19990714003006.A10871@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Matthew Jacob on Tue, Jul 13, 1999 at 10:48:27PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The switch configuration *can* work (it's early days for the code I put > in), but all that really does is join together multiple loops such that if > I query the Fabric name server and get list of disks back, I can 'map' > them to loop ID's such that the Qlogic knows they're not on the local > loop. This picture looks like, e.g.: Actually I mentioned the switch because as far as I know you can configure it in such a way that the host will never see disks that it's not intended for. That should isolate the hosts from each other even if FC id's go in and out? It is analogous to VLAN on ethernet. We will probably look into that again soon. We need [HW] RAID on a handful of machines and I would rather spend the money on a couple of good storage arrays instead of buying one for each machine. NFS is out for our environment. Would you happen to have a host-independent (stand-alone) FC RAID controller that you can recommend? Thanks! Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message