HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

Table 15 Types of Changes to Packages (continued)
Required Package StateChange to the Package
For information on online changes to generic resources, see “Online
Reconfiguration of Generic Resources” (page 136).
Package can be running for resources of evaluation type before_package_start
or during_package_start provided the new up criteria does not cause the resource
status to evaluate to 'down'.
Change the
generic_resource_up_criteria
Not allowed if changing the generic_resource_up_criteria causes the package to
fail.
For information on online changes to generic resources, see “Online
Reconfiguration of Generic Resources” (page 136).
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: http://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
Responding to Cluster Events
Serviceguard does not require much ongoing system administration intervention. As long as there
are no failures, your cluster will be monitored and protected. In the event of a failure, those packages
that you have designated to be transferred to another node will be transferred automatically. Your
ongoing responsibility as the system administrator will be to monitor the cluster and determine if
a transfer of package has occurred. If a transfer has occurred, you have to determine the cause
and take corrective actions.
The Event Monitoring Service and its HA monitors can provide monitoring for disks, LAN cards,
and some system events. Refer to the manual Using HA Monitors for more information.
The typical corrective actions to take in the event of a transfer of package include:
• Determining when a transfer has occurred.
• Determining the cause of a transfer.
• Repairing any hardware failures.
• Correcting any software problems.
• Restarting nodes.
• Transferring packages back to their original nodes.
Responding to Cluster Events 319