Managing Serviceguard Nineteenth Edition, Reprinted June 2011

• /usr/lbin/cmfileassistd—Serviceguard File Management daemon
• /usr/lbin/cmlogd—Serviceguard Syslog Log Daemon
• /usr/lbin/cmlvmd—Cluster Logical Volume Manager Daemon
• /opt/cmom/lbin/cmomd—Cluster Object Manager Daemon
• /usr/lbin/cmsnmpd—Cluster SNMP subagent (optionally running)
• /usr/lbin/cmserviced—Serviceguard Service Assistant Daemon
• /usr/lbin/qs—Serviceguard Quorum Server Daemon
• /usr/lbin/cmnetd—Serviceguard Network Manager daemon.
• /usr/lbin/cmvxd—Serviceguard-to-Veritas Membership Coordination daemon. (Only
present if Veritas CFS is installed.)
• /usr/lbin/cmvxpingd—Serviceguard-to-Veritas Activation daemon. (Only present if Veritas
CFS is installed.)
• /usr/lbin/cmdisklockd— Lock LUN daemon
• /usr/lbin/cmlockd—Utility daemon
• /opt/sgproviders/bin/cmwbemd—WBEM daemon
• /usr/lbin/cmproxyd—Proxy daemon
Each of these daemons logs to the /var/adm/syslog/syslog.logfile except for /opt/cmom/
lbin/cmomd, which logs to /var/opt/cmom/cmomd.log. The Quorum Server runs outside
the cluster. By default, it logs to the standard output, and it is suggested you redirect output to a
file named/var/adm/qs/qs.log.
Configuration Daemon: cmclconfd
This daemon is used by the Serviceguard commands to gather information from all the nodes
within the cluster. It gathers configuration information such as information on networks and volume
groups. It also distributes the cluster binary configuration file to all nodes in the cluster. This daemon
is started by inetd(1M). There are entries in the /etc/inetd.conf file.
Cluster Daemon: cmcld
This daemon determines cluster membership by sending heartbeat messages to cmcld daemons
on other nodes in the Serviceguard cluster. It runs at a real time priority and is locked in memory.
The cmcld daemon sets a safety timer in the kernel which is used to detect kernel hangs. If this
timer is not reset periodically by cmcld, the kernel will cause a system TOC (Transfer of Control)
or INIT, which is an immediate system reset without a graceful shutdown. (This manual normally
refers to this event simply as a system reset.) This could occur because cmcld could not communicate
with the majority of the cluster’s members, or because cmcld exited unexpectedly, aborted, or
was unable to run for a significant amount of time and was unable to update the kernel timer,
indicating a kernel hang. Before a system reset resulting from the expiration of the safety timer,
messages will be written to /var/adm/syslog/syslog.log and the kernel’s message buffer,
and a system dump is performed.
The duration of the safety timer depends on the cluster configuration parameter MEMBER_TIMEOUT,
and also on the characteristics of the cluster configuration, such as whether it uses a Quorum
Server or a cluster lock (and what type of lock) and whether or not standby LANs are configured.
For further discussion, see “What Happens when a Node Times Out” (page 85). For advice on
setting MEMBER_TIMEOUT, see “Cluster Configuration Parameters ” (page 105). For troubleshooting,
see “Cluster Re-formations Caused by MEMBER_TIMEOUT Being Set too Low” (page 320).
cmcld also manages Serviceguard packages, determining where to run them and when to start
them.
Serviceguard Architecture 39