On 02/21/2011 08:00 PM, Frederik Schüler wrote: > Hello *, > > as the various ocf:*:ping[d] incarnations don't meet my specific needs,
May I ask why and how? > I > wrote a small RA using ethtool to detect a network link failure, in order to > trigger a failover. Well, what if the link is up but there's an upstream problem? I've always liked how ocf:pacemaker:ping actually monitors connectivity to an upstream IP, which covers both immediate link failure and upstream problems. Similar to how in active/backup bonding, you can fail over based on the status of an ARP request, rather than MII link status. Your thoughts? Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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
