Saturday, 29 October 2011

Heartbeat failure recovery system help

Heartbeat failure recovery system help

I`m trying to implement a failure recovery system for our network firewalls. In theory the idea is if one fails the other one should be able of taking over and when the master firewall comes back up online, the slave should yield its place.

I`m hoping heartbeat is the answer.

Now in practice I`m experimenting with two test systems each running FC 14 minimal install with 2 NIC`s before implementing this on the production network.

I`m trying to setup heartbeat on 2 test machines running FC 14 minimal install with 2 NIC`s

The second host should be ready to take over if host 1 is down and take it`s ip address

My test machines have the following network config

eth0 - eth0 cross cable between them with internal ip`s 10.10.0.1/24 and 10.10.0.2/24

eth2 is connected to the router 192.168.200.x

I`ve been reading fwbuilder.org/4.0/docs/users_guide/heartbeat_cluster.html however it`s not exacly what i want.

My config files:

/etc/ha.d/authkeys
auth 2
2 sha1 test


/etc/ha.d/ha.cf
logfile /var/log/ha-log
logfacility local0
keepalive 2
deadtime 30
initdead 120
udpport 694
bcast eth0
auto_failback on
node TEST1
node TEST2

haresources
TEST1 IPaddr::10.10.0.3

So this creates a virtual NIC with the address of 10.10.0.3, but i want TEST2 to take over TEST1`s ip.

How can i acheive that? Or can anyone suggest a better option than heartbeat for what i`m trying to do?

No comments:

Post a Comment