From: Sadiq Yakasai (sadiqtanko@gmail.com)
Date: Tue Feb 26 2008 - 15:45:44 ARST
Hi Rik,
You can actually do unequal cost load-balancing on the outbound using
static routes. Have a look at this (R1 and R3 are dual hommed to each
other):
192.168.1.0/24
R1 (.1) ---------------------------------------------- (.3) R3
----------------------------------------------
162.1.13.0/24
R1#sh run | i ip route
ip route 0.0.0.0 0.0.0.0 192.168.1.3
ip route 0.0.0.0 0.0.0.0 162.1.13.3
ip route 0.0.0.0 0.0.0.0 10.10.10.1
ip route 0.0.0.0 0.0.0.0 10.10.10.3
ip route 0.0.0.0 0.0.0.0 10.10.10.4
ip route 10.10.10.1 255.255.255.255 192.168.1.3
ip route 10.10.10.2 255.255.255.255 192.168.1.3
ip route 10.10.10.3 255.255.255.255 192.168.1.3
ip route 10.10.10.4 255.255.255.255 192.168.1.3
R1#sh ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
Known via "static", distance 1, metric 0, candidate default path
Routing Descriptor Blocks:
* 192.168.1.3
Route metric is 0, traffic share count is 1
162.1.13.3
Route metric is 0, traffic share count is 1
10.10.10.4
Route metric is 0, traffic share count is 1
10.10.10.3
Route metric is 0, traffic share count is 1
10.10.10.1
Route metric is 0, traffic share count is 1
A nice trick there!
Sadiq
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2008 - 16:54:49 ARST