| Message ID | 20230531135713.13914-1-xose.vazquez@gmail.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Delegated to: | christophe varoqui |
| Headers | show |
| Series | multipath-tools: adapt HITACHI/OPEN- config to work with alua and multibus | expand |
On Wed, 2023-05-31 at 15:57 +0200, Xose Vazquez Perez wrote: > ALUA is needed by Hitachi Global-Active Device (GAD): > https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/8.1/Global-Active_Device/Overview_of_global-active_device Thanks, but where exactly did you find this information in the linked document? I don't see ALUA mentioned. Unfortunately Hitachi chose to use non-standard terminology... Is ALUA always active / supported in these arrays? Regards Martin PS: Btw, this sort of enhancement is likely soon obsoleted by the autodetection feature that Ben's latest series would add. > > Cc: Matthias Rudolph <Matthias.Rudolph@hitachivantara.com> > Cc: Martin Wilck <mwilck@suse.com> > Cc: Benjamin Marzinski <bmarzins@redhat.com> > Cc: Christophe Varoqui <christophe.varoqui@opensvc.com> > Cc: DM-DEVEL ML <dm-devel@redhat.com> > Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com> > --- > libmultipath/hwtable.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c > index 65bca744..a858ffa9 100644 > --- a/libmultipath/hwtable.c > +++ b/libmultipath/hwtable.c > @@ -485,7 +485,9 @@ static struct hwentry default_hw[] = { > /* USP-V, HUS VM, VSP, VSP G1X00 and VSP GX00 > families / HPE XP */ > .vendor = "(HITACHI|HP|HPE)", > .product = "^OPEN-", > - .pgpolicy = MULTIBUS, > + .pgpolicy = GROUP_BY_PRIO, > + .pgfailback = -FAILBACK_IMMEDIATE, > + .no_path_retry = 10, > }, > { > /* AMS other than AMS 2000 */ -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
On 5/31/23 17:49, Martin Wilck wrote: > On Wed, 2023-05-31 at 15:57 +0200, Xose Vazquez Perez wrote: >> ALUA is needed by Hitachi Global-Active Device (GAD): >> https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/8.1/Global-Active_Device/Overview_of_global-active_device > Thanks, but where exactly did you find this information in the linked > document? I don't see ALUA mentioned. Unfortunately Hitachi chose to > use non-standard terminology... No public info, personal e-mail from Matthias: "We have also a config for ALUA. It is used for hardware copy between two arrays and the server should only use the local paths: SLES 12 SP2 ALUA: device { vendor "HITACHI" product "OPEN-.*" features "0" path_grouping_policy group_by_prio prio alua path_selector "round-robin 0" rr_weight uniform no_path_retry 1 rr_min_io 100 path_checker directio failback immediate } " > Is ALUA always active / supported in these arrays? Disable by default. And it is only needed with GAD setup: Array settings: "ALUA Mode" Enabled "Path Mode" ALUA "ALUA Permitted" YES "ALUA Settable" YES "Target Port Asymmetric Access State" Active/Optimized Same case as HUAWEI https://github.com/opensvc/multipath-tools/commit/9283fa6663ad908fd0419edcef4795fbbbe9f09d "no_path_retry 10" comes from: https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/9.8.6/Volume_Management_-_VSP_5000_Series/Host_Attachment/05_Red_Hat_Linux_configuration_and_attachment#Device_Mapper_(DM)_Multipath_configuration.0D.0A____for_Red_Hat_Linux -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
On Wed, 2023-05-31 at 15:57 +0200, Xose Vazquez Perez wrote: > ALUA is needed by Hitachi Global-Active Device (GAD): > https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/8.1/Global-Active_Device/Overview_of_global-active_device > > Cc: Matthias Rudolph <Matthias.Rudolph@hitachivantara.com> > Cc: Martin Wilck <mwilck@suse.com> > Cc: Benjamin Marzinski <bmarzins@redhat.com> > Cc: Christophe Varoqui <christophe.varoqui@opensvc.com> > Cc: DM-DEVEL ML <dm-devel@redhat.com> > Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com> > --- > libmultipath/hwtable.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c > index 65bca744..a858ffa9 100644 > --- a/libmultipath/hwtable.c > +++ b/libmultipath/hwtable.c > @@ -485,7 +485,9 @@ static struct hwentry default_hw[] = { > /* USP-V, HUS VM, VSP, VSP G1X00 and VSP GX00 > families / HPE XP */ > .vendor = "(HITACHI|HP|HPE)", > .product = "^OPEN-", > - .pgpolicy = MULTIBUS, > + .pgpolicy = GROUP_BY_PRIO, > + .pgfailback = -FAILBACK_IMMEDIATE, > + .no_path_retry = 10, > }, > { > /* AMS other than AMS 2000 */ Reviewed-by: Martin Wilck <mwilck@suse.com> -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
On Sat, 2023-06-03 at 13:12 +0200, Xose Vazquez Perez wrote: > On 5/31/23 17:49, Martin Wilck wrote: > > > On Wed, 2023-05-31 at 15:57 +0200, Xose Vazquez Perez wrote: > > > ALUA is needed by Hitachi Global-Active Device (GAD): > > > https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/8.1/Global-Active_Device/Overview_of_global-active_device > > > Thanks, but where exactly did you find this information in the > > linked > > document? I don't see ALUA mentioned. Unfortunately Hitachi chose > > to > > use non-standard terminology... > > No public info, personal e-mail from Matthias: > > "We have also a config for ALUA. It is used for hardware copy between > two > arrays and the server should only use the local paths: > > SLES 12 SP2 ALUA: > > device { > vendor "HITACHI" > product "OPEN-.*" > features "0" > path_grouping_policy group_by_prio > prio alua > path_selector "round-robin 0" > rr_weight uniform > no_path_retry 1 > rr_min_io 100 > path_checker directio > failback immediate > } > " > > > Is ALUA always active / supported in these arrays? > > Disable by default. And it is only needed with GAD setup: > > Array settings: > "ALUA Mode" Enabled > "Path Mode" ALUA > "ALUA Permitted" YES > "ALUA Settable" YES > "Target Port Asymmetric Access State" Active/Optimized > > Same case as HUAWEI > https://github.com/opensvc/multipath-tools/commit/9283fa6663ad908fd0419edcef4795fbbbe9f09d > > "no_path_retry 10" comes from: > https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/9.8.6/Volume_Management_-_VSP_5000_Series/Host_Attachment/05_Red_Hat_Linux_configuration_and_attachment#Device_Mapper_(DM)_Multipath_configuration.0D.0A____for_Red_Hat_Linux Thanks a lot. I'll apply your patch, adding part of this information to the commit message. Martin -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c index 65bca744..a858ffa9 100644 --- a/libmultipath/hwtable.c +++ b/libmultipath/hwtable.c @@ -485,7 +485,9 @@ static struct hwentry default_hw[] = { /* USP-V, HUS VM, VSP, VSP G1X00 and VSP GX00 families / HPE XP */ .vendor = "(HITACHI|HP|HPE)", .product = "^OPEN-", - .pgpolicy = MULTIBUS, + .pgpolicy = GROUP_BY_PRIO, + .pgfailback = -FAILBACK_IMMEDIATE, + .no_path_retry = 10, }, { /* AMS other than AMS 2000 */
ALUA is needed by Hitachi Global-Active Device (GAD): https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/8.1/Global-Active_Device/Overview_of_global-active_device Cc: Matthias Rudolph <Matthias.Rudolph@hitachivantara.com> Cc: Martin Wilck <mwilck@suse.com> Cc: Benjamin Marzinski <bmarzins@redhat.com> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com> Cc: DM-DEVEL ML <dm-devel@redhat.com> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com> --- libmultipath/hwtable.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)