<div dir="ltr">OK, I tried the ping RA but my VIPs do not migrate when ping connection is lost. I placed my two VIPs in a group and I believe I must have something wrong with the scoring or location rules. Should I be using clone for the ping RA? <div>
<br></div><div>What is a good way to check is ping is failing or succeeding and if the scoring is happening correctly?</div><div><br></div><div>Below is my configuration and snippets from syslog</div><div><br></div><div>
<div>
ode baymaster-67</div><div>node baymaster-67-failover</div><div>primitive ip1 ocf:heartbeat:IPaddr2 \</div><div> params ip="192.168.67.81" nic="eth0" \</div><div> op monitor interval="2s"</div>
<div>primitive ip2 ocf:heartbeat:IPaddr2 \</div><div> params ip="192.168.200.1" nic="eth1" \</div><div> op monitor interval="2s"</div><div>primitive ping-nodes ocf:pacemaker:ping \</div>
<div> params host_list="192.168.67.80 192.168.200.100" multiplier="100" dampen="5s" \</div><div> op monitor interval="60" timeout="60" \</div><div> op start interval="0" timeout="60" \</div>
<div> op stop interval="0" timeout="60"</div><div>group baymaster-resources ip1 ip2</div><div>clone c_ping-nodes ping-nodes</div><div>location baymaster_ping baymaster-resources \</div><div> rule $id="ping_rule" inf: ping lte 0</div>
<div>location baymaster_vip baymaster-resources \</div><div> rule $id="ip_rule" inf: #uname eq baymaster-67</div><div>property $id="cib-bootstrap-options" \</div><div> dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \</div>
<div> cluster-infrastructure="cman" \</div><div> no-quorum-policy="ignore" \</div><div> stonith-enabled="false"</div></div><div><br></div><div>Should I be conserned about this line in syslog </div>
<div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 19, 2014 at 1:55 PM, Stefan Bauer <span dir="ltr"><<a href="mailto:stefan.bauer@cubewerk.de" target="_blank">stefan.bauer@cubewerk.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So you want to setup a ping ressource in each subnet. if your active node can not reach the ping node in one subnet, its an indication, that the node have lost its connectivity in that network.<br>
<br>
Mit freundlichen Grüßen<br>
<span class="HOEnZb"><font color="#888888"><br>
Stefan Bauer<br>
--<br>
Cubewerk GmbH<br>
Herzog-Otto-Straße 32<br>
83308 Trostberg<br>
08621 - 99 60 237<br>
HRB 22195 AG Traunstein<br>
GF Stefan Bauer<br>
<br>
> Am 19.03.2014 um 21:29 schrieb "Aaron Wilson" <<a href="mailto:awilson@nautilusgrp.com">awilson@nautilusgrp.com</a>>:<br>
</font></span><div class="HOEnZb"><div class="h5">><br>
> Stefan, thanks for the reply.<br>
><br>
> Having two nics is not for redundancy in my case. Resources on the primary server are being accessed from both subnets at the same time. The secondary server is to be a failover if the server goes down or if any of the Ethernet ports become disconnected for any reason. I read through the documentation and I am still not sure of the relationship between the Corosync hostnames / interfaces and Pacemaker resources. Could corosync be configured to detect failure and start failover of a node using rrp or does the resource need to be monitored by Pacemaker in order to get moved form primary to secondary server?<br>
><br>
> There is actually a third nic on the servers which could be used only for cluster communication if that works better.<br>
><br>
><br>
> Thanks again for your input. I will do some more reading as well.<br>
><br>
> - Aaron<br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
><br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
<br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><font color="#666666">Aaron Wilson | IT Manager</font><div><font color="#666666"><br></font><div><font color="#666666"><br></font></div>
</div><div><div><font color="#666666"><img src="http://www.nautilusgrp.com/wp-content/themes/nautilus2014/images/nautilus_logo.jpg" width="96" height="59"></font></div><div><span style="color:rgb(102,102,102)">Nautilus Group Inc.</span><font color="#666666"><br>
</font></div><div><a href="http://www.nautilusgrp.com/" style="color:rgb(17,85,204)" target="_blank">www.nautilusgrp.com</a><font color="#666666"><br></font></div><div><font color="#666666">2201 Dwight Way | Berkeley, CA 94704</font></div>
</div><div><div><span style="color:rgb(102,102,102)">M:</span><span style="color:rgb(102,102,102)"> <u>801.644.2533</u></span></div><div><br></div></div></div>
</div>