3.6. Configuring Cluster Daemons

The Red Hat Cluster Manager provides the following daemons to monitor cluster operation:

Each of these daemons can be individually configured using the Cluster Configuration Tool. To access the Cluster Daemon Properties dialog box, choose Cluster => Daemon Properties.

The following sections explain how to configure cluster daemon properties. However, note that the default values are applicable to most configurations and do not need to be changed.

3.6.1. Configuring clumembd

On each cluster system, the clumembd daemon issues heartbeats (pings) across the point-to-point Ethernet lines to which the cluster members are connected.

Figure 3-8. Configuring clumembd


You can enable both broadcast heartbeating and multicast heartbeating, but at least one of these features must be used.

Multicast heartbeating over a channel-bonded Ethernet interface provides good fault tolerance and is recommended for availability.

You can specify the following properties for the clumembd daemon:

3.6.2. Configuring cluquorumd

In a two-member cluster without a specified tiebreaker IP address, the cluquorumd daemon periodically writes a time-stamp and system status to a specific area on the primary and shadow shared partitions. The daemon also reads the other member's timestamp and system status information from the primary shared partition or, if the primary partition is corrupted, from the shadow partition.

Figure 3-9. Configuring cluquorumd

You can specify the following properties for the cluquorumd daemon:

3.6.3. Configuring clurmtabd

The clurmtabd daemon synchronizes NFS mount entries in /var/lib/nfs/rmtab with a private copy on a service's mount point. The clurmtabd daemon runs only when a service with NFS exports is running.

Figure 3-10. Configuring clurmtabd

You can specify the following properties for the clurmtabd daemon:

3.6.4. Configuring the clusvcmgrd daemon

On each cluster system, the clusvcmgrd service manager daemon responds to changes in cluster membership by stopping and starting services. You might notice, at times, that more than one clusvcmgrd process is running; separate processes are spawned for start, stop, and monitoring operations.

Figure 3-11. Configuring clusvcmgrd

You can specify the following properties for the clusvcmgrd daemon:

3.6.5. Configuring clulockd

The clulockd daemon manages the locks on files being accessed by cluster members.

Figure 3-12. Configuring clulockd

You can specify the following properties for the clulockd daemon: