Greetings!
Webmaster wrote:
> Scenario, different locations, different companies managing a T1 into each
> location. Main web server sits at one location, back-up at another. No
> connection between each machine other than the T1 to the internet.
Assumptions:
MainWeb Server 1.1.1.1
BackupWeb Server 2.2.2.2 (plus secondary IP address 1.1.1.1)
Following options - plus a bunch of even more weird:
1.) ISP-sided routing.
This will have to be implemented on your ISPs side and the routes properly
distributed. You will
have automagic failover wether the server or the link goes down.
route 1.1.1.1 (via main site) metric=1
route 1.1.1.1 2.2.2.2 metric=5
2.) Load-Balancer (I)
You place a load balancer in front of the main web server. If the main web
server goes down,
it sends ICMP-redirects, redirecting the packets to the Backup Web Server.
This won't help
if the link goes down.
3.) Load-Balancer (II)
You place a load balancer in front of the main web server. If the main web
server goes down,
it re-sends the packet with IP loose source routing via 2.2.2.2 back to the
uplink router.
This won't help if the link goes down.
4.) VPN / Tunneling
If you don not have access to ISP sided routing, then create aVPN/tunnel
between the two routers
in front of the web servers. You set the following routes on the routers:
Main site router:
route 1.1.1.1 connected metric=1
route 1.1.1.1 (via VPN to backup site) metric=5
Backup site router:
route 1.1.1.1 2.2.2.2 metric=1
But this won't help if the link goes down.
Just some thoughts. Comments?
Bye
Volker
begin:vcard
n:Tanger;Volker
tel;fax:+49 - 69 - 92901-213
tel;work:+49 - 69 - 92901-570
x-mozilla-html:FALSE
url:http://www.res.globalone.net/
org:Global One;Global Project Engineering
version:2.1
email;internet:[EMAIL PROTECTED]
title:Sr. Security Engineer
adr;quoted-printable:;;Stiftstrasse 23=0D=0A;Frankfurt;;60313;Germany
note;quoted-printable:Room 608=0D=0A
fn:Volker Tanger
end:vcard
