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

[Xose Vazquez Perez <xose.vazquez@gmail.com>]

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.