Thanks Andrew! I followed the example, it's working as expected!
-Vince -- Vince Gabriel Field Technical Analyst SGI office: 361.729.9151 cell: 409.392.8083 > -----Original Message----- > From: Andrew Beekhof [mailto:and...@beekhof.net] > Sent: Thursday, August 26, 2010 2:48 AM > To: The Pacemaker cluster resource manager > Subject: Re: [Pacemaker] IPaddr2 not failing-over > > On Wed, Aug 11, 2010 at 10:55 PM, Vince Gabriel <vin...@sgi.com> wrote: > > Hi everyone, > > > > I have new cluster that is works exceptionally well with the exception > of > > the IPaddr2 virtual interfaces initiated failovers. If the interface is > > downed or cable disconnected, a failover never happens. I've attempted > to > > incorporate pingd however that has not helped either? It's my > understanding > > a pingd clone should not be needed any long? > > If you want to move services based on connectivity, then you need a > ping(d) clone and some rules that make use of the properties it sets. > > http://www.clusterlabs.org/doc/en- > US/Pacemaker/1.0/html/Pacemaker_Explained/ch09s03s03.html > > > > > nas1:~ # rpm -qa | grep hear > > > > heartbeat-resources-3.0.0-0.2.8 > > > > heartbeat-common-3.0.0-0.6.5 > > > > libheartbeat2-3.0.0-0.6.5 > > > > cnas1:~ # rpm -qa | grep -i pace > > > > pacemaker-pygui-1.99.2-0.2.6 > > > > libpacemaker3-1.0.5-0.5.6 > > > > pacemaker-1.0.5-0.5.6 > > > > primitive HA3-ip ocf:heartbeat:IPaddr2 \ > > > > operations $id="HA3-ip-operations" \ > > > > op monitor interval="60s" start-delay="0" timeout="30s" > > on-fail="restart" \ > > > > op start interval="0" timeout="90" on-fail="restart" > > requires="fencing" \ > > > > op stop interval="0" timeout="100" on-fail="fence" \ > > > > params ip="10.10.20.33" nic="eth3" cidr_netmask="24" \ > > > > meta resource-stickiness="1" migration-threshold="1" > > > > It's my understanding...please correct me if I'm wrong....if the interface > fails > > it will attempt to restart the interface once, > > No, only if the resource fails. > Your logic only holds if the RA reports failure when the interface fails. > > > if it happens again the group > > it's associated with should failover to the standby node based on > > "migration-threshold="1"". > > > > Thanks in Advance, > > > > -Vince > > > > -- > > > > Vince Gabriel > > > > Field Technical Analyst > > > > SGI > > > > office: 361.729.9151 > > > > cell: 409.392.8083 > > > > > > > > > > > > _______________________________________________ > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > > Project Home: http://www.clusterlabs.org > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: > > http://developerbugs.linux- > foundation.org/enter_bug.cgi?product=Pacemaker > > > > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://developerbugs.linux- > foundation.org/enter_bug.cgi?product=Pacemaker _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker