Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi I have redhat 7.5 with HP3par connected to it.
It detects all drives ok, and it looks like it detects all paths ok as well. Problem is it is sending data only through one path not through all available ( 4 of them for each of drives) . I have configured it according to HPE recomendations but still nothing works as intended.
# This is a basic configuration file with some examples, for device mapper
# multipath.
#
# For a complete list of the default configuration values, run either
# multipath -t
# or
# multipathd show config
#
# For a list of configuration options with descriptions, see the multipath.conf
# man page
## By default, devices with vendor = "IBM" and product = "S/390.*" are
## blacklisted. To enable mulitpathing on these devies, uncomment the
## following lines.
blacklist_exceptions {
devnode "^(dm-)[0-9]*"
wwid "360002ac000000000000000250001aa9c"
wwid "360002ac000000000000000240001aa9c"
wwid "360002ac000000000000000230001aa9c"
wwid "360002ac000000000000000270001aa9c"
wwid "360002ac000000000000000260001aa9c"
wwid "360002ac0000000000000002800021340"
wwid "360002ac0000000000000002900021340"
wwid "360002ac0000000000000003300021340"
wwid "360002ac0000000000000003400021340"
wwid "360002ac0000000000000002a00021340"
"/etc/multipath.conf" 140L, 3682C
device {
vendor "3PARdata"
product "VV"
}
# device {
# vendor "IBM"
# product "S/390.*"
# }
}
## Use user friendly names, instead of using WWIDs as names.
#defaults {
# polling_interval 10
# user_friendly_names yes
# find_multipaths yes
# path_selector "round-robin 0"
#}
##
## Here is an example of how to configure some standard options.
##
#
defaults {
polling_interval 10
# path_selector "round-robin 0"
# path_grouping_policy group_by_prio
# uid_attribute ID_SERIAL
# prio alua
# path_checker readsector0
# rr_min_io 100
# max_fds 8192
# rr_weight priorities
# failback immediate
# no_path_retry fail
user_friendly_names yes
}
##
## The wwid line in the following blacklist section is shown as an example
## of how to blacklist devices by wwid. The 2 devnode lines are the
## compiled in default blacklist. If you want to blacklist entire types
## of devices, such as all scsi devices, you should use a devnode line.
## However, if you want to blacklist specific devices, you should use
## a wwid line. Since there is no guarantee that a specific device will
## not change names on reboot (from /dev/sda to /dev/sdb for example)
## devnode lines are not recommended for blacklisting specific devices.
##
blacklist {
# wwid 26353900f02796769
# devnode "^(ram|raw|loop|fd|md|sr|scd|st)[0-9]*"
# devnode "^hd[a-z]"
}
#multipaths {
# multipath {
# wwid 3600508b4000156d700012000000b0000
# alias yellow
# path_grouping_policy multibus
# path_selector "round-robin 0"
# failback manual
# rr_weight priorities
# no_path_retry 5
# }
# multipath {
# wwid 1DEC_____321816758474
# alias red
# }
#}
devices {
device {
vendor "3PARdata"
product "VV"
path_grouping_policy "group_by_prio"
path_selector "round-robin 0"
path_checker "tur"
features "0"
hardware_handler "1 alua"
prio "alua"
failback immediate
rr_weight "uniform"
no_path_retry 18
fast_io_fail_tmo 10
dev_loss_tmo "infinity"
}
# device {
# vendor "COMPAQ "
# product "MSA1000 "
# path_grouping_policy multibus
# }
}
Thank you and apologies for formating ( already corrected).
Will try yoiur suggestion on multibus
As to monitoring we have ability to check only on 3par end. Since we have two 3par devices we know our config is ok. As well besides this linux server we have one vmware server connected to the same 3par . Vmaware uses trafic just for couple hours over night and then all ports are utilised . but when redhat is running all traffic goes just to one port. Problem is that now it starts reaching 100% utilisation and causes problems.
Really appreciate your help. tried multibus but that did not help.
I found hp documentation from 2016 on how to set it up , but i dont see problems on our side. Will ask support for newest config possible and then we will see. Next year we will get support for redhat, but for now i need to resolve that issue on my own...
Multipath will use the preferred by storage path according to ALUA protocol.
Usually only one storage head is a LUN owner then its paths are preferred, other paths less optimized for IO.
Also usually every storage head is connected by redundant paths to SAN, then you should see at least two paths equally used.
Please check your FC zones settings to achieve full mesh redundant schema.
ALUA is the best option, but you can use round-robin option if you insist.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
