0

I have a cluster with 2 Nodes running on different subnets. They both communicate but I have always one node offline

node 1 : mon0101 is online and mon0201 is offline
node 2 : mon0101 is offline and mon0201 is online

IP of node 1 is : 10.1.18.115 netmask 255.255.255.0 gateway 10.1.18.254
IP of node 2 is : 10.2.18.115 netmask 255.255.255.0 gateway 10.2.18.254
Nodes are distants and we use a vpn to communicate.

EDIT : the purpose of this configuration is a monitoring system in redundant distributed architecture. We have 2 Central Server collecting informations one in primary mode and the other in secondary mode. When the primary is dead, pacemaker/corosync do the job and we can keep activities alive. Servers are on two different place communicating by vpn.

EDIT 2 : As asked my conf files and some results :
My cluster.conf content
My pcs status result on node 1
My pcs status result on node 2
My cman_tool result on node 1
My cman_tool result on node 2
My pcs cluster status on node 1
My pcs cluster status on node 2

Multicast is enabled on my SonicWall both on firewall & VPN settings
If I use this config on node on the same networks everything run fine, both nodes are online and failover is a success.

  • 2
    Are you sure pacemaker/crm is connecting? Because if both of them show the other node as down, it seems in fact they are not communicating. What is the purpose of this setup? It seems errorprone, at minimum. – Lenniey Mar 29 '18 at 11:39
  • 1
    I agree with Lenniey, you shouldn't try stretching Pacemaker across distances/networks without understanding all the implications of doing so. Boothd (from SUSE) is something you might want to look into if you do intend to stretch your cluster across distances/networks. – Matt Kereczman Mar 30 '18 at 16:36
  • It's all the problem, when i try "service pacemaker status" on both node, it's listening, same thing for corosync, but they don't communicate across the network. – Philippe Delerm Apr 9 '18 at 13:21
  • If you really want to keep this setup, the configs and logs of both nodes would be helpful. Unicast, multicast, etc., all of these settings can be broken by a VPN. – Lenniey Apr 16 '18 at 14:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.