Managing Serviceguard 13th Edition, February 2007

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5 199
files [NOTFOUND=continue UNAVAIL=continue] dns
[NOTFOUND=return UNAVAIL=return]
or
files [NOTFOUND=continue UNAVAIL=continue] nis
[NOTFOUND=return UNAVAIL=return]
This step is critical, allowing the cluster nodes to resolve hostnames
to IP addresses while DNS, NIS, or the primary LAN is down.
4. If no cluster exists on a system that you intend to configure into the
cluster, create a $SGCONF/cmclnodelist file on all nodes and allow
access by all cluster nodes. See “Using the cmclnodelist File” on
page 193.
Creating Mirrors of Root Logical Volumes
HP strongly recommends that you use mirrored root volumes on all
cluster nodes. The following procedure assumes that you are using
separate boot and root volumes; you create a mirror of the boot volume
(/dev/vg00/lvol1), primary swap (/dev/vg00/lvol2), and root volume
(/dev/vg00/lvol3). In this example and in the following commands,
/dev/dsk/c4t5d0 is the primary disk and /dev/dsk/c4t6d0 is the
mirror; be sure to use the correct device file names for the root disks on
your system.
NOTE Under agile addressing, the physical devices in these examples would
have names such as /dev/[r]disk/disk1
, and /dev/[r]disk/disk2.
See “About Device File Names (Device Special Files)” on page 115.
1. Create a bootable LVM disk to be used for the mirror.
# pvcreate -B /dev/rdsk/c4t6d0
2. Add this disk to the current root volume group.
# vgextend /dev/vg00 /dev/dsk/c4t6d0
3. Make the new disk a boot disk.
# mkboot -l /dev/rdsk/c4t6d0