[Pacemaker] Trouble getting two node cluster to failover when network lost

[Stefan Bauer]

So you want to setup a ping ressource in each subnet. if your active node can not reach the ping node in one subnet, its an indication, that the node have lost its connectivity in that network.

Mit freundlichen Grüßen

Stefan Bauer
-- 
Cubewerk GmbH
Herzog-Otto-Straße 32
83308 Trostberg
08621 - 99 60 237
HRB 22195 AG Traunstein
GF Stefan Bauer

> Am 19.03.2014 um 21:29 schrieb "Aaron Wilson" <awilson at nautilusgrp.com>:
> 
> Stefan, thanks for the reply. 
> 
> Having two nics is not for redundancy in my case. Resources on the primary server are being accessed from both subnets at the same time. The secondary server is  to be a failover if the server goes down or if any of the Ethernet ports become disconnected for any reason.  I read through the documentation and I am still not sure of the relationship between the Corosync hostnames / interfaces and Pacemaker resources.  Could corosync be configured to detect failure and start failover of a node using rrp or does the resource need to be monitored by Pacemaker in order to get moved form primary to secondary server?  
> 
> There is actually a third nic on the servers which could be used only for cluster communication if that works better. 
> 
> 
> Thanks again for your input. I will do some more reading as well.
> 
> - Aaron
> _______________________________________________
> 
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> 
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> 
> 
> Project Home: http://www.clusterlabs.org
> 
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> 
> Bugs: http://bugs.clusterlabs.org
>