[ClusterLabs] Pacemaker connectivity loss to ISP

S0ke s0ke at protonmail.com
Thu Mar 24 17:18:50 EDT 2016

Ended up setting up 2 static routes and then using those as the ips designated in the ocf:ping host_list. Works like a charm.

-------- Original Message --------
Subject: Pacemaker connectivity loss to ISP
Local Time: March 24, 2016 12:12 PM
UTC Time: March 24, 2016 5:12 PM
From: s0ke at protonmail.com
To: users at clusterlabs.org

So I'm trying to figure out the best method to accomplish this. We have a 2 node cluster. We have multiple WANs connected to 2 different ISPs. Generally everything is forced out eth0, eth1 is the backup.


| | | |
| | | |
eth0 eth1 eth0 eth1
-------------- -----------
| HA1 | | HA2 |
-------------- ----------
So in this scenario if eth0 loses connectivity to its upstream router/gateway we want it to failover to ha2. I tried this by using the ethmonitor type but it seems to only work if the cable is pulled from the actual interface itself or the swithport is shutdown. We want it to failover if it's unable to ping out to to web through eth0. So if connectivity is lost on the actual modem/gateway it will failover. I looked at using ocf:ping but it doesn't seem to allow me to specify an interface to use. What would be the best method to do this ocf:ping or heartbeat:ethmonitor?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160324/e8460208/attachment-0003.html>

More information about the Users mailing list