[PATCH] libmultipath: update 3PARdata builtin config

[PATCH] libmultipath: update 3PARdata builtin config

[Benjamin Marzinski]

This updated config comes from hp.

Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
---
 libmultipath/hwtable.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
index 390d143..54bdcfc 100644
--- a/libmultipath/hwtable.c
+++ b/libmultipath/hwtable.c
@@ -49,6 +49,8 @@ static struct hwentry default_hw[] = {
 		.hwhandler     = "1 alua",
 		.prio_name     = PRIO_ALUA,
 		.no_path_retry = 18,
+		.fast_io_fail  = 10,
+		.dev_loss      = MAX_DEV_LOSS_TMO,
 	},
 	{
 		/* RA8000 / ESA12000 */
-- 
2.7.4

Re: [PATCH] libmultipath: update 3PARdata builtin config

[Xose Vazquez Perez]

On 06/26/2017 09:03 PM, Benjamin Marzinski wrote:

> This updated config comes from hp.

It would be nice to have more information.
Why and when is this needed?


BTW: HPE 'MSA 205x' and 'StoreVirtual 3200'(LeftHand) are missing.

> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
>  libmultipath/hwtable.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
> index 390d143..54bdcfc 100644
> --- a/libmultipath/hwtable.c
> +++ b/libmultipath/hwtable.c
> @@ -49,6 +49,8 @@ static struct hwentry default_hw[] = {
>  		.hwhandler     = "1 alua",
>  		.prio_name     = PRIO_ALUA,
>  		.no_path_retry = 18,
> +		.fast_io_fail  = 10,
> +		.dev_loss      = MAX_DEV_LOSS_TMO,
>  	},
>  	{
>  		/* RA8000 / ESA12000 */
>

Re: [PATCH] libmultipath: update 3PARdata builtin config

[Benjamin Marzinski]

On Wed, Jun 28, 2017 at 07:48:38PM +0200, Xose Vazquez Perez wrote:
> On 06/26/2017 09:03 PM, Benjamin Marzinski wrote:
> 
> > This updated config comes from hp.
> 
> It would be nice to have more information.
> Why and when is this needed?

I assume the change to dev_loss_tmo is simply a preference issue. Like
Netapp, they don't want their devices to get auto-removed when they go
down. I also assume that in their internal testing, they hit cases where
5 seconds wasn't enough time to wait for some transient issue with the
array to resolve.  At any rate, I'm simply passing along their request,
which seems like a perfectly reasonable one to me.

-Ben

> 
> 
> BTW: HPE 'MSA 205x' and 'StoreVirtual 3200'(LeftHand) are missing.
> 
> > Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> > ---
> >  libmultipath/hwtable.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
> > index 390d143..54bdcfc 100644
> > --- a/libmultipath/hwtable.c
> > +++ b/libmultipath/hwtable.c
> > @@ -49,6 +49,8 @@ static struct hwentry default_hw[] = {
> >  		.hwhandler     = "1 alua",
> >  		.prio_name     = PRIO_ALUA,
> >  		.no_path_retry = 18,
> > +		.fast_io_fail  = 10,
> > +		.dev_loss      = MAX_DEV_LOSS_TMO,
> >  	},
> >  	{
> >  		/* RA8000 / ESA12000 */
> >

Re: [PATCH] libmultipath: update 3PARdata builtin config

[Xose Vazquez Perez]

On 06/29/2017 04:57 PM, Benjamin Marzinski wrote:

>>> +		.fast_io_fail  = 10,
>>> +		.dev_loss      = MAX_DEV_LOSS_TMO,

> On Wed, Jun 28, 2017 at 07:48:38PM +0200, Xose Vazquez Perez wrote:
>
>> It would be nice to have more information.
>> Why and when is this needed?
> 
> I assume the change to dev_loss_tmo is simply a preference issue. Like
> Netapp, they don't want their devices to get auto-removed when they go
> down. I also assume that in their internal testing, they hit cases where
> 5 seconds wasn't enough time to wait for some transient issue with the
> array to resolve.  At any rate, I'm simply passing along their request,
> which seems like a perfectly reasonable one to me.

Those arguments should come from the vendor.

"dev_loss_tmo 14" is recommended(???) in latest 3PAR docs (Jun 2017):

- HPE 3PAR SUSE Linux Enterprise Implementation Guide (Wed 14 Jun 2017 11:48:14 PM CEST)
   http://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay/?docId=c02663748

- HPE 3PAR Red Hat Enterprise Linux and Oracle Linux Implementation Guide (Wed 14 Jun 2017 12:10:06 AM CEST)
   http://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay/?docId=c04448818

Re: [PATCH] libmultipath: update 3PARdata builtin config

[Benjamin Marzinski]

On Thu, Jul 13, 2017 at 08:25:30PM +0200, Xose Vazquez Perez wrote:
> On 06/29/2017 04:57 PM, Benjamin Marzinski wrote:
> 
> >>> +		.fast_io_fail  = 10,
> >>> +		.dev_loss      = MAX_DEV_LOSS_TMO,
> 
> > On Wed, Jun 28, 2017 at 07:48:38PM +0200, Xose Vazquez Perez wrote:
> >
> >> It would be nice to have more information.
> >> Why and when is this needed?
> > 
> > I assume the change to dev_loss_tmo is simply a preference issue. Like
> > Netapp, they don't want their devices to get auto-removed when they go
> > down. I also assume that in their internal testing, they hit cases where
> > 5 seconds wasn't enough time to wait for some transient issue with the
> > array to resolve.  At any rate, I'm simply passing along their request,
> > which seems like a perfectly reasonable one to me.
> 
> Those arguments should come from the vendor.
> 
> "dev_loss_tmo 14" is recommended(???) in latest 3PAR docs (Jun 2017):
> 
> - HPE 3PAR SUSE Linux Enterprise Implementation Guide (Wed 14 Jun 2017 11:48:14 PM CEST)
>    http://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay/?docId=c02663748
> 
> - HPE 3PAR Red Hat Enterprise Linux and Oracle Linux Implementation Guide (Wed 14 Jun 2017 12:10:06 AM CEST)
>    http://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay/?docId=c04448818

Here I what I got from HP:

********

We will be changing the recommendation in the next version of the 3PAR
Implementation Guide. I am the owner for these guides. 

The reason we want the  dev_loss_tmo "infinity"  is to help in a feature
called Peer Persistence where on primary array power fails and the
device on the remote array (standby array) becomes active. The standby
state of the device paths will automatically change to active state if
the underlying device instances exist so we need infinity setting.

The fast_io_fail_tmo we want to be bumped from 5 to 10 so that it allows
a array feature called persistent port to work well where we want the
want the array path going away failure transient state to be held for
the longer time in the SCSI and FC OS layers (I/O retry) without
multipath reacting to it which allows the array to move the physical
port flogi instance on the switch to move to partner physical port as an
NPIV Port when the array node goes down.  Complete details in this PDF  

https://www.hpe.com/h20195/v2/GetPDF.aspx/4AA4-4545ENW.pdf

*******

-Ben

Re: [PATCH] libmultipath: update 3PARdata builtin config

[Xose Vazquez Perez]

On 07/29/2017 12:37 AM, Benjamin Marzinski wrote:

> Here I what I got from HP:
> 
> We will be changing the recommendation in the next version of the 3PAR
> Implementation Guide. I am the owner for these guides. 
> 
> The reason we want the  dev_loss_tmo "infinity"  is to help in a feature
> called Peer Persistence where on primary array power fails and the
> device on the remote array (standby array) becomes active. The standby
> state of the device paths will automatically change to active state if
> the underlying device instances exist so we need infinity setting.
> 
> The fast_io_fail_tmo we want to be bumped from 5 to 10 so that it allows
> a array feature called persistent port to work well where we want the
> want the array path going away failure transient state to be held for
> the longer time in the SCSI and FC OS layers (I/O retry) without
> multipath reacting to it which allows the array to move the physical
> port flogi instance on the switch to move to partner physical port as an
> NPIV Port when the array node goes down.  Complete details in this PDF  
> 
> https://www.hpe.com/h20195/v2/GetPDF.aspx/4AA4-4545ENW.pdf

Fine, I will send a v2 PATCH with that text. Christophe, drop this one.

Re: [PATCH] libmultipath: update 3PARdata builtin config

[Christophe Varoqui]

[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]

Merged,
Thanks.

(And version bumped to 0.7.2)

On Mon, Jun 26, 2017 at 9:03 PM, Benjamin Marzinski <bmarzins@redhat.com>
wrote:

> This updated config comes from hp.
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
>  libmultipath/hwtable.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
> index 390d143..54bdcfc 100644
> --- a/libmultipath/hwtable.c
> +++ b/libmultipath/hwtable.c
> @@ -49,6 +49,8 @@ static struct hwentry default_hw[] = {
>                 .hwhandler     = "1 alua",
>                 .prio_name     = PRIO_ALUA,
>                 .no_path_retry = 18,
> +               .fast_io_fail  = 10,
> +               .dev_loss      = MAX_DEV_LOSS_TMO,
>         },
>         {
>                 /* RA8000 / ESA12000 */
> --
> 2.7.4
>
>

[-- Attachment #1.2: Type: text/html, Size: 1405 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: [PATCH] libmultipath: update 3PARdata builtin config

[Xose Vazquez Perez]

Christophe Varoqui wrote:

> (And version bumped to 0.7.2)

untagged: https://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=tags

Re: [PATCH] libmultipath: update 3PARdata builtin config

[Christophe Varoqui]

[-- Attachment #1.1: Type: text/plain, Size: 240 bytes --]

And done.

On Sat, Aug 5, 2017 at 1:23 PM, Xose Vazquez Perez <xose.vazquez@gmail.com>
wrote:

> Christophe Varoqui wrote:
>
> > (And version bumped to 0.7.2)
>
> untagged: https://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=tags
>

[-- Attachment #1.2: Type: text/html, Size: 699 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]