Managing HP Serviceguard A.11.20.00 for Linux, June 2012

• File systems and volume groups are valid.
• Services are executable.
• Any package that this package depends on is already be part of the cluster configuration.
For more information, see the manpage for cmcheckconf (1m) and “Checking Cluster
Components” (page 188).
When cmcheckconf has completed without errors, apply the package configuration, for example:
cmapplyconf -P $SGCONF/pkg1/pkg1.conf
This adds the package configuration information to the binary cluster configuration file in the
$SGCONF directory and distributes it to all the cluster nodes.
NOTE: For modular packages, you now need to distribute any external scripts identified by the
external_pre_script and external_script parameters.
But, if you are accustomed to configuring legacy packages, note that you do not have to create a
separate package control script for a modular package, or distribute it manually. (You do still have
to do this for legacy packages; see “Configuring a Legacy Package” (page 210).)
Adding the Package to the Cluster
You can add the new package to the cluster while the cluster is running, subject to the value of
max_configured_packages in the cluster configuration file. See “Adding a Package to a
Running Cluster” (page 218).
Creating a Disk Monitor Configuration
Serviceguard provides disk monitoring for the shared storage that is activated by packages in the
cluster. The monitor daemon on each node tracks the status of all the disks on that node that you
have configured for monitoring.
The configuration must be done separately for each node in the cluster, because each node monitors
only the group of disks that can be activated on that node, and that depends on which packages
are allowed to run on the node.
To set up monitoring, include a monitoring service in each package that uses disks you want to
track. Remember that service names must be unique across the cluster; you can use the package
name in combination with the string cmresserviced. The following shows an entry in the package
configuration file for pkg1:
service_name cmresserviced_pkg1
service_fail_fast_enabled yes
service_halt_timeout 300
service_cmd "cmresserviced /dev/sdd1 /dsv/sde1"
service_restart none
CAUTION: Because of a limitation in LVM, service_fail_fast_enabled must be set to
yes, forcing the package to fail over to another node if it loses its storage.
NOTE: The service_cmd entry must include the cmresserviced command.
It is also important to set service_restart to none.
Adding the Package to the Cluster 179