HP Serviceguard for Linux Version A.11.19 Deployment Guide, September 2012

20
path_checker tur
hardware_handler "0"
failback immediate
no_path_retry 12
rr_min_io 100
}
3. Restart the multipath daemon by executing the following commands:
/etc/init.d/multipathd restart
/sbin/multipath
4. 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]
NOTE: If you have problem viewing the 3 mpaths to the 3 volumes, try running the following
command:
/opt/hp/hp_fibreutils/hp_rescan -a
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
volume for the sample Serviceguard for Linux package (ws) to be created in a later step. And the
third volume is for the DSAU consolidated log (clog), which allows the user to view consolidated
syslog and Serviceguard package logs for the entire cluster from a central location. The consolidated
log will be configured as a Serviceguard for Linux package, also in a later step.
Most of the shared volume configuration is performed on the first node. The configuration can then
be imported to the second node. A few of the steps must be performed on both nodes.
Table 3 shows the details for the 3 shared volumes used in this sample deployment.