Difference between revisions of "Set up a heartbeat cluster"

From Linuxintro
imported>ThorstenStaerk
imported>ThorstenStaerk
Line 18: Line 18:
 
  heartbeat-1:~ # scp /etc/ha.d/ha.cf root@heartbeat-2:/etc/ha.d
 
  heartbeat-1:~ # scp /etc/ha.d/ha.cf root@heartbeat-2:/etc/ha.d
 
  heartbeat-1:~ # scp /etc/ha.d/authkeys root@heartbeat-2:/etc/ha.d
 
  heartbeat-1:~ # scp /etc/ha.d/authkeys root@heartbeat-2:/etc/ha.d
 +
* start the cluster
 +
heartbeat-1:~ # /etc/init.d/heartbeat start
 +
heartbeat-2:~ # /etc/init.d/heartbeat start

Revision as of 10:06, 7 May 2009

OK, I am trying to set up a heartbeat cluster with SUSE Linux here. I have 3 machines:

  • heartbeat-1, 192.168.0.21 (virtual)
  • heartbeat-2, 192.168.0.22 (virtual)
  • tweedleburg, 192.168.0.5 (physical)

On heartbeat-*, I install SLES 10 as per default, but I disable ZMD and the firewall. On tweedleburg, I install an iscsi storage. I want to install a highly available web server to gain some experience with clustering. We use heartbeat as cluster manager.

  • establish passwordless login between heartbeat-1 and -2.
  • adapt /etc/hosts on both nodes so that it contains
192.168.0.21    heartbeat-1.site heartbeat-1
192.168.0.22    heartbeat-2.site heartbeat-2
  • configure the cluster on node 1
heartbeat-1:~ # yast2 heartbeat

Choose MD5 as auth method and myauth as password.

  • install heartbeat on node 2
heartbeat-1:~ # yast -i heartbeat
  • propagate the heartbeat configuration
heartbeat-1:~ # scp /etc/ha.d/ha.cf root@heartbeat-2:/etc/ha.d
heartbeat-1:~ # scp /etc/ha.d/authkeys root@heartbeat-2:/etc/ha.d
  • start the cluster
heartbeat-1:~ # /etc/init.d/heartbeat start
heartbeat-2:~ # /etc/init.d/heartbeat start