If firewalld is available, just try with 'firewall-cmd --panic-on' (or
something like that).
Best Regards,Strahil Nikolov
On Fri, Mar 19, 2021 at 12:50, Marcelo Terres wrote:
___
Manage your subscription:
Hello Jan.
Thank you very much for your help, It was definitely related to the way I
was blocking the packets.
Since I'm running these tests with VMs, I just paused node1 and then node2
got the IP after a few seconds.
About the issues in the documentation: I'll recreate the scenario from
Marcelo,
Hello.
I have configured corosync with 2 nodes and added a qdevice to help with
the quorum.
On node1 I added firewall rules to block connections from node2 and the
qdevice, trying to simulate a network issue.
Just please make sure to block both incoming and also outgoing packets.
Is there any reason to use lms mode for the qdevice ?
Best Regards,
Strahil Nikolov
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
Hello.
I have configured corosync with 2 nodes and added a qdevice to help with
the quorum.
On node1 I added firewall rules to block connections from node2 and the
qdevice, trying to simulate a network issue.
The problem I'm having is that one node1 I can see it dropping the
service (the IP),
Hello.
I have configured corosync with 2 nodes and added a qdevice to help with
the quorum.
On node1 I added firewall rules to block connections from node2 and the
qdevice, trying to simulate a network issue.
The problem I'm having is that one node1 I can see it dropping the
service (the IP),
