Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Reconfiguring a Package
Chapter 7 291
Reconfiguring a Package on a Halted Cluster
You can also make permanent changes in the package configuration
while the cluster is not running. Use the same steps as in “Reconfiguring
a Package on a Running Cluster” on page 290.
Adding a Package to a Running Cluster
You can create a new package and add it to the cluster configuration
while the cluster is up and while other packages are running. The
number of packages you can add is subject to the value of
MAX_CONFIGURED_PACKAGES in the cluster configuration file.
To create the package, follow the steps in the chapter Chapter 6,
“Configuring Packages and Their Services,” on page 199. Then use a
command such as the following to verify the configuration of the newly
created pkg1 on a running cluster:
cmcheckconf -P $SGCONF/pkg1/pkg1conf.ascii
Use a command such as the following to distribute the new package
configuration to all nodes in the cluster:
cmapplyconf -P $SGCONF/pkg1/pkg1conf.ascii
If this is a legacy package, remember to copy the control script to the
$SGCONF/pkg1 directory on all nodes that can run the package.
Deleting a Package from a Running Cluster
Serviceguard will not allow you to delete a package if any other package
is dependent on it. To check for dependencies, use cmviewcl -v -l
<package>. System multi-node packages cannot be deleted from a
running cluster.
You can use Serviceguard Manager to delete the package.
On the Serviceguard command line, you can (in most cases) delete a
package from all cluster nodes by using the cmdeleteconf command.
This removes the package information from the binary configuration file
on all the nodes in the cluster. The command can only be executed when
the package is down; the cluster can be up.
The following example halts the failover package mypkg and removes the
package configuration from the cluster: