<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2014-11-26 13:22 GMT+01:00 Keith Ouellette <span dir="ltr"><<a href="mailto:KeithO@fibermountain.com" target="_blank">KeithO@fibermountain.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Anne,<br>
<br>
Are you expecting the eth0 to actually put in the "down" state like using the "ifconfig eth0 down" command? If so the IPaddr2 resource does not do that. What that is used for is to configure a second IP address on the NIC that can be moved around from "eth0" on each node. Can you clearify that? Also, can you paste the output of the "ip addr" command as well? The full configuration of "crm configure show" would also be helpful<br></blockquote><div><br></div><div>Maybe I've misunderstood documentation but just reused <a href="http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Clusters_from_Scratch/#_perform_a_failover">http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Clusters_from_Scratch/#_perform_a_failover</a></div><div> It seemed to work at the beginning as expected.</div><div><br></div><div>I've sent some minutes ago my full configuration</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Thanks,<br>
Keith<br>
<br>
<br>
<br>
Keith Ouellette<br>
<br>
<a href="mailto:KeithO@fibermountain.com">KeithO@fibermountain.com</a><br>
700 West Johnson Avenue<br>
Cheshire, CT06410<br>
<a href="http://www.fibermountain.com" target="_blank">www.fibermountain.com</a><br>
P. <a href="tel:%28203%29%20806-4046" value="+12038064046">(203) 806-4046</a><br>
C. <a href="tel:%28860%29%20810-4877" value="+18608104877">(860) 810-4877</a><br>
F. <a href="tel:%28845%29%20358-7882" value="+18453587882">(845) 358-7882</a><br>
<br>
Disclaimer: The information contained in this communication is confidential, may be privileged and is intended for the exclusive use of the above named addressee(s). If you are not the intended recipient(s), you are expressly prohibited from copying, distributing, disseminating, or in any other way using any information contained within this communication. If you have received this communication in error, please contact the sender by telephone or by response via mail. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on this message, as well as any attachments. We cannot accept liability for any loss or damage caused by software viruses.<br>
<span class="im"><br>
-----Original Message-----<br>
From: Anne Nicolas [mailto:<a href="mailto:ennael1@gmail.com">ennael1@gmail.com</a>]<br>
Sent: Wednesday, November 26, 2014 6:54 AM<br>
To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
Subject: Re: [Pacemaker] Problem with ClusterIP<br>
<br>
Le 26/11/2014 12:23, Michael Schwartzkopff a écrit :<br>
> Am Mittwoch, 26. November 2014, 12:01:36 schrieb Anne Nicolas:<br>
>> Hi !<br>
>><br>
>> I've been using clusterip for a while now without any problem in<br>
>> Active/Passive clusters (2 nodes).<br>
><br>
> Could you please explain, how could you use the ClusterIP in a<br>
</span><div class=""><div class="h5">> active/passive cluster? ClusterIP ist for the use in an active/active<br>
> cluster. See man iptables and look for the CLUSTERIP target.<br>
<br>
><br>
> Please explain more detailed.<br>
> What is your config?<br>
> What do you expect the cluster to do?<br>
> What really happens?<br>
> Where is the problem?<br>
<br>
Maybe my explanation was not that clear. Here is my configuration<br>
<br>
crm configuration show<br>
<br>
node $id="17435146" pogcupsvr<br>
node $id="34212362" pogcupsvr2<br>
primitive apache ocf:heartbeat:apache \<br>
params configfile="/etc/httpd/conf/httpd.conf" \<br>
op start interval="0" timeout="40s" \<br>
op stop interval="0" timeout="60s"<br>
primitive clusterip ocf:heartbeat:IPaddr2 \<br>
params ip="172.16.16.11" cidr_netmask="24" nic="eth0" \<br>
meta target-role="Started"<br>
...<br>
property $id="cib-bootstrap-options" \<br>
<br>
dc-version="1.1.7-2.mga1-ee0730e13d124c3d58f00016c3376a1de5323cff" \<br>
cluster-infrastructure="corosync" \<br>
stonith-enabled="false" \<br>
no-quorum-policy="ignore"<br>
rsc_defaults $id="rsc-options" \<br>
resource-stickiness="100"<br>
<br>
So I've started primary node (pogcupsvr). Configuration was checked and ok. Then started the second node (pogcupsvr2). This time all the configuration looked ok, no error but when I checked the network configuration, eth0 was up on both nodes with same IP address of course, instead of having it up only on primary node.<br>
<br>
What I was expected (and in all other tests it was ok ) is that eth0 was up only on primary node and used by apache server.<br>
><br>
>> I'm looking for ideas to investigate the causes for such a problem.<br>
>> If anybody can help me on this, I would be gratefull<br>
><br>
> Yes, I think I can help ;-)<br>
<br>
Thanks for that :)<br>
><br>
><br>
> Mit freundlichen Grüßen,<br>
><br>
> Michael Schwartzkopff<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> Getting started:<br>
> <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>
Anne<br>
<a href="http://mageia.org" target="_blank">http://mageia.org</a><br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a> <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> 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>
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 class="gmail_signature">Anne<br><a href="http://www.mageia.org" target="_blank">http://www.mageia.org</a><br></div>
</div></div>