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: s...@protonmail.com
To: users@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.
ISP1 ISP2 ISP2 ISP1
| | | |
| | | |
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?
Thanks
_______________________________________________
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org