Re: [lvs-users] debian lenny-lvs virtual IP

To: " users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [lvs-users] debian lenny-lvs virtual IP
From: Marek Soha <marek@xxxxxxx>
Date: Mon, 16 Feb 2009 14:17:43 +0100
It's not one node cluster...topology is:


I want loadb1 to do loadbalancing the mysql load to two database
servers without MASQ.

One question is - it is possible topology?

I solved it by creating only ldirector configuration with MASQ and wrr
loadbalancing but...if it is possible to solve it also with heartbeat
I want to know it because of my "education" :)

Sebastian, dňa 16. februára 2009 ste napísali:
SV> Like Graeme says, a one-node cluster doesn't make sense. If you plan on
SV> adding a second node, then proceed and try a /etc/ha.d/haresources file with
SV> these contents:

SV> loadb1 ldirectord

SV> And /etc/ha.d/ with these contents:

SV> debugfile /var/log/ha-debug
SV> logfile /var/log/ha-log
SV> logfacility daemon
SV> bcast        eth0
SV> mcast eth0 694 1 0
SV> auto_failback off
SV> node        loadb1

SV> If that works, add all the other options. If you never plan to add a second
SV> node, forget heartbeat and just create the interface and LVS table yourself.

SV> Sebastian
SV> _______________________________________________
SV> Please read the documentation before posting - it's available at:

SV> mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
SV> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
SV> or go to

SV> __________ Informacia od NOD32 3136 (20080527) __________

SV> Tato sprava bola preverena antivirusovym systemom NOD32.


S prianim pekneho dna

             \\ _ _ // 
              ( o o ) 
             Marek Soha 
            marek@xxxxxxx network administrator
          ICQ 146-284-791
          MSN spam@xxxxxxx
             oooO  (  ) 
             (  )  ) / 
              \ ( (_/ 

Please read the documentation before posting - it's available at: mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to
<Prev in Thread] Current Thread [Next in Thread>