Managing Serviceguard Fifteenth Edition, reprinted May 2008

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5210
lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c4t6d0
The following is an example of mirroring the root logical volume:
lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c4t6d0
5. Update the boot information contained in the BDRA for the mirror
copies of boot, root and primary swap.
/usr/sbin/lvlnboot -b /dev/vg00/lvol1
/usr/sbin/lvlnboot -s /dev/vg00/lvol2
/usr/sbin/lvlnboot -r /dev/vg00/lvol3
6. Verify that the mirrors were properly created.
lvlnboot -v
The output of this command is shown in a display like the following:
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c4t5d0 (10/0.5.0) -- Boot Disk
/dev/dsk/c4t6d0 (10/0.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c4t5d0
/dev/dsk/c4t6d0
Root: lvol3 on: /dev/dsk/c4t5d0
/dev/dsk/c4t6d0
Swap: lvol2 on: /dev/dsk/c4t5d0
/dev/dsk/c4t6d0
Dump: lvol2 on: /dev/dsk/c4t6d0, 0
Choosing Cluster Lock Disks
The following guidelines apply if you are using a lock disk. See “Cluster
Lock” on page 68 and “Cluster Lock Planning” on page 145 for discussion
of cluster lock options.
The cluster lock disk is configured on an LVM volume group that is
physically connected to all cluster nodes. This volume group may also
contain data that is used by packages.
When you are using dual cluster lock disks, it is required that the default
I/O timeout values are used for the cluster lock physical volumes.
Changing the I/O timeout values for the cluster lock physical volumes
can prevent the nodes in the cluster from detecting a failed lock disk
within the allotted time period which can prevent cluster re-formations
from succeeding. To view the existing IO timeout value, run the following
command: