Managing HP Serviceguard for Linux, Tenth Edition, September 2012

NOTE: Follow these rules:
• Do not try to use LVM to configure the lock LUN.
• The partition type must be 83.
• Do not create any filesystem on the partition used for the lock LUN.
• Do not use md to configure multiple paths to the lock LUN.
• HP recommends that you can configure the same multipath device name for all the
LUNs on various nodes of a cluster, so that the administration of the cluster can be
made easier.
To transfer the disk partition format to other nodes in the cluster use the command:
sfdisk -R <device>
where <device> corresponds to the same physical device as on the first node. For
example, if /dev/sdc is the device name on the other nodes use the command:
sfdisk -R /dev/sdc
You can check the partition table by using the command:
fdisk -l /dev/sdc
NOTE: fdisk may not be available for SUSE on all platforms. In this case, using
YAST2 to set up the partitions is acceptable.
Support for Lock LUN Devices
The following table describes the support for lock LUN devices on udev and device
mapper:
This is supported, but the same udev rules must be used across all nodes
in the cluster for the whole LUN or the partitioned LUN.
If udev device is selected as lock
LUN.
This is not supported on a whole LUN or a partitioned LUN.If /dev/disk/by-id, /dev/
disk/by-path, and /dev/
disk/by-uuid device is
selected as lock LUN.
This is not supported on a whole LUN or a partitioned LUN.If /dev/dm-xx is selected as
lock LUN.
This is not supported on a whole LUN or a partitioned LUN.If /dev/mpath/mpathX is
selected as lock LUN.
This is supported on a whole LUN and a partitioned LUN.If /dev/mapper/mpathX
(user-friendly names) is selected
as lock LUN.
This is supported on a whole LUN and a partitioned LUN.If /dev/mapper/xxx(aliases)
is selected as lock LUN.
168 Building an HA Cluster Configuration