0

I need to setup a heartbeat with pacemaker based on debian OS where the active server virtual IP is 192.168.1.10 and the passive server virtual IP is 192.168.1.11. Both of the server is connected to a cisco ethernet switch. My question is, do setup the heartbeat for the 2 servers, do i need 2 more separate virtual IP for heartbeat or can I use 192.168.1.10 and 192.168.1.11 for the heartbeat configuration to listen for the servers?

Improve this question

1 Answer 1

Reset to default
0

You should use a dedicated NIC for heartbeat and maybe (depends on your needs) sync the data using DRBD. A good start point is in Debian Clusters From Scratch.
Please, read the Debian-HA FAQ too.
And for a DRBD howto, read this.

Improve this answer
2
  • Thanks for the guidance. If the setup were to be done using a dedicated NIC which connect to a separate network, I know that it could be a problem if a fault happened on the main network (ex: server 1 to switch connection broken). In this case, the heartbeat will not switch over to server 2 as the heartbeat is still alive. I did some googling, which I know this can be resolve using pacemaker pingd. My question would be, will it be an issue if i were to stick with 1 NIC instead of having a dedicated NIC, such as package lost on a 1Gbps network?
    – John
    Nov 3, 2015 at 9:06
  • IMHO, could generate a performance issue. If some user flood the chanel, the slave could stop seeing the master and create a split-brain situation.
    – Jose Raul Barreras
    Nov 3, 2015 at 13:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .