Managing HP Serviceguard for Linux Ninth Edition, April 2009

NOTE: All the nodes in the cluster must be powered up and accessible when you
make package configuration changes.
Table 7-2 Types of Changes to Packages
Required Package StateChange to the Package
Package must not be running.
NOTE: You cannot delete a package if another package has a dependency
on it.
Delete a package
Package must not be running.Change package type
Package can be running.Add or delete a module:
modular package
Package can be running, but should not be starting.
Timing problems may occur if the script is changed while the package is
starting.
Change run script contents:
legacy package
Package can be running, but should not be halting.
Timing problems may occur if the script is changed while the package is
halting.
Change halt script
contents: legacy package
Package can be running.
Serviceguard treats any change to service_name or service_cmd as deleting
the existing service and adding a new one, meaning that the existing service
is halted.
Add or delete a service:
modular package
Package must not be running.Add or delete a service:
legacy package
Package can be running.
Serviceguard will not allow the change if the new value is less than the
current restart count. (You can use cmmodpkg -R<service_name>
<package> to reset the restart count if you need to.)
Change service_restart:
modular package
Package must not be running.Change
SERVICE_RESTART: legacy
package
Package must not be running. (Also applies to cross-subnet configurations.)
Package must not be running. Subnet must already be configured into the
cluster.
Add or remove a SUBNET
(in control script): legacy
package
Package can be running.
See “ip_subnet” (page 205) for important information. Serviceguard will reject
the change if you are trying to add an ip_subnet that is not configured on all
the nodes on the package's node_name list.
Add or remove an
ip_subnet: modular package
Reconfiguring a Package 265