Hi John, On Tue, Sep 27, 2011 at 07:39:50PM -0400, John Lauro wrote: > As an example setup for some of systems: > My haresources file has: > hawebcl1 IPaddr2::xx.xx.xx.77/24/eth0 > > Actual IPs are xx.xx.xx.78 and xx.xx.xx.79 on the haproxy boxes. > > The real gateway is .1. > > So both haproxy hosts have the mangle setup for tproxy, gateway as .1, > etc... > All the backend servers have .77 as their default gateway instead of .1. > > I leave haproxy running on both. It means both constantly poll the backend > servers, but why both having heartbeat start/stop it... > > > Only minor annoying part is you must specify the unique IP on the source > lines in haproxy config which makes it slightly harder to keep them in sync. > IE: > source xx.xx.xx.78 usesrc client > If you have heartbeat stop/start haproxy you could probably just use the > shared IP for a common config file.
You should always assign your shared IPs in /32, that way the machine's real address will always be used for outgoing traffic (checks, logs, ...). Cheers, Willy
