HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

model, see the HP-UX IPSec Version A.03.00 Administrator's Guide which you can find at
http://www.hp.com/go/hpux-security-docs —> HP-UX IPSec Software.
ip_strong_es_model is disabled (set to 0) by default. Setting it to 1 enables it.
CAUTION: HP supports enabling this parameter only if you are not using a cross-subnet
configuration (page 30). Otherwise, leave the parameter at its default setting (zero, meaning
disabled).
Enabling this parameter allows you to configure a default gateway for each physical IPv4
interface. These gateways allow a system to send an unbound packet through the interface
for the address to which the socket (or communication endpoint) is bound. If the socket (or
communication endpoint) is not bound to a specific address, the system sends the packet
through the interface on which the unbound packet was received.
This means that the packet source addresses (and therefore the interfaces on a multihomed
host) affect the selection of a gateway for outbound packets once ip_strong_es_model
is enabled. For more information see “Using a Relocatable Address as the Source Address
for an Application that is Bound to INADDR_ANY” (page 349).
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.
IMPORTANT: This must be done, as described below, whether or not you intend to use
cmpreparestg (1m) to configure storage. See “Using Easy Deployment Commands to Configure
the Cluster” (page 162) for more information about cmpreparestg.
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)” (page 80).
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
4. Mirror the boot, primary swap, and root logical volumes to the new bootable disk. Ensure
that all devices in vg00, such as those for /usr, /swap, are mirrored.
NOTE: The boot, root, and swap logical volumes must be done in exactly the following
order to ensure that the boot volume occupies the first contiguous set of extents on the new
disk, followed by the swap and the root.
The following is an example of mirroring the boot logical volume:
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c4t6d0
The following is an example of mirroring the primary swap logical volume:
lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c4t6d0
172 Building an HA Cluster Configuration