No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Huawei SAN Storage Host Connectivity Guide for SUSE

HUAWEI SAN Storage Host Connectivity Guide for SUSE Linux Servers
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Working Principle

Working Principle

Heartbeat consists of three components.

  • CCM

    Cluster Consensus Membership (CCM) manages a cluster's member nodes, inter-node relationship, and inter-node resource allocation. Heartbeat uses CCM to monitor the running status of primary and secondary nodes in a cluster. ha-logd records the running information about all modules and services in a cluster.

  • LRM

    Local Resource Manager (LRM) starts, stops, and monitors local resources. This component consists of LRM daemon process lrmd and node monitoring process STONITH daemon. lrmd manages inter-node communication. STONITH daemon usually is a fence device used for monitoring node status. A normal node can use the fence device to restart or shut down a faulty node to release resources like IP addresses and disks. In this way, resources are always owned by one node, preventing resource contention.

  • CRM

    Cluster Resource Manager (CRM) manages inter-node dependencies and resources as well as node resource usage. Normally, CRM consists of the daemon process crmd, cluster policy engine, and cluster failover engine. The cluster policy engine manages dependencies and resource usage. The cluster failover engine monitors the CRM status and invokes process on nodes for necessary resource takeover.

The cores of a Heartbeat cluster are heartbeat monitoring and resource takeover. Heartbeat monitoring is implemented through serial ports. Every two nodes send packets in between through the serial cable to inform each other of the current status. If any one of the nodes does not receive packets sent from the other, the node whose packets are not received is detected as failed. Immediately, the resource takeover module takes over services or resources from the failed node.

Updated: 2019-05-16

Document ID: EDOC1000150158

Views: 38280

Downloads: 535

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next