Managing Serviceguard Eighteenth Edition, September 2010

3. Distribute the new script to all nodes that are configured for that package.
Make sure you place the new script in the correct directory with the proper file
modes and ownership.
4. Run cmcheckconf to validate the package configuration with the new external
script.
CAUTION: If cmcheckconf fails, do not proceed to the next step until you have
corrected all the errors.
5. Run cmapplyconf on the running package.
This will stop any resources started by the original script, and then start any
resources needed by the new script.
6. You can now safely delete the original external script on all nodes that are
configured to run the package.
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
” (page 386).
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 ” (page 279). 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” (page 263) and “Creating
a File System and Mount Point Package” (page 264).
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.
388 Cluster and Package Maintenance