Managing HP Serviceguard A.11.20.00 for Linux, June 2012

Command (m for help): n
Partition number (1-4): 1
HEX code (type L to list codes): 83
Command (m for help): 1
Command (m for help): 1
Command (m for help): p
Disk /dev/sdc: 64 heads, 32 sectors, 4067 cylinders
Units = cylinders of 2048 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sdc 1 1 1008 83 Linux
Command (m for help): w
The partition table has been altered!
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.
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.
Setting Up and Running the Quorum Server
If you will be using a quorum server rather than a lock LUN, the Quorum Server software must be
installed on a system other than the nodes on which your cluster will be running, and must be
running during cluster configuration.
For detailed discussion, recommendations, and instructions for installing, updating, configuring,
and running the Quorum Server, see the HP Serviceguard Quorum Server Version A.04.00 Release
Notes at http://www.hp.com/go/hpux-serviceguard-docs->HP Serviceguard
Quorum Server Software. See also the discussion of the QS_HOST and QS_ADDR parameters
under “Cluster Configuration Parameters ” (page 80).
Creating the Logical Volume Infrastructure
Serviceguard makes use of shared disk storage. This is set up to provide high availability by using
redundant data storage and redundant paths to the shared devices. Storage for a Serviceguard
package is logically composed of LVM Volume Groups that are activated on a node as part of
starting a package on that node. Storage is generally configured on logical units (LUNs).
Disk storage for Serviceguard packages is built on shared disks that are cabled to multiple cluster
nodes. These are separate from the private Linux root disks, which include the boot partition and
130 Building an HA Cluster Configuration