SUSE Linux Enterprise Server

Heartbeat Guide

Publication Date 04 Feb 2011

Legal Notice

This manual is protected under Novell intellectual property rights. By reproducing, duplicating or distributing this manual you explicitly agree to conform to the terms and conditions of this license agreement.

This manual may be freely reproduced, duplicated and distributed either as such or as part of a bundled package in electronic and/or printed format, provided however that the following conditions are fulfilled:

That this copyright notice and the names of authors and contributors appear clearly and distinctively on all reproduced, duplicated and distributed copies. That this manual, specifically for the printed format, is reproduced and/or distributed for noncommercial use only. The express authorization of Novell, Inc must be obtained prior to any other use of any manual or part thereof.

For Novell trademarks, see the Novell Trademark and Service Mark list http://www.novell.com/company/legal/trademarks/tmlist.html. * Linux is a registered trademark of Linus Torvalds. All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a Novell trademark; an asterisk (*) denotes a third party trademark.

All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither Novell, Inc., SUSE LINUX Products GmbH, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.

Contents

About This Guide

1. Feedback
2. Documentation Updates
3. Documentation Conventions

1. Overview

1.1. Product Features
1.2. Product Benefits
1.3. Cluster Configurations
1.4. Heartbeat Cluster Components
1.5. Architecture

2. Installation and Setup

2.1. Hardware Requirements
2.2. Software Requirements
2.3. Shared Disk System Requirements
2.4. Preparations
2.5. Installing Heartbeat
2.6. Configuring STONITH

3. Setting Up a Simple Resource

3.1. Configuring a Resource with the Heartbeat GUI
3.2. Manual Configuration of a Resource

4. Configuring and Managing Cluster Resources

4.1. Graphical HA Management Client
4.2. Creating Cluster Resources
4.3. Configuring Resource Constraints
4.4. Specifying Resource Failover Nodes
4.5. Specifying Resource Failback Nodes (Resource Stickiness)
4.6. Configuring Resource Monitoring
4.7. Starting a New Cluster Resource
4.8. Removing a Cluster Resource
4.9. Configuring a Heartbeat Cluster Resource Group
4.10. Configuring a Heartbeat Clone Resource
4.11. Migrating a Cluster Resource

5. Manual Configuration of a Cluster

5.1. Configuration Basics
5.2. Configuring Resources
5.3. Configuring Constraints
5.4. Configuring CRM Options
5.5. For More Information

6. Managing a Cluster

cibadmin — read, modify, or administer Heartbeat Cluster Information Base
crmadmin — control the Cluster Resource Manager
crm_attribute — manipulate attributes in the CIB
crm_diff — identify changes to the cluster configuration and apply patches to the configuration files
crm_failcount — manipulate the failcount attribute on a given resource
crm_master — determine which resource instance to promote to master
crm_mon — monitor the cluster's status
crm_resource — interact with the Cluster Resource Manager
crm_standby — manipulate a node's standby attribute to determine whether resources can be run on this node
crm_uuid — get a node's UUID
crm_verify — check the CIB for consistency

7. Creating Resources

7.1. STONITH Agents
7.2. Resource Agents
7.3. Writing OCF Resource Agents

8. Troubleshooting

A. HB OCF Agents

ocf:apache — Apache web server
ocf:AudibleAlarm — AudibleAlarm resource agent
ocf:ClusterMon — ClusterMon resource agent
ocf:db2 — db2 resource agent
ocf:Delay — Delay resource agent
ocf:drbd — This resource agent manages a Distributed Replicated Block Device (DRBD) object as a master/slave resource. DRBD is a mechanism for replicating storage; please see the documentation for setup details.
ocf:Dummy — Dummy resource agent
ocf:eDir88 — eDirectory resource agent
ocf:Evmsd — Evmsd resource agent
ocf:EvmsSCC — EVMS SCC resource agent
ocf:Filesystem — Filesystem resource agent
ocf:ICP — ICP resource agent
ocf:ids — OCF resource agent for the IBM's database server called Informix Dynamic Server (IDS)
ocf:IPaddr2 — Manages virtual IPv4 addresses
ocf:IPaddr — Manages virtual IPv4 addresses
ocf:IPsrcaddr — IPsrcaddr resource agent
ocf:IPv6addr — manages IPv6 alias
ocf:iscsi — iscsi resource agent
ocf:Ldirectord — Wrapper OCF Resource Agent for ldirectord
ocf:LinuxSCSI — LinuxSCSI resource agent
ocf:LVM — LVM resource agent
ocf:MailTo — MailTo resource agent
ocf:ManageRAID — Manages RAID devices
ocf:ManageVE — OpenVZ VE resource agent
ocf:mysql — MySQL resource agent
ocf:o2cb — OCFS2 membership layer manager.
ocf:oracle — oracle resource agent
ocf:oralsnr — oralsnr resource agent
ocf:pgsql — pgsql resource agent
ocf:pingd — pingd resource agent
ocf:portblock — portblock resource agent
ocf:Pure-FTPd — OCF Resource Agent compliant FTP script.
ocf:Raid1 — RAID1 resource agent
ocf:rsyncd — OCF Resource Agent compliant rsync daemon script.
ocf:SAPDatabase — SAP database resource agent
ocf:SAPInstance — SAP instance resource agent
ocf:SendArp — SendArp resource agent
ocf:ServeRAID — ServeRAID resource agent
ocf:SphinxSearchDaemon — searchd resource agent
ocf:Stateful — Example stateful resource agent
ocf:SysInfo — SysInfo resource agent
ocf:tomcat — tomcat resource agent
ocf:VIPArip — Virtual IP Address by RIP2 protocol
ocf:WAS6 — WAS6 resource agent
ocf:WAS — WAS resource agent
ocf:WinPopup — WinPopup resource agent
ocf:Xen — Manages Xen DomUs
ocf:Xinetd — Xinetd resource agent

Terminology

List of Figures

1.1. Three-Server Cluster
1.2. Three-Server Cluster after One Server Fails
1.3. Typical Fibre Channel Cluster Configuration
1.4. Typical iSCSI Cluster Configuration
1.5. Typical Cluster Configuration Without Shared Storage
1.6. Heartbeat Architecture
2.1. Node Configuration
2.2. Authentication Keys
2.3. Media Configuration
2.4. Startup Configuration
4.1. Group Resource

List of Examples

5.1. Structure of an Empty Configuration