Managing Serviceguard Eighteenth Edition, September 2010

Table 7-3 Types of Changes to Packages (continued)
Required Package StateChange to the Package
Both packages can be either running or halted.
Special rules apply to packages in maintenance mode; see “Dependency
Rules for a Package in Maintenance Mode or Partial-Startup Maintenance
Mode ” (page 356).
For dependency purposes, a package being reconfigured is considered
to be UP. This means that if pkgA depends on pkgB, and pkgA is down
and pkgB is being reconfigured, pkgA will run if it becomes eligible to
do so, even if pkgB's reconfiguration is not yet complete.
HP recommends that you separate package dependency changes from
changes that affect resources and services that the newly dependent
package will also depend on; reconfigure the resources and services
first and apply the changes, then configure the package dependency.
For more information see “About Package Dependencies” (page 179).
Add or delete a configured
dependency
Before you can add an SG-CFS-DG-id# disk group package, the
SG-CFS-pkg Cluster File System package must be up and running.
Before you can add an SG-MP-id# mount point package to a node, the
SG-DG-id# disk group package must be up and running on that node.
Add CFS packages
NOTE: Check the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility
and Feature Matrix and the latest Release Notes for your version of Serviceguard for
up-to-date information on CVM and CFS support:
www.hp.com/go/hpux-serviceguard-docs.
Changes that Will Trigger Warnings
Changes to the following will trigger warnings, giving you a chance to cancel, if the
change would cause the package to fail.
NOTE: You will not be able to cancel if you use cmapplyconf -f.
• Package nodes
• Package dependencies
• Package weights (and also node capacity, defined in the cluster configuration file)
• Package priority
• auto_run
• failback_policy
•
396 Cluster and Package Maintenance