This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag

Homepage

About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.
To get rid of this notice, you may want to browse the old wiki instead.

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2017-12-13 14:47:08

ipfail

ipfail is an add-on designed to interface with Linux-HA. It uses the Linux-HA API to communicate with the nodes in the cluster. The default setup of Linux-HA will not failover resources simply if an interface goes down. This is a reasonable scenario for many HA setups, however it is not acceptable in other instances, particularly when dealing with firewall pairs. If an interface goes down, or the network behind it is no longer reachable due to some other hardware failure, the resource holder must relinquish control to the backup, who will be able to take up the role as the primary. ipfail handles this by watching special ping nodes. If a ping node is detected to have failed, ipfail will contact the other cluster member to see if it has better connectivity. If it does, then we can be reasonably sure that an interface/network connection has died and that we should failover our resources if we have any.

ipfail can now work with auto_failback, as of the 1.1.4 release of Heartbeat. This allows a user to create active/active clusters and still use ipfail.

Note that ipfail needs redundant communications media to work correctly - because it won't cause a failover on its own unless it can contact the other cluster member. In other words, if you're pinging on the same media as the only heartbeat channel configured, you're destined to be disappointed in ipfail.

Read how to configure ipfail.

For V2 style clusters you will have to look into pingd instead.

ipfail is primarily the fault of KevinDwyer.