Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Configuring a System
Using Distributed Systems Administration Utilities
Chapter 3160
commands, refer to“cfengine Daemons and Commands” on page 147. The
Serviceguard package ensures that cfengine’s cfservd daemon
remains highly available. The cfengine configuration files update.conf
and cfagent.conf define the master configuration synchronization
server to be the registered DNS name for the relocatable IP address of
the package. When managed clients run cfagent (see cfagent (8)),
cfagent connects to cfservd on the package’s adoptive node. Thus the
cluster members themselves are all managed clients. The member
hosting the package additionally acts as the master server for the policy
files.
When booting the cluster, each member will start a client cfservd. This
is the cfservd that responds to cfrun requests. When the package starts
on a member, that cfservd now has access to the filesystem of the
package and becomes the master cfservd that serves the policy files to
all managed clients. This cfservd is monitored by the package. If
cfservd fails, the package will attempt to restart on another member.
That member’s cfservd will then become the master cfservd.
Note that halting the package does not stop the cfservd daemon on the
adoptive member since the expectation is that the daemon is present to
respond to future cfrun requests. Also, unlike some other HA services, if
the csync package is down or unavailable, remote clients are not
adversely impacted. The clients continue to run with their currently
defined configurations. The administrator would need to make sure the
package is up and running in order to distribute any new configuration
instructions to the managed clients.
The wizard automates cfengine key distribution to all cluster members.
For a detailed description of key distribution steps performed, refer to
“Security Notes” on page 178.
Serviceguard Automation Features The Distributed Systems
Administration Utilities require Serviceguard 11.17 or later. With
Serviceguard 11.17 or later, when members are added to or deleted from
the cluster the configuration synchronization tools will automatically
take the appropriate configuration actions. Specifically:
• When adding a member to the cluster, the new member will be
automatically configured to participate in configuration
synchronization. The following configuration actions occur
automatically on the added member:
1. etc/rc.config.d/cfservd is changed to set
CSYNC_CONFIGURED to 1