HPE EVA Storage
1748081 Members
5328 Online
108758 Solutions
New Discussion юеВ

Re: Trying to get multipath working with BL460c & MSA2324sa

 
BradV
Esteemed Contributor

Re: Trying to get multipath working with BL460c & MSA2324sa

See my last post.
Timo J
Frequent Advisor

Re: Trying to get multipath working with BL460c & MSA2324sa

Hi Brad,

We have similar HW (BL460c G7 + P700 + MSA2324sa) and SW (RHEL 5.6) combo as you have. We also have similar kind of multipath problems as you did.

It was nice to read that you managed to get the combo working - Unfortunately we are still stuck with the same problem. Could you be so kind and share the multipath config here or/and share other tricks you needed to do to get the combo working?

Cheers, Timo
N/A
BradV
Esteemed Contributor

Re: Trying to get multipath working with BL460c & MSA2324sa

Hi Timo,

I think I might have miss-stated just a little. I was able to get RHEL 5.5 working, not RHEL 5.6 or RHEL 6.0. After installing 5.5, I then installed psp 8.60 (I think 8.62 is the most recent) followed by installing HPDMMultipathEnablementKit vs 4.4.1.

Vs 4.4.1 essentially just creates the multipath.conf file. The real trick the psp which builds some new kernels for you.

HP told me that they are working on hard on getting RHEL 6.0 certified, but did not give me a timetable. :(

Regards,

Brad
Timo J
Frequent Advisor

Re: Trying to get multipath working with BL460c & MSA2324sa

Thanks for the answers Brad,

Sorry to bother you again/still but we have to get the multipath working. As you seem to be only one who has managed to crack the problem here are few more questions:

1) Could you tell a bit more about your RHEL 5.5 installation? As a reference, we made a basic kickstart installation with only basic packages included:

%packages
@admin-tools
@base
@core
@development-tools
@development-libs
@system-tools
@base-x
@editors

2) Did you have the device-mapper-multipath or related package(s) installed in advance (before PSP and HPDMmultipath)?

3) Did you run yum update during the OS installation (before/after installing PSP, etc)?

4) While installing PSP we droppped all fiber channel related stuff - Did you do the same or install all suggested updates?

5) While installing the HPDMmultipath-4.4.1 kit we noticed that the install script didn't install the hp_scsi_id - did you copy it manually to /sbin/ or leave it as it is?

6) Any possibility to get to see your multipath.conf file?

Cheers, Timo
N/A
BradV
Esteemed Contributor

Re: Trying to get multipath working with BL460c & MSA2324sa

.
BradV
Esteemed Contributor

Re: Trying to get multipath working with BL460c & MSA2324sa

Hi Timo,

1) My kickstart %packages section:
%packages
@admin-tools
@base
@core
@development-libs
@development-tools
@gnome-desktop
@gnome-software-development
@graphical-internet
@java
@kvm
@legacy-software-development
@mail-sever
@network-server
@office
@x-software-development
@base-x
kexec-tools
iscsi-initiator-utils
bridge-utils
fipscheck
x86info
device-mapper-multipath
sgpio
imake
kvm-tools
vnc-server
dnsmasq
mesa-libGLU-devel
xorg-x11-utils
xorg-x11-server-Xnext
xorg-x11-server-Xvfb
expect
libnl
lm_sensors
net-snmp
-system-config-netboot
-readadhead
-krb5-workstation
-pcmciautils
-pam_smb
-pkinit-nss
-dhcpv6-client
-rsh
-rp-pppoe
-pam_krb5
-irda-utils
-ypbind
-bluez-utils
-evolution-data-server-devel
-dovecot
-spamassin

2) yes
3) no
4) PSP had it's own prerequisites. I installed all of them it asked for (had to re-run the install a couple of times) until all suggested packages were installed.
5) That is correct. The only thing it does under 5.5 is setup the multipath.conf. It doesn't use the hp_scsi_id application anymore.
6) In the mulipath.conf, I added to the blacklist:

devnode "hd[a-z][[0-9]*]"

to keep it from reading the on-board disks.

Other than that, it is just as the enablement kit made it. I have:

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

There may some typos in the above. :)

Regards,

Brad