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

Configuring a System
Using Distributed Systems Administration Utilities
Chapter 3 151
A possible but somewhat unusual configuration is to have a fixed
member of Serviceguard cluster act as the master server but no package
is configured so cfservd will not be highly available. This configuration is
valid but not recommended.
Configuring cfengine
The following sections provide detailed instructions for setting up a
configuration synchronization master server and its clients. The quickest
way to get started is to use the Configuration Synchronization Wizard
(csync_wizard), described below. Completely manual configurations are
also described.
Using the Configuration Synchronization Wizard
The csync_wizard (see csync_wizard (1)) automates the task of setting a
configuration synchronization master server and its managed clients. It
supports setting up a standalone system or a Serviceguard cluster as the
master server. The wizard configures all managed clients to run a
cfservd so that cfrun (see cfrun (8)) can be used on the master server.
See the appropriate sections below for details.
Using the Wizard to Configure a Standalone Synchronization
Server To configure a synchronization server for a standalone system,
run the csync_wizard(1) on the standalone system you wish to configure
as the master synchronization server:
# /opt/dsau/sbin/csync_wizard
The wizard displays the following introductory screen:
Querying the system <local hostname> for current status, one moment...
This Configuration Synchronization Wizard helps you set up the Configuration
Engine (cfengine) environment. Cfengine is a powerful tool for performing
policy-based management for groups of systems and cluster environments.
It is a client/server based utility. A standalone system or Serviceguard
cluster can be configured as the cfengine ‘master’. The master contains
the configuration description and configuration files that will be used by
all the clients. Clients copy the configuration description from the master
and apply it to themselves. The configuration description supports a rich set
of management actions such as copying configuration files from the master to
the client, performing edits to files, checking file ownerships, permissions,
and checksums, executing shell commands, checking for processes, etc.