Managing Serviceguard Nineteenth Edition, Reprinted June 2011

To remove the legacy CVM disk groups and CFS mount points, follow these steps:
CAUTION: You must not use the HP-UX mount and umount commands in a CFS environment;
use cfsmount or cfsumount for legacy CFS packages. For modular packages, you must use
cmcheckconf, cmapplyconf, cmrunpkg, cmmodpkg, and cmrunpkg. Non-CFS commands
(for example, mount -o cluster, dbed_chkptmount, or sfrac_chkptmount) could cause
conflicts with subsequent operations on the file system or Serviceguard packages, and will not
create an appropriate multi-node package, with the result that cluster packages are not aware of
file system changes.
1. Remove any dependencies on the package being deleted. Delete dependency_ parameters
from the failover application package configuration file, then apply the modified configuration
file:
cmapplyconf -v -P app1.conf
2. Unmount the shared file system
cfsumount <mount point>
3. Remove the mount point package from the cluster
cfsmntadm delete <mount point>
This disassociates the mount point from the cluster. When there is a single volume group
associated with the mount point, the disk group package will also be removed
4. Remove the disk group package from the cluster. This disassociates the disk group from the
cluster.
cfsdgadm delete <disk group>
Resetting the Service Restart Counter
The service restart counter is the number of times a package service has been automatically restarted.
This value is used to determine when the package service has exceeded its maximum number of
allowable automatic restarts.
When a package service successfully restarts after several attempts, the package manager does
not automatically reset the restart count. You can reset the counter online using the cmmodpkg -R
-s command. For example:
cmmodpkg -R -s myservice pkg1
The current value of the restart counter is shown in the output of cmviewcl -v.
Allowable Package States During Reconfiguration
In many cases, you can make changes to a package’s configuration while the package is running.
The table that follows shows exceptions — cases in which the package must not be running, or in
300 Cluster and Package Maintenance