Managing HP Serviceguard for Linux, Tenth Edition, September 2012

The following items are checked:
• Package name is valid, and at least one node_name entry is included.
• There are no duplicate parameter entries (except as permitted for multiple volume
groups, etc).
• Values for all parameters are within permitted ranges.
• Configured resources are available on cluster nodes.
• 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.
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 271).)
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 282).
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
Adding the Package to the Cluster 231