From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Supporto for EVA3000?
Date: Thu, 08 Nov 2007 08:22:58 +0100 [thread overview]
Message-ID: <4732B952.2030500@suse.de> (raw)
In-Reply-To: <20071107180321.GE28113@ether.msp.redhat.com>
Benjamin Marzinski wrote:
> On Tue, Nov 06, 2007 at 12:08:59PM +0100, Domenico Viggiani wrote:
>> Good morning,
>> does anyone know if the old HP EVA3000 (HSV100) disk-array is supported with
>> dm-multipath shipped with Red Hat 4?
>
> If the product name comes up as HSV100, then this version of the
> firmware needs the storageworks hardware handler module to function optimally.
> This is not available on the RHEL4 kernel. I have never actually used
> one of these disk-arrays, but I believe that there is a firmware update for the
> EVA3000 that solves this problem. You should see the product name change to
> HSV110, and the device will be properly autoconfigured in RHEL4.
>
> If for some reason you cannot update the firmware, I believe that you
> can still use multipath with the device at a performance penalty. I
> don't recall the best configuration for that scenario off the top of my
> head.
>
No, you can't. The ominous 'Storageworks handler' Ben referred to is
actually the hp_sw hardware handler available in later versions.
This firmware requires a 'START STOP UNIT' command to be send to the
inactive path; the firmware will then activate it (and deactivate the
old path).
Hence you're pretty much stuck without it.
So a firmware update would be your best option here.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
prev parent reply other threads:[~2007-11-08 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 11:08 Supporto for EVA3000? Domenico Viggiani
2007-11-07 18:03 ` Benjamin Marzinski
2007-11-08 7:22 ` Hannes Reinecke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4732B952.2030500@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.