We have 2 internal web servers that are being load balanced round robin by an ACE. The ACE is going away and will not be replaced with an appliance.
My boss would like to have the 2 internal web servers receive the http requests and decide between them which will actually handle the request in a round robin configuration without adding an additional server or appliance into the equation. This would eliminate a single point of failure, the appliance, and if one of the servers goes down the other will continue to service the http requests.
I’m told that Windows does NLB with a few clicks between 2 servers and doesn’t require using a third device like the ACE.
Is this possible to configure on Linux? Is there software to make this happen or can it be done with only the OS? We are using SUSE SLES 11 SP2. Thanks.
On Tue, 30 Oct 2012 18:24:03 +0000, dvbell wrote:
[color=blue]
We have 2 internal web servers that are being load balanced round robin
by an ACE. The ACE is going away and will not be replaced with an
appliance.
My boss would like to have the 2 internal web servers receive the http
requests and decide between them which will actually handle the request
in a round robin configuration without adding an additional server or
appliance into the equation. This would eliminate a single point of
failure, the appliance, and if one of the servers goes down the other
will continue to service the http requests.
I’m told that Windows does NLB with a few clicks between 2 servers and
doesn’t require using a third device like the ACE.
[COLOR="#0000FF"]I tracked down the SLES 11 SP2 doc for your link above, and it mentions multipathing, but I could not find anything on round robin load balancing.[/COLOR]
[COLOR="#0000FF"]The link above requires using a third server to do the load balancing and that is outside the parameters I gave. Sorry, but thanks.[/COLOR]
We have 2 internal web servers that are being load balanced round robin
by an ACE. The ACE is going away and will not be replaced with an
appliance.
My boss would like to have the 2 internal web servers receive the http
requests and decide between them which will actually handle the request
in a round robin configuration without adding an additional server or
appliance into the equation. This would eliminate a single point of
failure, the appliance, and if one of the servers goes down the other
will continue to service the http requests.
I’m told that Windows does NLB with a few clicks between 2 servers and
doesn’t require using a third device like the ACE.
Is this possible to configure on Linux? Is there software to make this
happen or can it be done with only the OS? We are using SUSE SLES 11
SP2. Thanks.
[/color]
IMHO, whoever said Windows does safe LB without anything else doesn’t understand
much.
If we can throw some state stuff out the window… then fine… just LB by
rotating via multiple DNS A records. That’s the easiest way.
If want things like session stickiness and SSL, etc… you really need to
consider a LB device (or two for at least failover redundancy).
Use keepalived / VRRPd / whatever to create TWO virtual IP’s spamming bother servers. Then use round robin DNS to present the two to clients. Here is an example with fake IPs:
Server A:
Real IP: 10.10.10.10
Virt IP 1: 10.10.10.1 ← Master
Virt IP 2: 10.10.10.2 ← Slave
Real IP: 10.10.10.20
Virt IP 1: 10.10.10.1 ← Slave
Virt IP 2: 10.10.10.2 ← Master
A client will get either .1 or .2 which will go to the server which is the Master for that IP. If either server fails, the other server will be the Master for BOTH .1 and .2 hence handling failover. This will handle most use cases.
http://www.novell.com/communities/no…g-smt-servers-sles11-sp1-hae-cluster
The link above requires using a third server to do the load balancing and that is outside the parameters I gave. Sorry, but thanks.
while I have not read the linked documentation, I know from experience that you don’t need a third machine to run load-balanced web servers with HAE cluster.
[/color]