Managing Systems and Workgroups: A Guide for HP-UX System Administrators
Configuring a System
Using Distributed Systems Administration Utilities
Chapter 3 201
Starting the "clog" Serviceguard package, this will take a few moments...
The "clog" Serviceguard package has been started on cluster-member.
Successfully created the "clog" Serviceguard package.
Successfully configured clustername as a log consolidation server.
Cluster Configuration Notes
In a Serviceguard cluster, the adoptive node for the clog package
performs the log consolidation functions. All the other cluster members
participate as log forwarding clients and send log messages to the
relocatable IP address of the clog package.
DSAU maintains two configuration files that control whether the
instance of syslog-ng on a particular cluster member operates as a
consolidation server or a log forwarding client:
/etc/syslog-ng.conf.server and /etc/syslog-ng.conf.client.
The symbolic link /etc/syslog-ng.conf points to one of the
configuration files. When the cluster is booted, all the members start as
log forwarding clients with syslog-ng running on each member. The
/sbin/init.d/syslog-ng startup script sets the symbolic link
/etc/syslog-ng.conf to point to /etc/syslog-ng.conf.client.
When the clog package starts, the adoptive node restarts that instance
of syslog-ng as a log consolidation server instance. The package script
resets the /etc/syslog-ng.conf symbolic link to point to
/etc/syslog-ng.conf.server.
If the clog package is halted, the symlink is changed to point to
/etc/syslog-ng.conf.client and the syslog-ng instance on that
member restarted. Note that when a cluster is a log consolidation server,
and the package is down, no log consolidation occurs and forwarded log
messages are lost.
Note that cluster members can forward log messages to the consolidator
using either UDP or TCP. Within a Serviceguard cluster, ssh port
forwarding is not used. ssh port forwarding can be used to secure the log
traffic forwarded by remote clients outside the cluster. For additional
information, refer to “ssh Port Forwarding” on page 235.