Attachment 47029 Details for Bug 75341 – Gentoo Heartbeat HOWTO

Gentoo Heartbeat HOWTO

heartbeat-howto.xml (text/plain), 4.65 KB, created by Sven Vermeulen (RETIRED) on 2004-12-28 07:26:19 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Sven Vermeulen (RETIRED)

Created: 2004-12-28 07:26:19 UTC

Size: 4.65 KB

patch

obsolete

><?xml version='1.0' encoding='UTF-8'?>
>
>
>
><!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
>
><guide link="heartbeat-howto.xml">
><title>Gentoo Heartbeat HOWTO</title>
>
><author title="Author">
>  <mail link="iggy@gentoo.org">Brian Jackson</mail>
></author>
>
><abstract>
>With heartbeat systems can detect if another system is down and take appropriate
>action (such as taking over the service that ran on the other system). This
>HOWTO covers the installation and configuration of heartbeat on a Gentoo system.
></abstract>
>
>
>
><license/>
>
><version>1.0</version>
><date>2004-12-28</date>
>
><chapter>
><title>Introduction</title>
><section>
><title>What is Heartbeat?</title>
><body>
>
><p>
>Heartbeat takes care of dead node detection, and service/resource migration.
>Heartbeat clusters can be ridiculously simple or complex. We will cover setting
>up a simple cluster. To learn more about heartbeat, and how to setup even more
>complex setups see the <uri link="http://www.linux-ha.org/">Linux-HA
>Website</uri>.
></p>
>
></body>
></section>
></chapter>
>
><chapter>
><title>Getting Heartbeat to Work</title>
><section>
><title>Installation</title>
><body>
>
><p>
>I this HOWTO we are assuming that you have 2 nodes (cluster1 and cluster2) with
>ip addresses (192.168.0.1 and 192.168.0.2 respectively), and you will have one
>cluster ip (192.168.0.5).
></p>
>
><p>
>To install heartbeat, just use <c>emerge heartbeat</c>:
></p>
>
><pre caption="Installing Heartbeat">
># <i>emerge heartbeat</i>
></pre>
>
><p>
>This should complete without any problems, but if there are any report them via
><uri link="http://bugs.gentoo.org">bugzilla</uri>.
></p>
>
></body>
></section>
><section>
><title>Configuration</title>
><body>
>
><p>
>Edit <path>ha.cf</path>. You need at least the following settings:
></p>
>
><pre caption="ha.cf">
>bcast eth0
>keepalive 2
>warntime 10
>deadtime 30
>auto_failback off
>node cluster1
>node cluster2
></pre>
>
><p>
>if you are going to be using a serial cable as a heartbeat transport, add the
>following settings as well:
></p>
>
><pre caption="ha.cf, continued">
>serial /dev/ttyS0
>baud 19200
></pre>
>
><p>
>Now what do these settings mean?
></p>
>
><table>
><tr>
>  <th>Setting</th>
>  <th>Description</th>
></tr>
><tr>
>  <ti>bcast</ti>
>  <ti>send broadcast heartbeats on the device</ti>
></tr>
><tr>
>  <ti>keepalive</ti>
>  <ti>time between heartbeats (in seconds)</ti>
></tr>
><tr>
>  <ti>warntime</ti>
>  <ti>time before a warning is logged (in seconds)</ti>
></tr>
><tr>
>  <ti>deadtime</ti>
>  <ti>time before a node is declared dead (in seconds), and recovery starts</ti>
></tr>
><tr>
>  <ti>auto_failback</ti>
>  <ti>
>    on=resources are reclaimed by original node, off= resources are not 
>    reclaimed by original node
>  </ti>
></tr>
><tr>
>  <ti>node</ti>
>  <ti>uname -n of each node (i.e. you should have multiple node settings)</ti>
></tr>
><tr>
>  <ti>serial</ti>
>  <ti>device connected to other machine</ti>
></tr>
><tr>
>  <ti>baud</ti>
>  <ti>baud rate of serial device connected to other node</ti>
></tr>
></table>
>
><p>
>Other possible settings are:
></p>
>
><table>
><tr>
>  <th>Setting</th>
>  <th>Description</th>
></tr>
><tr>
>  <ti>ucast</ti>
>  <ti>
>    send unicast heartbeats to the ip of the other machine on the device.
>    Syntax: <c>ucast [dev] [ip of other node]</c>
>  </ti>
></tr>
><tr>
>  <ti>mcast</ti>
>  <ti>
>    use multicast to send heartbeats to other cluster members.
>    Syntax: <c>mcast [dev] [mcast group] [port] [ttl] [loop]</c>
>  </ti>
></tr>
></table>
>
><p>
>Now edit <path>haresources</path>. 
></p>
>
><note>
><path>haresources</path> must be identical on all cluster nodes.
></note>
>
><p>
>You only need the following line (edit nodenames/IP addresses accordingly):
></p>
>
><pre caption="haresources">
>cluster1 192.168.0.5
></pre>
>
><p>
>This will give you an IP that moves to cluster2 when cluster1 dies.
></p>
>
></body>
></section>
><section>
><title>Configuring the AuthKeys</title>
><body>
>
><p>
>Edit the <path>authkeys</path> file and add the following two lines:
></p>
>
><pre caption="authkeys">
>1 sha1 key-for-sha1-any-text-you-want
></pre>
>
></body>
></section>
><section>
><title>Starting HeartBeat</title>
><body>
>
><pre caption="Starting heartbeat">
># <i>/etc/init.d/heartbeat start</i>
></pre>
>
></body>
></section>
><section>
><title>Testing HeartBeat</title>
><body>
>
><p>
>You can pull the plug on cluster1 to test failover, or you can just shutdown
>heartbeat on cluster1, and watch as your cluster ip migrates to the other node.
></p>
>
></body>
></section>
></chapter>
><chapter>
><title>Resources</title>
><section>
><body>
>
><ul>
>  <li>
>    <uri link="http://www.linux-ha.org/download/GettingStarted.html">Getting
>    Started with Linux-HA</uri>
>  </li>
></ul>
>
></body>
></section>
></chapter>
>
></guide>

Actions: View

Attachments on bug 75341: 47028 | 47029 | 47030