Linux Device Mapper development
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] multipath-tools: add README.alua with instructions to enable ALUA
Date: Tue, 21 Nov 2017 19:50:20 +0100	[thread overview]
Message-ID: <91541216-2c8f-9c50-e645-391442912e24@gmail.com> (raw)
In-Reply-To: <20171120185315.3026-1-xose.vazquez@gmail.com>

On 11/20/2017 07:53 PM, Xose Vazquez Perez wrote:
> ALUA is supported in some storage devices, but usually it's disabled by default.

Christophe, please drop this one. v2 is on the way.

> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
> Cc: device-mapper development <dm-devel@redhat.com>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> ---
>  README.alua | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>  create mode 100644 README.alua
> 
> diff --git a/README.alua b/README.alua
> new file mode 100644
> index 0000000..134696a
> --- /dev/null
> +++ b/README.alua
> @@ -0,0 +1,14 @@
> +This is a rough guide, consult your storage device manufacturer documentation.
> +
> +ALUA is supported in some devices, but usually it's disabled by default.
> +To enable ALUA, the following options should be changed:
> +
> +- EMC CLARiiON/VNX:
> +   "Failover Mode" should be changed to "4".
> +
> +- HPE 3PAR:
> +   "Host:" should be changed to "Generic-ALUA Persona 2 (UARepLun, SESLun, ALUA)".
> +
> +- Promise VTrak/Vess:
> +   "LUN Affinity" and "ALUA" should be changed to "Enable", "Redundancy Type"
> +   must be "Active-Active".
> 

      reply	other threads:[~2017-11-21 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 18:53 [PATCH] multipath-tools: add README.alua with instructions to enable ALUA Xose Vazquez Perez
2017-11-21 18:50 ` Xose Vazquez Perez [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=91541216-2c8f-9c50-e645-391442912e24@gmail.com \
    --to=xose.vazquez@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox