Heartbeat Configuration; Test Of The Ha Setup - Novell SLRS 8 Admin Manual

Table of Contents

Advertisement

5 Setting up Administration and Branch Servers
Change the primary node2 to node1 again with "drbdsetup /dev/nb0
secondary" on node2 and issue "drbdsetup /dev/nb0 primary" on node1
Delete the test data
You have now finished the preparation of DRBD.
5.3.6 Heartbeat Configuration
Adapt the configuration file templates delivered by SUSE:
File ha.cf: Change the entries node bs1 and node bs2 to match the
names of your servers given by "uname -n", for example, to node servername1.
File haresources: Change the entry
"bs1 192.168.2.3 datadisk::drbd0 Filesystem::/dev/nb0::/drbd::ext3"
Here, replace bs1 with the server name of your primary node and the
IP address with your service IP (the IP will change between the nodes
during failover). The service IP is probably out of the public network
range, 192.168.1.3 in this example.
File authkeys: No changes.
All three files must be copied to the directory /etc/ha.d/ on both nodes.

5.3.7 Test of the HA Setup

As a first test of your HA configuration, do the following:
Make sure that DRBD is started on both nodes with node1 as the primary
and that /dev/nb0 is not mounted.
Start Heartbeat first on node1 then on node2 with the command "rcheartbeat
start".
After some time, the service IP on node1 should be configured and
/dev/nb0 should be mounted on /drbd.
Issue "rcheartbeat stop" on node1. After some time, the service IP
and the mount of /dev/nb0 to /drbd should migrate to node2.
Now issue "rcheartbeat start" on node1 again. The service IP and
the mount should migrate from node2 to node1 again.
If this test is not working as expected, first check the connection of your dif-
ferent network cards. Further troubleshooting is out of the scope of this doc-
ument. Refer to the Heartbeat and DRBD manuals.
68

Advertisement

Table of Contents
loading

This manual is also suitable for:

Suse linux retail solution 8

Table of Contents