Hello,<br><br>Thanks for the reply. Let me rephrase my query regarding interface monitoring.<br>I have (say 3 IP interfaces) eth0, eth1, eth2.<br>Heartbeat is running on eth0.<br>I can monitor my eth0 link using Heartbeat but is there a possibility of monitoring eth1 and eth2 interfaces as well using Heartbeat mechanism?<br>
I need this to detect scenarios like if eth0 is working fine (thus, no break in cluster communication via Heartbeat) but there is some issue with either eth1 or eth2, I need to raise some alarms etc<br><br>Thanks and regards<br>
Neha Chatrath<br><br>Message: 4<br>
Date: Tue, 08 Nov 2011 09:45:17 +0100<br>
From: Florian Haas <<a href="mailto:florian@hastexo.com">florian@hastexo.com</a>><br>
To: The Pacemaker cluster resource manager<br>
<<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><div id=":14c">><br>
Subject: Re: [Pacemaker] Query regarding "crm node standby/online"<br>
command<br>
Message-ID: <<a href="mailto:4EB8EC1D.8050209@hastexo.com">4EB8EC1D.8050209@hastexo.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On 2011-11-08 06:22, neha chatrath wrote:<br>
> Hello,<br>
><br>
> I am running Heartbeat and Pacemaker in a cluster with 2 nodes.<br>
> I also have a client registered with Heartbeat daemon for any node/IF<br>
> status changes.<br>
<br>
Can you give more details as to the nature of that client?<br>
<br>
> When I execute "crm node standby" command on one of the nodes, there is<br>
> no node status change info reported to the client.<br>
> Is this the expected behavior?<br>
<br>
I would say yes, as putting a node in standby mode does not change its<br>
status of being a fully-fledged member of the cluster. It still<br>
participates in all cluster communications, it receives all<br>
configuration changes and status updates. It's merely ineligible for<br>
running any resources. So from the cluster communications layer point of<br>
view (i.e. from Heartbeat's or Corosync's perspective) nothing changes.<br>
<br>
> Also, one more query about Heartbeat daemon:<br>
> In my system, I have multiple IP interfaces (each configured with a<br>
> separate IP) with Heartbeat running on one of them.<br>
> I have a requirement of monitoring of all these IP interfaces and<br>
> perform necessary actions (like perform failover etc) in case of any<br>
> interface failure.<br>
<br>
Well there is no reason to do this externally. You set up fencing using<br>
an out-of-band fencing method. When cluster communications break down,<br>
you fence one node off the cluster, so resources fail over to the other.<br>
<br>
As a word of caution, it seems like you're at least headed into the<br>
direction of reinventing the wheel, and it also seems like you are<br>
trying to implement functionality that's already present in the stack.<br>
(This is just a hunch based on the limited information given, however.)<br>
If that is the case, I would strongly suggest you take a look at<br>
Clusters From Scratch and the Linux-HA User's Guide, and possibly also<br>
Pacemaker: Configuration Explained, to better familiarize yourself with<br>
the functionality of the stack.<br>
<br>
Hope this helps.<br>
Cheers,<br>
Florian<br>
</div><br><br><div class="gmail_quote">On Tue, Nov 8, 2011 at 10:52 AM, neha chatrath <span dir="ltr"><<a href="mailto:nehachatrath@gmail.com">nehachatrath@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<br><br>I am running Heartbeat and Pacemaker in a cluster with 2 nodes.<br>I also have a client registered with Heartbeat daemon for any node/IF status changes.<br><br>When I execute "crm node standby" command on one of the nodes, there is no node status change info reported to the client.<br>
Is this the expected behavior?<br clear="all"><br>Also, one more query about Heartbeat daemon:<br>In my system, I have multiple IP interfaces (each configured with a separate IP) with Heartbeat running on one of them.<br>
I have a requirement of monitoring of all these IP interfaces and perform necessary actions (like perform failover etc) in case of any interface failure.<br>I am able to monitor the interface on which Heartbeat is running but not the rest of them.<br>
Does Heartbeat allows monitoring of interfaces other than the interfaces on which Heartbeat is running?<br> <br>Thanks and regards<span class="HOEnZb"><font color="#888888"><br>Neha Chatrath<br> <br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Cheers<br>Neha Chatrath<br> KEEP SMILING!!!!<br>