Managing HP Serviceguard A.11.20.20 for Linux, May 2013

and start the package for the first time. But if you then halt the multi-node package via
cmhaltpkg, it can be re-started only by means of cmrunpkg, not cmmodpkg.
• If a multi-node package is halted via cmhaltpkg, package switching is not disabled. This
means that the halted package will start to run on a rebooted node, if it is configured to run
on that node and its dependencies are met.
• When a multi-node package is started the first time (either at cluster startup, or subsequently
if auto_run is set to no, and package switching is then enabled) any dependent package
will start on its primary node. But if a multi-node package is halted along with its dependent
packages, and the multi-node package is then restarted, dependent packages which have
had package switching re-enabled will start on the first eligible node on which an instance of
the multi-node package comes up; this may not be the dependent packages’ primary node.
To ensure that dependent failover packages restart on their primary node if the multi-node
packages they depend on need to be restarted, make sure the dependent packages’ package
switching is not re-enabled before the multi-node packages are restarted. You can then either
restart the dependent failover packages with cmrunpkg, specifying the node you want them
to start on, or enable package switching for these packages after the multi-node package
startup is complete.
6.1.3 Package Modules and Parameters
The table that follows shows the package modules and the configuration parameters each module
includes. Read this section in conjunction with the discussion under “Package Configuration Planning
” (page 104).
Use this information, and the parameter explanations that follow (page 174) to decide which modules
(if any) you need to add to the failover, multi-node, or system multi-node module, to create your
package. If you are used to creating legacy packages, you will notice that parameters from the
package control script (or their equivalents) are now in the package configuration file; these
parameters are marked (S) in the table.
You can use cmmakepkg -l (letter “l”) to see a list of all available modules, including
non-Serviceguard modules such as those supplied in the HP Toolkits.
NOTE: If you are going to create a complex package that contains many modules, you may
want to skip the process of selecting modules, and simply create a configuration file that contains
all the modules:
cmmakepkg -m sg/all $SGCONF/pkg_sg_complex
(The output will be written to $SGCONF/pkg_sg_complex.)
6.1.3.1 Base Package Modules
At least one base module (or default or all, which include the base module) must be specified
on the cmmakepkg command line. Parameters marked with an asterisk (*) are new or changed
as of Serviceguard A.11.18, A.11.19, A.11.20.00, A.11.20.10, or A.11.20.20 (S) indicates
that the parameter (or its equivalent) has moved from the package control script to the package
configuration file for modular packages. See the “Package Parameter Explanations” (page 174) for
more information.
6.1 Choosing Package Modules 171