Re: Failover IP router
- From: brad@xxxxxxxxxxxxxx
- Date: Tue, 27 Nov 2007 15:49:56 -0600 (CST)
I have been googleing for this, but can't seem to find the right answer.
What I am trying to do is to create a failover router on a redhat box.
1. website.com will be on 2 servers
2. website.com has one IP address
3. redhat box router will have the 1 IP address for website.com on it.
4. website.com server1 will be on 192.168.1.10
5. website.com server2 will be on 192.168.1.11
6. If website.com server1 fails, website.com server2 will take over.
We are not worried about cookies that have been set on server1 to be moved
to server2. We are just worried about the second machine taking over.
What
would be better is if it could be a load balancing setup so that it will
use
both servers, but if one fails, people will not notice it because the
other
server will then be taking all of the requests.
I have googled for "Linux failover iptables router" and a few other
combinations of words, but what I keep finding is failover for the
outbound
connections. Having 3 Nic cards 1 going to one ISP, 1 going to another
ISP
and one going to the internal network. Maybe I am just using the wrong
wording. Any url links for instructions would be appreciated.
Thank You
Steve
It looks like you are trying to use the router to perform the failover.
Another approach would be to use RHEL Cluster Suite and configure it with
the 2 servers (leave the router out of it). Going this route the 2
webservers will talk to each other with a heartbeat and if the active
server fails, the passive server will detect this and stop the primary
server, take over the IP address and begin serving the content. The
cluster suite also supports load balancing but I have not used it.
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Cluster_Administration/index.html
Another option would be to use something like pound for software load
balancing. You could run pound on the router and have it listen on the
website's public IP and then forward requests to the 2 backend web servers
based on a number of algorithms. It will detect a failed server and stop
sending requests to it. I am sure the cluster suite load balancing works
in a similar manner.
http://www.apsis.ch/pound/
Brad Crotchett
brad@xxxxxxxxxxxxxx
http://www.bradandkim.net
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
- References:
- Failover IP router
- From: Steven Buehler
- Failover IP router
- Prev by Date: Re: Failover IP router
- Next by Date: Re: Failover IP router
- Previous by thread: RE: Failover IP router
- Next by thread: RE: Failover IP router
- Index(es):
Relevant Pages
- Re: Cannot connect to RWW from home PC
... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS
record for. ... One question - if I reset the Thomson Router will that clear all the
... Heres' the info for our server: ... (microsoft.public.windows.server.sbs) - Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
... Windows Server 2008 Readiness Team ... I was feeling nervous about our teaming-capable
adapter as I read it might be sending out heartbeats, so I disabled it AND configured the cluster
on a separate DLink card in multicast mode. ... I am losing the plot with NLB, I have spent
a week trying to get it working. ... I thought that the litmus test was that the router functions
fine when no NLB is installed, but when it is, things start going screwy. ... (microsoft.public.windows.server.clustering) - Re: Cannot connect to RWW from home PC
... That would be the address you need a DNS record for. ... You say "And in the
router you need to forward to your external nic IP" ... Still can't telnet to any of your
ports at your public ip address. ... Heres' the info for our server: ...
(microsoft.public.windows.server.sbs) - Re: Cannot connect to RWW from home PC
... You say "And in the router you need to forward to your external nic IP" ...
You say "You need the domain hoster to setup a DNS record that will be ... We have rerun
CEICW sort of hoping it would sort out the router but no ... Heres' the info for our server:
... (microsoft.public.windows.server.sbs) - Re: Cannot connect to RWW from home PC
... No 10.0.0.138 is the address used to log onto Thomson's router to make the ...
On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0
172.26.0.1/16 Extra none ... Heres' the info for our server: ... (microsoft.public.windows.server.sbs)