<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10pt" ><div dir="ltr" >Hi , thanks for the quick reply.</div>
<div dir="ltr" >I have a couple of follow up questions below in <span style="color:#0000cd;" >blue below</span></div>
<div dir="ltr" >
<blockquote data-history-content-modified="1" data-history-expanded="1" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" ><div><font size="2" face="Default Monospace,Courier New,Courier,monospace" >On 12/07/2021 23:27, Kiril Pashin wrote:<br>> Hi ,<br>> is it valid to use the same network adapter interface on the same host to be<br>> part of multiple<br>> heart beat rings ?<br><br>There should be no problem from technical side, but I wouldn't call this<br>use case "valid". Idea of multiple rings is to have multiple independent<br>connections between nodes - something what one nic simply doesn't provide.</font><br> </div>
<div><br><font size="2" face="Default Monospace,Courier New,Courier,monospace" >> The scenario is hostA has eth0 ( ip 192.10.10.1 ) interface and hostB has eth0 (<br>> 192.20.20.1 ) and eth1 ( 192.20.20.2 ) .<br><br>This is unsupported configuration</font><br> </div>
<div><span style="color:#0000ff;" >Can you clarify here why this is unsupported, you mentioned above that there should be no problem from a technical side ?</span></div>
<div><br><font size="2" face="Default Monospace,Courier New,Courier,monospace" >> Are there any restrictions to form two heartbeat rings { eth0, eth0 } and {<br>> eth0, eth1 }<br><br>Technically only restriction is based on IP. But to make it reliable one<br>should use multiple NICs with multiple links and multiple switches.</font></div></blockquote>
<div><span style="color:#0000ff;" >I understand that its not as reliable as using multiple NICs, you mention the only restriction is based on IP . Is there a doc</span></div>
<div><span style="color:#0000ff;" >mentioning such restrictions ?</span></div>
<blockquote class="history-quote-1626195248393" data-history-content-modified="1" data-history-expanded="1" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" ><div><br><font size="2" face="Default Monospace,Courier New,Courier,monospace" >> as well as create a nozzle device to be able to ping hostA in case eth0 or eth1<br>> go down on hostB<br><br>It is definitively possible to create noozle device which will allow to<br>ping hostA in case some of nic fails, but not in the way described in<br>config snip. Noozle device should have different IP subnet (noozle is<br>basically yet another network card).</font></div>
<div> </div>
<div><span style="color:#0000ff;" >I made up the example in this<font size="2" face="Default Monospace,Courier New,Courier,monospace" > </font>email, however , i assumed all the IPs in the examle are<br>are using 24 bits for the subnet netmask<font size="2" face="Default Monospace,Courier New,Courier,monospace" > </font>so the nozzle is on a different subnet 192.168.10</span></div>
<div><span style="color:#0000ff;" >Can you clarify the problem with my config snip ?</span></div>
<div><br><font size="2" face="Default Monospace,Courier New,Courier,monospace" >> nodelist {<br>> node {<br>> ring0_addr: 192.10.10.1<br>> ring1_addr: 192.10.10.1<br>> name: node1<br>> nodeid: 1<br>> }<br>> node {<br>> ring0_addr: 192.20.20.1<br>> ring1_addr: 192.20.20.2<br>> name: node2<br>> nodeid: 2<br>> }<br>> }<br>> nozzle {<br>> name: noz01<br>> ipaddr: 192.168.10.0<br>> ipprefix: 24<br>> }<br><br>This config will definitively not work.</font><br><br><font size="2" face="Default Monospace,Courier New,Courier,monospace" >Regards,<br> Honza<br><br>> Thanks,<br>> Kiril Pashin<br>> DB2 Purescale Development & Support<br>> kirilp@ca.ibm.com<br>><br>><br>><br>> _______________________________________________<br>> Manage your subscription:<br>> <a href="https://lists.clusterlabs.org/mailman/listinfo/users" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a> <br>><br>> ClusterLabs home: <a href="https://www.clusterlabs.org/" target="_blank">https://www.clusterlabs.org/</a> <br>> </font></div></blockquote>
<div> </div></div></div><BR>
<BR>