<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10pt" ><div dir="ltr" >To clarify my problem, this is more on Qdevice issue I want to fix.</div>
<div dir="ltr" >See below for more detail.</div>
<div dir="ltr" > </div>
<div dir="ltr" >Thank you,</div>
<div dir="ltr" >Richard</div>
<div dir="ltr" > </div>
<blockquote data-history-content-modified="1" data-history-expanded="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: Andrei Borzenkov <arvidjaar@gmail.com><br>Sent by: "Users" <users-bounces@clusterlabs.org><br>To: users@clusterlabs.org<br>Cc:<br>Subject: [EXTERNAL] Re: [ClusterLabs] Two ethernet adapter within same subnet causing issue on Qdevice<br>Date: Thu, Oct 1, 2020 2:45 PM<br>
<div><font face="Default Monospace,Courier New,Courier,monospace" size="2" >01.10.2020 20:09, Richard Seo пишет:<br>> Hello everyone,<br>> I'm trying to setup a cluster with two hosts:<br>> both have two ethernet adapters all within the same subnet.<br>> I've created resources for an adapter for each hosts.<br>> Here is the example:<br>> Stack: corosync<br>> Current DC: <host 1> (version 2.0.2-1.el8-744a30d655) - partition with quorum<br>> Last updated: Thu Oct 1 12:50:48 2020<br>> Last change: Thu Oct 1 12:32:53 2020 by root via cibadmin on <host 1><br>> 2 nodes configured<br>> 2 resources configured<br>> Online: [ <host1> <host2> ]<br>> Active resources:<br>> db2_<host1>_ens192 (ocf::heartbeat:db2ethmon): Started <host1><br>> db2_<host2>_ens192 (ocf::heartbeat:db2ethmon): Started <host2><br>> I also have a qdevice setup:<br>> # corosync-qnetd-tool -l<br>> Cluster "hadom":<br>> Algorithm: LMS<br>> Tie-breaker: Node with lowest node ID<br>> Node ID 2:<br>> Client address: ::ffff:<ip for ens192 for host 2>:40044<br>> Configured node list: 1, 2<br>> Membership node list: 1, 2<br>> Vote: ACK (ACK)<br>> Node ID 1:<br>> Client address: ::ffff:<*ip for ens192 for host 1*>:37906<br>> Configured node list: 1, 2<br>> Membership node list: 1, 2<br>> Vote: ACK (ACK)<br>> When I ifconfig down ens192 for host 1, looks like qdevice changes the Client<br>> address to the other adapter and still give quorum to the lowest node ID (which<br>> is host 1 in this case) even when the network is down for host 1.<br><br>Network on host 1 is obviously not down as this host continues to<br>communicate with the outside world. Network may be down for your<br>specific application but then it is up to resource agent for this<br>application to detect it and initiate failover.</font></div>
<div> </div>
<div>The Network (ens192) on host 1 is down. host1 can still communicate with the world, because host1 has another network adapter (ens256). However, only ens192 was configured as a resource. I've also configured specifically ens192 ip address in the corsync.conf. </div>
<div><font face="Default Monospace,Courier New,Courier,monospace" size="2" ><span style="font-family:Arial,Helvetica,sans-serif;" >I want the network on host 1 down. that way, I can reproduce the problem where quorum is given to a wrong node.</span><br><br>> Cluster "hadom":<br>> Algorithm: LMS<br>> Tie-breaker: Node with lowest node ID<br>> Node ID 2:<br>> Client address: ::ffff:<ip for ens192 for host 2>:40044<br>> Configured node list: 1, 2<br>> Membership node list: 1, 2<br>> Vote: ACK (ACK)<br>> Node ID 1:<br>> Client address: ::ffff:<*ip for ens256 for host 1*>:37906<br>> Configured node list: 1, 2<br>> Membership node list: 1, 2<br>> Vote: ACK (ACK)<br>> Is there a way we can force qdevice to only route through a specified adapter<br>> (ens192 in this case)?<br><br>Create host route via specific device.</font></div>
<div> </div>
<div><font size="2" >I've looked over the docs, haven't found a way to do this. I've tried configuring corosync.conf using the specific ip addresses. Could you specify how to route to a specific network adapter from a qdevice? <br><br><font face="Default Monospace, Courier New, Courier, monospace" >> Also while I'm on this topic, is multiple communication ring support with</font><br><font face="Default Monospace, Courier New, Courier, monospace" >> pacemaker supported or will be supported in the near future?</font><br><br><font face="Default Monospace, Courier New, Courier, monospace" >What exactly do you mean? What communication are you talking about?</font><br><br><font face="Default Monospace, Courier New, Courier, monospace" >You seem to confuse multiple layers here. qnetd and pacemaker are two</font><br><font face="Default Monospace, Courier New, Courier, monospace" >independent things.</font></font></div>
<div> </div>
<div><font size="2" >So this is a separate question regarding Pacemaker and Corosync. I want to know if having multiple communication ring in the nodelist in corosync.conf is supported by Pacemaker with Corosync right now. The communication protocal is called Redundant ring protocol.</font></div>
<div><br><font size="2" ><font face="Default Monospace, Courier New, Courier, monospace" >_______________________________________________</font><br><font face="Default Monospace, Courier New, Courier, monospace" >Manage your subscription:</font><br><a href="https://lists.clusterlabs.org/mailman/listinfo/users" style="font-family: "Default Monospace", "Courier New", Courier, monospace;" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><font face="Default Monospace, Courier New, Courier, monospace" > </font><br><br><font face="Default Monospace, Courier New, Courier, monospace" >ClusterLabs home: </font><a href="https://www.clusterlabs.org/" style="font-family: "Default Monospace", "Courier New", Courier, monospace;" target="_blank">https://www.clusterlabs.org/</a><font face="Default Monospace, Courier New, Courier, monospace" > </font></font><br> </div></blockquote>
<div dir="ltr" > </div></div><BR>