|
No, i am definitely not saying that you should switch, I am just saying that
the documentation of keepalived described very well the principals that you
should configure heartbeat with .
a sample of redundant active-active lvs directors setup with heartbeat :
on f1 :
external interface 200.200.200.1
internal interface 10.0.0.1
on f2 :
external interface 200.200.200.2
internal interface 10.0.0.2
haresources on both machines :
f1 10.0.0.253 200.200.200.3
f2 10.0.0.254 200.200.200.4
half of real servers have default gateway point to 10.0.0.253 , and the
other half to 10.0.0.254
half of the clients access the real servers with ip address 200.200.200.3,
and half with 200.200.200.4
if you don't need active active setup , just (in this config) i would have
in haresources :
f1 10.0.0.253 200.200.200.3
all real servers have as default gateway 10.0.0.253, and all clients would
access the cluster at 200.200.200.3
-------Original Message-------
From: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Date: éåí øáéòé 27 ðåáîáø 2002 18:47:22
To: 'lvs-users@xxxxxxxxxxxxxxxxxxxxxx'
Subject: RE: One Network LVS-NAT with HA
So are trying to say that I should use keepalived instead of heartbeat?
-----Original Message-----
From: Alex Kramarov [mailto:alex@xxxxxxxxxxxxxxx]
Sent: Wednesday, November 27, 2002 10:29 AM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: One Network LVS-NAT with HA
I would really suggest that people read the keepalived documentation about
using directors in active-active more - this would answer a lot of questions
of this kind .
In general, even in a active-passive setup one should have a floating vip on
the external network that the requests from clients are directed to it, and
a floating vip on the internal network, that this vip is the default gateway
to the real servers.
from this setup to active-active in only one step - have 2 VIPs on the
external side, and 2 on the internal, make sure that in normal situation one
pair of vip's (one external and one internal) is on one director, and the
other pair is on the second. direct clients to use the 2 vip's (for example,
set that the html of your site is retrieved through vip1, and the images
through vip2). if any of the directors fail, then all 4 ip's will be on the
same machine, thus achieving high availability, and active-active
configuration.
the documentation on keepalived's site provides very good description of
this process.
using only one network shouldn't contradict with this setup - just make the
logical adjustments.
Alex.
CONFIDENTIALITY NOTICE: The information in this e-mail is privileged and
confidential. Any use, copying or dissemination of any portion of this
e-mail by or to anyone other than the intended recipient(s) is unauthorized.
If you have received this e-mail in error, please reply to sender and delete
it from your system immediately.
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
.
|
