On Mon, 2017-09-11 at 23:38 +0100, J Martin Rushton wrote: > I've had it switched off over the last week whilst I've been trying to > sort this out, but forgot tonight. It must be the combination of > setting multicast_querier and stopping the firewall that is needed. I
FYI this should open the requisite ports: firewall-cmd --permanent --add-service=high-availability firewall-cmd --reload You may need to tweak that if your cluster network is not in the default zone. > can now see: > > Quorum information > ------------------ > Date: Mon Sep 11 23:20:15 2017 > Quorum provider: corosync_votequorum > Nodes: 4 > Node ID: 1 > Ring ID: 1/31156 > Quorate: Yes > > Votequorum information > ---------------------- > Expected votes: 4 > Highest expected: 4 > Total votes: 4 > Quorum: 3 > Flags: Quorate > > Membership information > ---------------------- > Nodeid Votes Name > 1 1 192.168.1.2 (local) > 2 1 192.168.1.51 > 3 1 192.168.1.52 > 4 1 192.168.1.53 > > which is what I wanted. > > Thank you very much, I can go on to build the filesystem now. > Martin > > On 11/09/17 23:14, Leon Steffens wrote: > > Is the firewalld service running? Just did a quick test on my Centos 7 > > installation and by default SSH is allowed through the firewall, but > > corosync cannot connect to the other nodes. > > > > Try: systemctl stop firewalld.service > > _______________________________________________ > Users mailing list: Users@clusterlabs.org > http://lists.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 -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.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