Managing HP Serviceguard for Linux Ninth Edition, April 2009

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 252).)
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 263).
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.
220 Configuring Packages and Their Services