|
Andre Correa wrote:
>
> Hi LVS...
>
> I have a PPPoE/L2TP concentrator that make Routing, NAT, firewall,
> Traffic Shapping, QOS and 802.1q for PPPoE and L2TP users connected to
> it. I'm looking for a way to implement redundancy and scalability in
> my solution and thought LVS would help.
>
> Is LVS able to load balance a PPPoE server? reading howtos and
> docs I've found nothing on PPPoE, VPN or VLAN examples. The Director is
> told to be a "L4 switch" what can be a problem for L2 protocols.
I don't know a whole lot about most of these. Either you're
going to have to educate some of us or wait till someone, who
knows, comes up on the list.
I assume these are all routing type functions (your box passes
the packets on to other boxes, which the client is really connecting
to).
LVS is designed to provide redundacy for servers, ie you put on-line,
multiple copies of a server and allow many clients to contact only
one of these machines. To the sum of the clients, there appears to
be a big machine.
If this is correct, you need multiple routers with failover between
them. Failover is a little tricky to implement. There are two
methods used in LVS, heartbeat (from the Linux-HA people) and
an implementation of vrrpd by Alexandre Cassen.
However you aren't home even if you setup failover. If any of these
protocols have state, which must be maintained through the failover,
then you need a router state sync demon. These are even trickier.
LVS has one of these to transfer state between failover directors.
In general you'll need one of these demons for each protocol
which has state.
Joe
--
Joseph Mack PhD, Senior Systems Engineer, SAIC contractor
to the National Environmental Supercomputer Center,
ph# 919-541-0007, RTP, NC, USA. mailto:mack.joseph@xxxxxxx
|
