We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Static Route for "preferred gateway" with failover to "default gateway" for ONE subnet ONLY

Medium Priority
7,168 Views
Last Modified: 2009-11-25
I am having trouble working through this situation.  I have four branches connected via full mesh WAN links.  ONE of the four branchs is a 56k connection, while the other three are all High Speed connections.  We have set up a secondary high speed WAN link (using a wireless connection) to the slow linked branch that will ONLY provide access between the Head Office and the "slow" branch office.  For this slow branch, the Primary Gateway will still remain the slow link for remote workstations accessing everything except Win2k Server Access (ie..Internet still goes out over slow link).  I want the workstations to fail over to the slow speed link for Win2k Server access if the high speed link goes down (fails to respond to PING) because there IS a route to head office through the slow link (and vice versa for Head Office to Slow Office).

Branch Office Subnet:  192.168.2.0
Default Gateway (slow full mesh):  192.168.2.254
Second Gateway (fast main office link only):  192.168.2.1

Head Office Subnet:  192.168.1.0
Default Gateway (fast full mesh):  192.168.1.254
Second Gateway (single branch direct link only):  192.168.1.1

In the Main Office, I want the servers to communicate to the Branch Office via the fast link, BUT if the fast link goes down I want the servers to auto-switch to the slow link.  I also want the workstations in the Branch office to do the same thing.

What I know:
I did my testing from a workstation in HEAD Office.  The metric on the default gateway is set to 2.
I have added a static route to the 192.168.2.x network with this command
route add 192.168.2.0 mask 255.255.255.0 192.168.1.1 metric 1 -p
Therefore, the head office workstation would communicate to slow branch on metric 1 static route, but on Failure it should have tried the Default Gateway.

PROBLEM:
When I ping a workstation at the remote branch, it goes through the static route that I have set up to the Fast Gateway.  To test the "failover" I shut down the power to the fast gateway device.  I expected the pings to time out for a short period of time and then the workstation would start using the Default Gateway at metric 2.  This never happened, and I do not know why.  

To test further, I added a second static route with a metric 2 pointing to the default gateway.  When I did a ROUTE PRINT, the following lines appeared as I expected they would at the bottom of the output:

Default Gateway:    192.168.1.254
============================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
     192.168.2.0    255.255.255.0    192.168.1.1       1
     192.168.2.0    255.255.255.0   192.168.1.254       2

I cannot set two DEFAULT gateways in Network Properties because the 2nd gateway is ONLY valid to reach the slow remote branch (vice-versa for the remote branch access to Head Office).  The Primary Link gateways need to stay valid at all times.

QUESTION:
Does anyone have any ideas why my workstation is not automatically using the 2nd gateway when it fails to get through the "dead" gateway?

All Hail The Ascii Map

Remote Branch...................Remote Branch
...............|.........\.........................../
...............|..........\......................../
...............|.........56k...............FAST
...............|..............\................./
...............|...............\======/
.............FAST...........|.............|
...............|...........Private Network
...............|...............|.............|
...............|...............|======|
...............|............../...............\
...............|............./..................\
...............|........FAST...............FAST
...............|........../.......................\
........Head Office................Remote Branch
Comment
Watch Question

Commented:
Static routing doesn't really do failover, especially on Windows.  Cisco sort of fakes it by ignoring static routes to interfaces that are down, but that won't help you here.

Next best, then, is to have the hosts and gateways speak some routing protocol so that hosts find out what route to use based on what gateways are up at the moment.  RIP is the obvious choice for this situation.  Failover might take 30 seconds, which is still not great.

In fact, you can have a default (with a higher metric) pointing to the failover gateway, and just have the primary supply a lower-metric default via RIP.

(You will need to install the RIP networking component on the client hosts.  And you'll need to do something similar at the main branch for the routes that point back to that office....)

Author

Commented:
If I do install RIP (which for the moment I will assume is part of the Win2K PRO & SRV CD's), will this create large amounts of data being "routed" by these workstations?  I'm concerned about this from two stand-points:

1)  The security of having 10 workstations and 6 servers acting as "routers" between these gateways (especially concerned about the servers acting as routers)
2)  The extra traffic as 10+ machines sense the data and "route" it without needing to

OR, am I mis-thinking what you're asking me to do?

If I install RIP, is there a way to tell the machines that, even though RIP is installed, they should route nothing at all?  Then, they won't route anything, which answers my security concerns, BUT do they still take advantage of the Routing PROTOCOL in order to sense a dead gateway?
Leandro IaconoSenior Premier Field Engineer

Commented:
I don't think that RIP is routing ... none of them route ... RIP is just a language to learn where the computer should go through .... depending on factors you give it ... for example ... speed ....

Through RIP a computer automaticly learns the fastest way to get from one point to another .... its doesn't make the computer act like or be a router ...

Am I not correct PennGwyn ?
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Leandro IaconoSenior Premier Field Engineer

Commented:
Wow ... you really do know your stuff PennGwyn

Author

Commented:
Sorry about the delays.  I have been away for a while (and am away for an extended Easter Weekend).  I haven't forgotten about your suggestions, and will be trying them out soon.  Will keep all informed as to what the results are.

Hayzeus

Author

Commented:
Final Update:
The Gateways were not failing over because the method I was using to trigger them was ICMP vs. TCP.  ICMP packets will not trip the "dead gateway detection," thus my gateways were not failing over properly.

I am not sure if the answer suggested in this thread was going to work because I never tried it.  However, it sounds plausible to me, and based on the depth of detail that you provided, I will award you the points.

Thanks for the help,
Hayzeus
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.