<div dir="ltr">Thanks!</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 20, 2014 at 12:29 AM, Jan Friesse <span dir="ltr"><<a href="mailto:jfriesse@redhat.com" target="_blank">jfriesse@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Aaron Wilson napsal(a):<br>
<div class="">> Stefan, thanks for the reply.<br>
><br>
> Having two nics is not for redundancy in my case. Resources on the primary<br>
> server are being accessed from both subnets at the same time. The secondary<br>
> server is to be a failover if the server goes down or if any of the<br>
> Ethernet ports become disconnected for any reason. I read through the<br>
> documentation and I am still not sure of the relationship between the<br>
> Corosync hostnames / interfaces and Pacemaker resources. Could corosync be<br>
> configured to detect failure and start failover of a node using rrp or does<br>
> the resource need to be monitored by Pacemaker in order to get moved form<br>
> primary to secondary server?<br>
><br>
<br>
</div>Corosync itself doesn't take any visible action when one of rings failed<br>
(it just keeps sending messages via another ring). RRP is there only for<br>
redundancy and it's intended to be invisible for corosync clients<br>
(Pacemaker included). Everything resource management related is<br>
Pacemaker job.<br>
<div class="im HOEnZb"><br>
> There is actually a third nic on the servers which could be used only for<br>
> 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>
><br>
><br>
><br>
</div><div class="HOEnZb"><div class="h5">> _______________________________________________<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>
><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>