----- Original Message ----- 

> From: "M Siddiqui" <msiddi...@live.com.pk>
> To: "The Pacemaker cluster resource manager"
> <pacemaker@oss.clusterlabs.org>
> Sent: Tuesday, January 24, 2012 12:47:18 PM
> Subject: [Pacemaker] HA Cluster Connected over VPN

> Hi there,

> I have a situation where two cluster nodes are connected over the
> VPN; each node
> is configured with two interfaces to provide ring redundancy for
> corosync:

> NODE1:
> eth1: 192.168.1.111/24
> eth2: 192.168.1.112/24

> NODE2:
> eth1: 192.168.1.113/24
> eth2: 192.168.1.114/24

> Since two nodes are geographically distributed and connected over the
> VPN,
> configuring each interface in a different subnet is not an option
> here.

> Now corosync got confused due to same subnet; how we can handle this
> situation?
> What is the experts recommendation? Thanks in advance for the answer.

Not an expert but could you bond the two Ethernet interfaces and just present 
the single bonded interface to corosync?  Then the bond could handle single 
link failure outside of corosync

HTH

Jake

> kind regards,
> mumtaz
> _______________________________________________
> Pacemaker mailing list: Pacemaker@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

_______________________________________________
Pacemaker mailing list: Pacemaker@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

Reply via email to