Re: load balancing with a failover
- From: "Charlie Root" <root@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Mar 2006 18:00:21 +0100
"Charlie Root" <root@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:duaim1$103q$1@xxxxxxxxxxxxxxxxxxxxxx
<yo> wrote in message news:9rdh02drpjnvq7j0m4l63hgcoafkif1rov@xxxxxxxxxx
its a cost thing they dont want to load balance the 3rd line and only
want it as a backup solution.
ok, then the only solution I see is to use GRE tunnel between loopbacks of
two routers, run EIGRP _only_ over the tunnel and have RTR tracker to
setup route to the remote loopback over thirds interface only if one of
the two "primary" links goes down. There will be slight overhead of GRE
encapsulation and your routers CPU will be penalized, but at the moment I
can't think of any alternative.
I'm sorry, gotta go now. If you don't solve this issue during the weekend,
I'll post configs with GRE on monday.
If it's still relevant, below is simplest version of possible config. Assume
you have serial0/0:0 (IP: 192.168.0.2/30 on your side) and serial0/1:0 (IP:
192.168.0.6/30) as two primary interfaces and serial1/0:0 is the backup
interface (IP: 192.168.0.10/30); IP of the loopback (source of GRE tunnel)
on the remote side is 192.168.1.1/32. The tunnel interfaces have addresses
from other network though (say 192.168.130.0/30)
!
track 100 interface Serial0/0:0 line-protocol
!
track 101 interface Serial0/0:0 line-protocol
!
track 102 list boolean or
object 100 not
object 101 not
!
int lo0
ip addr 192.168.1.2 255.255.255.255
!
int tun0
ip addr 192.168.130.2 255.255.255.252
tun mode gre
tun source lo0
tun dest 192.168.1.1
!
ip route 192.168.1.1 255.255.255.255 192.168.0.9 track 102
!
router eigrp 1
network 192.168.130.0 0.0.0.3
no auto-summary
!
CE-2.LAB#sh ip eigrp topology
IP-EIGRP Topology Table for AS(1)/ID(192.168.129.2)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 192.168.130.0/30, 1 successors, FD is 297244416
via Connected, Tunnel0
Add whatever other networks you have on these routers, but do NOT run EIGRP
on serial interfaces (important!). The other side should configured in the
similar fashion. If you want to have more reliable solution you just need to
replace tracking interfaces with RTR ping probe of remote address like in
this document -
http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps5413/products_feature_guide09186a00801d862d.html.
I didn't have enough time to rebuild physical setup in the lab to represent
the scenario, but here is some debug output that will give you an idea
what's going on (disregard the addresses just watch out what's going on):
CE-2.LAB# deb ip routing
IP routing debugging is on
CE-2.LAB#sh ip rou 192.168.1.1
% Network not in table
CE-2.LAB#conf t
Enter configuration commands, one per line. End with CNTL/Z.
CE-2.LAB(config)#int se0/0:0
CE-2.LAB(config-if)#shut
CE-2.LAB(config-if)#
1w0d: is_up: 0 state: 6 sub state: 1 line: 0 has_route: True
1w0d: RT: interface Serial0/0:0 removed from routing table
1w0d: RT: del 192.168.128.20/30 via 0.0.0.0, connected metric [0/0]
1w0d: RT: delete subnet route to 192.168.128.20/30
1w0d: RT: NET-RED 192.168.128.20/30
1w0d: RT: delete network route to 192.168.128.0
1w0d: RT: NET-RED 192.168.128.0/24
1w0d: RT: SET_LAST_RDB for 192.168.1.1/32
NEW rdb: via 192.168.0.5
1w0d: RT: add 192.168.1.1/32 via 192.168.0.5, static metric [1/0]
1w0d: RT: NET-RED 192.168.1.1/32
1w0d: RT: del 0.0.0.0 via 192.168.128.21, static metric [1/0]
1w0d: RT: delete network route to 0.0.0.0
1w0d: RT: NET-RED 0.0.0.0/0
1w0d: RT: NET-RED 0.0.0.0/0
*Sep 9 08:44:40.670: %LINK-5-CHANGED: Interface Serial0/0:0, changed state
to administratively down
1w0d: is_up: 0 state: 6 sub state: 1 line: 0 has_route: False
*Sep 9 08:44:41.670: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Serial0/0:0, changed state to down
1w0d: is_up: 0 state: 6 sub state: 1 line: 0 has_route: False^Z
CE-2.LAB#sh ip rou 192.168.1.1
*Sep 9 08:44:47.862: %SYS-5-CONFIG_I: Configured from console by console
Routing entry for 192.168.1.1/32
Known via "static", distance 1, metric 0
Routing Descriptor Blocks:
* 192.168.0.5
Route metric is 0, traffic share count is 1
CE-2.LAB#conf t
Enter configuration commands, one per line. End with CNTL/Z.
CE-2.LAB(config)#int se0/0:0
CE-2.LAB(config-if)#no shut
CE-2.LAB(config-if)#
1w0d: is_up: 0 state: 4 sub state: 1 line: 0 has_route: False^Z
CE-2.LAB#
*Sep 9 08:45:02.778: %SYS-5-CONFIG_I: Configured from console by console
*Sep 9 08:45:02.910: %LINK-3-UPDOWN: Interface Serial0/0:0, changed state
to up
1w0d: is_up: 1 state: 4 sub state: 1 line: 0 has_route: False
1w0d: RT: SET_LAST_RDB for 192.168.128.20/30
NEW rdb: is directly connected
1w0d: RT: add 192.168.128.20/30 via 0.0.0.0, connected metric [0/0]
1w0d: RT: NET-RED 192.168.128.20/30
1w0d: RT: interface Serial0/0:0 added to routing table
1w0d: is_up: 1 state: 4 sub state: 1 line: 0 has_route: True
1w0d: RT: del 192.168.1.1/32 via 192.168.0.5, static metric [1/0]
1w0d: RT: delete subnet route to 192.168.1.1/32
1w0d: RT: NET-RED 192.168.1.1/32
1w0d: RT: delete network route to 192.168.1.0
1w0d: RT: NET-RED 192.168.1.0/24
*Sep 9 08:45:04.074: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Serial0/0:0, changed state to up
Hope this helps.
Kind regards,
iLya
.
- References:
- Re: load balancing with a failover
- From: Charlie Root
- Re: load balancing with a failover
- From: Charlie Root
- Re: load balancing with a failover
- Prev by Date: Is possible Pix + Netflow stadistics?
- Next by Date: Re: a question on EIGRP protocol
- Previous by thread: Re: load balancing with a failover
- Next by thread: Re: load balancing with a failover
- Index(es):
Relevant Pages
|
