Prev: Connect Solaris8 to Internet?
Next: problems installing hp laserjet 1320nw
From: dawe on 28 Apr 2010 10:06
Hi all, I have a tricky question about the driver support for HP MSA
devices.
It happens that we have a FreeBSD 8 machine on a HP DL 380 G5,
connected to a MSA 70. This array has 25 disks. The array has been
configured to present all the disks to the OS so that zfs could manage
them individually (and also adding 4 additional disks from the DL 380
itself).
To allow this we had to modify the driver in order to support more
than 16 disks per controller (this is a simple #define in the ciss
module).
This said, we wanted to migrate to OpenSolaris (or Nexenta 3) to use
zfs deduplication capabilities, possibly by installing the OS and
upgrading the zfs version to avoid any data loss (i.e. we don't want
to recreate pools and fs from scratch).
Unfortunately I don't know if the 16 disks limit is valid for HP
drivers (and I can't find any info on HP website) and, if yes, how to
override it.

Thanks

d
From: John D Groenveld on 28 Apr 2010 10:43
In article <9a0aa1b9-cb13-4678-ba0d-aefcdf6e3e96(a)g11g2000yqe.googlegroups.com>,
dawe <daweonline(a)gmail.com> wrote:
>It happens that we have a FreeBSD 8 machine on a HP DL 380 G5,
>connected to a MSA 70. This array has 25 disks. The array has been

HPQ's search engine points me towards the CPQary3 driver.
Is that the correct driver for your HBA?

>configured to present all the disks to the OS so that zfs could manage
>them individually (and also adding 4 additional disks from the DL 380
>itself).

Good practice.

>Unfortunately I don't know if the 16 disks limit is valid for HP
>drivers (and I can't find any info on HP website) and, if yes, how to
>override it.

From cpqary3(7D)
The target driver's configuration file shall need entries if
support is needed for targets numbering greater than the
default number of targets supported by the corresponding
target driver.

By default, entries for SCSI target numbers 0 to 15 are
present in sd.conf. Entries for target numbers 16 and above
shall be added in SCSI class in the sd.conf file for sup-
porting corresponding logical volumes.

Download the latest Solaris 10 and configure the boot image from
installation media per HPQ's README and James C Liu and Brian
Downy's Howto:
<URL:http://www.sun.com/bigadmin/features/articles/device_driver_install.html>

Adjust the sd.conf on the boot image.

Boot single-user.

Run format(1M) and confirm that all 25 disks are present.

John
groenveld(a)acm.org
From: dawe on 28 Apr 2010 11:13
On Apr 28, 4:43 pm, groen...(a)cse.psu.edu (John D Groenveld) wrote:

> HPQ's search engine points me towards the CPQary3 driver.
> Is that the correct driver for your HBA?

I think so

>
> >configured to present all the disks to the OS so that zfs could manage
> >them individually (and also adding 4 additional disks from the DL 380
> >itself).
>
> Good practice.
>

:-) Thanks!

> Download the latest Solaris 10 and configure the boot image from
> installation media per HPQ's README and James C Liu and Brian
> Downy's Howto:
> <URL:http://www.sun.com/bigadmin/features/articles/device_driver_install.html>
>
> Adjust the sd.conf on the boot image.
>
> Boot single-user.
>
> Run format(1M) and confirm that all 25 disks are present.

Thanks John, I'll try this ASAP. Do you think it will be valid also
for Nexenta 3? I may need it because of the GNU userland...

Thanks again

d
From: John D Groenveld on 28 Apr 2010 13:25
In article <fd876955-0b3f-46cf-ba7f-73964b4d6ee7(a)v14g2000yqb.googlegroups.com>,
dawe <daweonline(a)gmail.com> wrote:
>Thanks John, I'll try this ASAP. Do you think it will be valid also
>for Nexenta 3? I may need it because of the GNU userland...

I don't know about the current state of network booting and
the addition of third party drivers in Indiana nor Nexenta.

I know there's ongoing work on enterprise installation.
I recently used the text installation build of Indiana b134.

I advise you start with Solaris 10 and prove HPQ's drivers
will work since that's what HPQ supports, then once you've
crossed that milestone, move on to OpenSolaris and join
the Caiman project.
<URL:http://hub.opensolaris.org/bin/view/Project+caiman/>

Happy hacking,
John
groenveld(a)acm.org
From: Chris Ridd on 28 Apr 2010 13:34
On 2010-04-28 18:25:35 +0100, John D Groenveld said:

> In article <fd876955-0b3f-46cf-ba7f-73964b4d6ee7(a)v14g2000yqb.googlegroups.com>,
> dawe <daweonline(a)gmail.com> wrote:
>> Thanks John, I'll try this ASAP. Do you think it will be valid also
>> for Nexenta 3? I may need it because of the GNU userland...
>
> I don't know about the current state of network booting and
> the addition of third party drivers in Indiana nor Nexenta.
>
> I know there's ongoing work on enterprise installation.
> I recently used the text installation build of Indiana b134.
>
> I advise you start with Solaris 10 and prove HPQ's drivers
> will work since that's what HPQ supports, then once you've
> crossed that milestone, move on to OpenSolaris and join
> the Caiman project.
> <URL:http://hub.opensolaris.org/bin/view/Project+caiman/>

OTOH I think HP SmartArray HBA drivers were recently added to
OpenSolaris. Ah yes:

<http://hg.genunix.org/onnv-gate.hg/rev/6966deaa0775>

pkg:/driver/storage/cpqary3

--
Chris

 |  Next  |  Last
Pages: 1 2
Prev: Connect Solaris8 to Internet?
Next: problems installing hp laserjet 1320nw