Managing Serviceguard Fifteenth Edition, reprinted May 2008

Cluster and Package Maintenance
Reconfiguring a Package
Chapter 7 395
Reconfiguring a Package on a Halted Cluster
You can also make permanent changes in package configuration while
the cluster is not running. Use the same steps as in “Reconfiguring a
Package on a Running Cluster” on page 394.
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 “Configuring
Packages and Their Services” on page 275. Use a commands such as the
following to verify the configuration of a newly created pkg1 and
distribute the configuration to all nodes in the cluster:
cmcheckconf -P /etc/cmcluster/pkg1/pkg1conf.ascii
cmapplyconf -P /etc/cmcluster/pkg1/pkg1conf.ascii
If this is a legacy package, remember to copy the control script to the
/etc/cmcluster/pkg1 directory on all nodes that can run the package.
To create the CFS disk group or mount point multi-node packages on
systems that support CFS, see “Creating the Disk Group Cluster
Packages” on page 254 and “Creating a File System and Mount Point
Package” on page 256.
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. To
delete one of the Veritas Cluster File System packages (on systems that
support CFS), use the cfscluster, cfsdgadm, or cfsmntadm 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.