Managing Serviceguard 13th Edition, February 2007

Cluster and Package Maintenance
Reconfiguring a Package
Chapter 7 337
-R -s command, thus enabling the service in future restart situations
to have the full number of restart attempts up to the configured
SERVICE_RESTART count. Example:
# cmmodpkg -R -s myservice pkg1
The current value of the restart counter may be seen in the output of the
cmviewcl -v command.
Allowable Package States During Reconfiguration
All nodes in the cluster must be powered up and accessible when making
configuration changes.
Refer to Table 7-2 to determine whether or not the package may be
running while you implement a particular kind of change. Note that for
all of the following cases the cluster may be running, and also packages
other than the one being reconfigured may be running.
Table 7-2 Types of Changes to Packages
Change to the
Package Required Package State
Add a new
package
Other packages may be in any state.
Delete a package Package must not be running. You cannot delete a
package if another package has a configured
dependency on it.
Add a service Package must not be running.
Remove a service Package must not be running.
Add a subnet Package must not be running. Subnet must
already be configured into the cluster.
Remove a subnet Package must not be running.
Add a resource Package must not be running.
Remove a
resource
Package must not be running.