MSA Storage
1822149 Members
3937 Online
109640 Solutions
New Discussion

MSA 2052: Best practice on How to Implement Multipath and LVM on Red Hat High Availability Cluster

 
sungpillhan
Occasional Contributor

MSA 2052: Best practice on How to Implement Multipath and LVM on Red Hat High Availability Cluster

Hello friends, 

I'm new to HP Storage and am trying to see if MSA 2052 supports below configuration. I searched all documenations on MSA 2052, can't find any guide or best practice on how to configure and implement Red Hat HA Cluster with multipaths to MSA 2052. Am I not able to find the regarding documentations or simply...really it's not available in HPE support? 

configuration:

2 HP Gen9 DL360 Servers

4 Dual Port QLogic FC HBA cards

Red Hat Enterprise Linux 7 with High Availability (Active/Passive)

Oracle 11g

 

4 REPLIES 4

Re: MSA 2052: Best practice on How to Implement Multipath and LVM on Red Hat High Availability Clust

You need to check HPE SPOCK in order to check compatibility of your setup,

https://h20272.www2.hpe.com/spock2/Cont/ConfigsetView/index/113591

Also you can check this guide which will help you as well. It contains MSA204X details but you will get idea of MSA205X as well.

https://h20272.www2.hpe.com/spock/utility/document.aspx?docurl=Shared%20Documents/an/solutions_linux/Device_Mapper_Multipath_RG.pdf

From Red Hat side check below link,

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/dm_multipath/mpio_setup

MSA Best practice guide,

https://h20195.www2.hpe.com/v2/getpdf.aspx/A00015961ENW.pdf?

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

*********************************************************************



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
sungpillhan
Occasional Contributor

Re: MSA 2052: Best practice on How to Implement Multipath and LVM on Red Hat High Availability Clust

Thank you for the links to device mapper config guid.e 

Since there's no official doc to configure /etc/multipath.conf for MSA 2052. Is below looking good? I just replaced product name from MSA 2040 SAS to MSA 2052 SAS. But the disks are not SAS, but SSD. 

 

device {
vendor "HP"
product "MSA 2052 SAS"
path_grouping_policy group_by_prio
getuid_callout "/sbin/scsi_id -g -u -n -s /block/%n"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
path_selector "round-robin 0"
path_checker tur
hardware_handler "0"
failback immediate
rr_weight uniform
rr_min_io 100
no_path_retry 18
}

Re: MSA 2052: Best practice on How to Implement Multipath and LVM on Red Hat High Availability Clust

@sungpillhan ....please note multi-path configuration is no more depend on vendor. After red hat 5.5 it's native multipathing so configuration will be customer specific and vendor will not have any control in that.

inside multipathd.conf file "product" is nothing but to identify the MSA product that you are using where this config file will be applicable. It doesn't really matter if you mention or not. Now coming to what to mention if you really want to mention as best practice, you can mention as per your product model which can be either MSA2052 SAN or MSA2052 SAS. It doesn't really matter what kind of drives you are using.

some examples I have seen as below and one of them product details not mention as well,

defaults {
user_friendly_names               yes
polling_interval                        10
path_selector                           "round-robin 0"
path_grouping_policy             group_by_prio
prio                                          alua
path_checker                          tur
rr_min_io_rq                            100
flush_on_last_del                    no
max_fds                                  "max"
rr_weight                                uniform
failback                                   immediate
no_path_retry                        18
queue_without_daemon       no
}

device {
vendor                                  "HP"
product                                "MSA 2050"
path_grouping_policy          group_by_prio
uid_attribute                        "ID_SERIAL"
prio                                        alua
path_selector                       "round-robin 0"
path_checker                        tur
hardware_handler                "0"
failback                                  immediate
rr_weight                               uniform
rr_min_io_rq                          1
no_path_retry                       18
}

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

*********************************************************************



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo

Re: MSA 2052: Best practice on How to Implement Multipath and LVM on Red Hat High Availability Clust

Do you have any update or outstanding query?

Request you to please update on the forum so that everyone can get the update who are all following.

If you have no further query and you are satisfied with answers then kindly mark the forum as resolved.


Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

*************************************************************************

 

 



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo