Managing Serviceguard 14th Edition, June 2007

Building an HA Cluster Configuration

Preparing Your Systems

Chapter 5 211

nameserver 15.243.160.51

3. Edit or create the /etc/nsswitch.conf file on all nodes and add the

following text (on one line), if it does not already exist:

• for DNS, enter (one line):

hosts: files [NOTFOUND=continue UNAVAIL=continue] dns

[NOTFOUND=return UNAVAIL=return]

• for NIS, enter (one line):

hosts: files [NOTFOUND=continue UNAVAIL=continue] nis

{NOTFOUND=return UNAVAIL=return]

If a line beginning with the string “hosts:” already exists, then

make sure that the text immediately to the right of this string is (on

one line):

files [NOTFOUND=continue UNAVAIL=continue] dns

[NOTFOUND=return UNAVAIL=return]

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 configuration 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 205.

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.