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

As part of planning, you need to decide the following:
• What volume groups are needed?
• How much disk space is required, and how should this be allocated in logical volumes?
• What file systems need to be mounted for each package?
• Which nodes need to import which logical volume configurations?
• If a package moves to an adoptive node, what effect will its presence have on performance?
• What hardware/software resources need to be monitored as part of the package? You can
then configure these as generic resources in the package and write appropriate monitoring
scripts for monitoring the resources.
NOTE: Note that generic resources influences the package based on the status. The actual
monitoring of the resource should be done in a script and this must be configured as a service.
The script sets the status of the resource based on the availability of the resource. See
“Monitoring Script for Generic Resources” (page 390).
Create a list by package of volume groups, logical volumes, and file systems. Indicate which nodes
need to have access to common file systems at different times.
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 0 0 # 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/SMS/Serviceguard Manager Plug-in 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.hp.com/go/hpux-serviceguard-docs.
For a failover package that uses CVM or CFS, you configure system multi-node packages to handle
the volume groups and file systems.
CAUTION: Serviceguard manages Veritas processes, specifically gab and LLT, through system
multi-node packages. As a result, the Veritas administration commands such as gabconfig,
llthosts, and lltconfig should only be used in display mode, for example gabconfig -a.
You could crash nodes or the entire cluster if you use Veritas commands such as the gab* or llt*
commands to configure these components or affect their runtime behavior.
CVM 4.1 and later without CFS
Veritas Cluster Volume Manager 4.1 and later uses the system multi-node package SG-CFS-pkg
to manage the cluster’s volumes.
126 Planning and Documenting an HA Cluster