RE: [Keepalived-devel] VRRP as a heartbeat mechanism

[Tan, S. <Ta...@so...>]

Just compile keepalived with just the VRRP elements - you don't need to use
the LVS parts. 

(I'm doing this for a couple of linux routers that act as gateways for hosts
with default gateways set.)

:)

Stephen

-----Original Message-----
From: Diego Rivera [mailto:lr...@ra...]
Sent: 23 July 2003 04:58
To: kee...@li...
Subject: [Keepalived-devel] VRRP as a heartbeat mechanism


Hello all (my 4th post today...damn!! :) )

I have a quick question: between some keepalived-enabled boxes who are
successfully doing VRRP (over multiple interfaces) I have a private
circuit that is mainly used to sync configs and similar tasks - no VRRP
goes through there currently.

I'm interested in only sending VRRP traffic through the sync circuit,
NOT the others, but keeping the same effect as it happens now (i.e.
failover happens on the Virtual IPs on all other interfaces).

The idea is to use that sync channel as our "heartbeat" channel, and not
all the rest.  Failover would occurr if any box is out of contact on the
HB channel, and only those boxes for whom the channel is still "alive"
(i.e, HB interface hasn't failed) would attempt to achieve MASTER state.

Is this possible?  What could be an example for doing so?  Is this even
smart (yes, I admit I'm pretty dumb ok? :) ), or is there a better way?

Best


-- 
===========================================================
* Diego Rivera                                            *
*                                                         *
* "The Disease: Windows, the cure: Linux"                 *
*                                                         *
* E-mail: lrivera<AT>racsa<DOT>co<DOT>cr                  *
* Replace: <AT>='@', <DOT>='.'                            *
*                                                         *
* GPG: BE59 5469 C696 C80D FF5C  5926 0B36 F8FF DA98 62AD *
* GPG Public Key avaliable at: http://pgp.mit.edu         *
===========================================================


 
========================================
DISCLAIMER 

The contents of this e-mail and any attachments are confidential to the intended recipient and may also be legally privileged.  Unless you are the named addressee (or authorised to receive for the addressee) of this email you may not copy, disclose or distribute it to anyone else.  

If you have received this email in error, please notify us immediately by e-mail on adm...@se... and then delete the email and any copies.  The Sega Group have made all reasonable efforts to ensure that this e-mail and any attached documents or software are free from software viruses, but it is the recipient's responsibility to confirm this.

========================================