is suitable whenever you have to ways to route traffic into a distand IP
network. In normal cases via your main-gateway and while having
interferrences on your main line via the backup-gateway,
We arranged a few
possible configurations for you:
1) Internet Fallback (Default
Use f.ex. one of your 10
monitors to setup an internet fallback connection.
destination network 0.0.0.0 and as destination netmask 0.0.0.0
Main-gateway is in
this case 192.168.1.1 and use the 192.168.1.2 as backup-gateway.
We search now 3
diffrent hosts into the internet with diffrent services (f.ex. SMTP TCP 25, POP3 TCP 110, WWW TCP 80)
here are virtual and not real existend. Please take for your company
unimportand hosts, since these hosts are not reachable in backup
2) LAN-LAN Fallback
Use one monitor to monitor
the LAN-LAN connection to your branch office. For that you need two
licences of Failover-Route (one for each site).
Enter as destination
network 192.168.2.0 and as destination netmask 255.255.255.0 metric 1.
Your main-gateway is in
this case 192.168.1.1 and your backup-gateway is 184.108.40.206. Use IP
Port Server on both Failover-Routers with TCP Port 32000 (f.ex.)
Please configure now the
following check hosts in the central office:
192.168.2.5 TCP 32000
192.168.2.1 TCP 23 (Telnet)
Please configure now the
following check hosts in the branch office:
192.168.1.5 TCP 32000
192.168.1.1 TCP 23 (Telnet)
Please note, that these
check-hosts are not reachable in backup cases!
3) VPN Fallback (dynamic
In this very special example we have branch offices with dynamic IPs
and one leased line per site. At the central site we have two leased
lines with public IPs. The branch offices connect to line 1 via VPN over
Failover-Route now recognizes if a site connects to line 2 because of an
interruption of line 1 at the central site and routs the IP traffic for
the connected branch offices to line 2 (here you have to use at least a
3 monitor version). If line 1 at the central site is back again,
Failover-Route waits until the VPN tunnels connects back to line 1 and
then routes the traffic back to the main-gateway. For this scenario you
have to use VPN hardware that allows to configura VPN backup server at
the branch offices (f.ex. Cisco or SonicWalls)
Failover-Route is no load-balancing Sysmte. But you are able to
seperate some dedicated traffic with failover function as well.
For example your company sends and receives emails from 10.40.21.1 and
you won't overload your main line with SMTP and POP3 traffic any longer,
then configure one monitor as follows:
Check 2 hosts in the same
IP network as your SMTP/POP server. Here: 10.40.21.2 TCP 80 and 10.40.21.3 TCP 53.
Route now your POP/SMTP server destination network: 10.40.21.1 mask
255.255.255.255.255 to the DSL fallback line gateway. Enter as backup
gateway the main line gateway.
Use another monitor to
check your Internet connection: 0.0.0.0 mask 0.0.0.0 over your main
leased line. Configure now the backup DSL line as backup gateway.
Configure the check hosts similliar to scenario 1.
If both lines are up, SMTP/POP traffic is routed to DSL/Fallabck and the
remaining internet traffic goes to your main line 1. If one of the two
lines fails the whole internet traffic will be routed to the remaining
gateway until the line is back again.
All these scenarios can be combined if you have the appropriate
number of monitors available. We recommend urgently to plan your IP
routing to prevent logical errors while configuring Failover-Route!
More detailled information about the scenarios you will find in the
Failover-Route manual you can download in our download section or in the
manual, you can find in the \manual folder of your Failover-Route
Intelligent Failover-Fallback Software