JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide
search filter icon
search icon

Document Information

Preface

1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

Introduction to Heartbeats

Creating a Heartbeat

How to Create a Heartbeat

Creating a Heartbeat Plug-in

How to Create Heartbeat Plug-in

Modifying a Heartbeat Plug-in Property

How to Modify the Properties of a Heartbeat Plug-in

Deleting Heartbeats and Heartbeat Plug-ins

How to Delete a Heartbeat

How to Delete a Plug-in From a Heartbeat

Displaying Heartbeat Configuration Information

How to Display Heartbeat Configuration Information

Tuning the Heartbeat Properties

How to Modify the Heartbeat Properties

Creating a Heartbeat That Uses a Custom Heartbeat Plug-in

Creating a Custom Heartbeat Plug-in

How to Add a Custom Heartbeat Plug-in to an Existing Default Heartbeat

How to Create a Custom Heartbeat Plug-in and Add It to a Custom Heartbeat

Configuring Heartbeat-Loss Notification

Configuring the Heartbeat-Loss Notification Properties

Creating an Action Shell Script for Heartbeat-Loss

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Deployment Example: Replicating Data With MySQL

G.  Error Return Codes for Script-Based Plug-Ins

Index

Introduction to Heartbeats

A heartbeat in Geographic Edition is a container for a collection of heartbeat plug-ins. A heartbeat has a name and one property that you can tune, Query_interval. The Query_interval property specifies the delay between heartbeat status requests.

The heartbeat plug-in facilitates the actual physical monitoring activity. The plug-in is defined by a required query command or query library, an optional requester and responder agent, a type, and a Plugin_properties string.

The Geographic Edition product provides the following default plug-ins:

A default heartbeat that uses the default heartbeat plug-ins is created every time you run geops create or geops join without specifying a custom heartbeat. The name of the default heartbeat is hb_localclustername~remoteclustername. For more information about the geops command, refer to the geops(1M) man page.

You can create custom heartbeat plug-ins and associate them with existing default heartbeats or with new custom heartbeats.


Note - Custom heartbeats are provided for special circumstances and require careful configuration. Consult your Sun specialist for assistance if your system requires the use of custom heartbeats.

If you create a custom heartbeat, you must add at least one plug-in to prevent the partnership from remaining in degraded mode.