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

Configuring a System
Using Distributed Systems Administration Utilities
Chapter 3176
The -v instructs cfrun itself to be more verbose and the
--verbose is passed on to the remote cfagent.
For additional troubleshooting information, please refer to
“cfengine Troubleshooting” on page 182.
Configuring a Synchronization Managed Client When manually
configuring managed clients, the basic steps are:
• Exchanging security keys. This establishes the trust relationship
between the managed client and master server.
• Copying update.conf from the master server to the managed client.
• Setting a schedule for which cfagent will perform synchronization
operations.
To configure a Serviceguard cluster as a client of an existing cfengine
master server, then each cluster member is treated as if it were a
standalone system and configured individually. If you add new members
to the cluster, each must be configured appropriately.
If you are adding a new member to a Serviceguard cluster and that
cluster is running the csync package, then the members of the cluster
are automatically configured as cfengine-managed clients. In this
scenario, the csync package acts as the master server. New members
will be automatically configured as a managed clients and also able to
handle failover for the package. The package’s storage infrastructure and
filesystem should be configured before adding the member to the cluster.
To add a new managed client, start by configuring the trust relationship
between the client and the master server. The two systems exchange
security keys to authenticate each other. The master server’s public key
needs to be copied to the client and the client’s public key is copied to the
master server:
1. As root, create the client’s security key using cfkey:
# mkdir -p /var/opt/cfengine/ppkeys
# cd /var/opt/cfengine/ppkeys
# /opt/dsau/sbin/cfkey
This creates the files localhost.pub and localhost.priv for this client.
2. Copy this client’s key to the master server. The master server uses
the following naming convention for the client keys,
<username> - <client_IP_address >.pub.