Managing Serviceguard Fifteenth Edition, reprinted May 2008

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4 171
HP recommends 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 entries are
# /dev/vg01/lvoldb2 /applic2 vxfs defaults 0 1 # for information purposes
# /dev/vg01/lvoldb3 raw_tables ignore ignore 00#only. They record the
# /dev/vg01/lvoldb4 /general vxfs defaults 0 2 # logical volumes that
# /dev/vg01/lvoldb5 raw_free ignore ignore 0 0 # exist for Serviceguard'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. Don’t forget to comment out the lines (using
the # character as shown).
NOTE Do not use /etc/fstab to mount file systems that are used by
Serviceguard packages.
Planning Veritas Cluster Volume Manager (CVM) and
Cluster File System (CFS)
NOTE Check the Serviceguard, SGeRAC, and SMS Compatibility and Feature
Matrix and the latest Release Notes for your version of Serviceguard for
up-to-date information on support for CVM and CFS:
http://www.docs.hp.com -> High Availability -> Serviceguard.
For a failover package that uses the CVM or CFS, you configure system
multi-node packages to handle the volume groups and file systems.