HP Serviceguard for Linux Version A.11.18 Deployment Guide, August 2008

22
b. Copy the sample multipath.conf file provided in the kit to the /etc directory (input as
one line):
cp /usr/share/doc/HPDMmultipath-tools-
4.0.0/multipath.conf.HPTemplate /etc/multipath.conf
c. Open the /etc/multipath.conf file to add a “device” subsection entry for the
MSA2000 within the “devices { }” block as follows:
device
{
vendor "HP”
product "MSA2[02]*"
path_grouping_policy multibus
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
path_selector "round-robin 0"
rr_weight uniform
prio_callout "/bin/true"
path_checker tur
hardware_handler "0"
failback immediate
no_path_retry 12
rr_min_io 100
}
7. Restart the multipath daemon by executing the following commands:
/etc/init.d/multipathd restart
/sbin/multipath
8. To view status of multipath devices, execute the following command:
/sbin/multipath -ll
The sample output shows there are 3 mpaths to the 3 volumes created on the MSA, dm-4,
dm-3, and dm-2 and the physical paths they are mapped to, for example, dm-4 maps to sdc
and sdf.
mpath2 (3600c0ff000d50322ff8a3e4803000000) dm-4 HP,MSA2012fc
[size=287M][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 0:0:1:2 sdc 8:32 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:2 sdf 8:80 [active][ready]
mpath1 (3600c0ff000d50322ff8a3e4802000000) dm-3 HP,MSA2012fc
[size=191M][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 0:0:1:1 sdb 8:16 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:1 sde 8:64 [active][ready]
mpath0 (3600c0ff000d50322ff8a3e4801000000) dm-2 HP,MSA2012fc
[size=96M][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 0:0:1:0 sda 8:0 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:0 sdd 8:48 [active][ready]
Configuring the Lock LUN and Shared Volumes
In this section, we will be configuring 3 shared volumes. The first is for the Serviceguard for Linux
cluster lock LUN, a special area of the disk used for cluster arbitration during cluster re-formation.
While this deployment guide provides steps to configure a lock LUN, a quorum server can also be
used for cluster arbitration. The quorum server is a separate software package that comes with
Serviceguard for Linux and requires a third server. The second volume will be used as a shared data