Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4158
• If a package moves to an adoptive node, what effect will its presence
have on performance?
Create a list by package of volume groups, logical volumes, and file
systems. Indicate which nodes need to have access to common
filesystems at different times.
It is recommended that you use customized logical volume names that
are different from the default logical volume names (lvol1, lvol2, etc.).
Choosing logical volume names that represent the high availability
applications that they are associated with (for example, lvoldatabase)
will simplify cluster administration.
To further document your package-related volume groups, logical
volumes, and file systems on each node, you can add commented lines to
the /etc/fstab file. The following is an example for a database application:
# /dev/vg01/lvoldb1 /applic1 vxfs defaults 0 1 # These six e
ntries are
# /dev/vg01/lvoldb2 /applic2 vxfs defaults 0 1 # for informa
tion purposes
# /dev/vg01/lvoldb3 raw_tables ignore ignore 00#only.They
record the
# /dev/vg01/lvoldb4 /general vxfs defaults 0 2 # logical vol
umes that
# /dev/vg01/lvoldb5 raw_free ignore ignore 0 0 # exist for S
erviceguard's
# /dev/vg01/lvoldb6 raw_free ignore ignore 0 0 # HA package.
Do not uncomment.
Create an entry for each logical volume, indicating its use for a file
system or for a raw device.
CAUTION Do not use /etc/fstab to mount file systems that are used by
Serviceguard packages.
Details about creating, exporting, and importing volume groups in
Serviceguard are given in the chapter on “Building an HA Cluster
Configuration.”