From: Rik Guyler (rik@guyler.net)
Date: Tue Feb 26 2008 - 19:04:33 ARST
I've been reading up on OER and it does do some cool stuff and all on one
router if needed. The documentation however leaves a lot to be desired.
Does anybody have any production OER running? Anybody have single router
configs with 2 ISP connections they could share?
Thanks
Rik
_____
From: dara tomar [mailto:wish2ie@gmail.com]
Sent: Tuesday, February 26, 2008 1:20 PM
To: Tony Schaffran (GS)
Cc: Sadiq Yakasai; Rik Guyler; Cisco certification
Subject: Re: outbound load-balancing
Tony,
I find the explanation your right.
Does the cisco OER really provides us with any such function??
Because it's quite basic as a requirement, and I don't see this happening as
per the BW difference between the interfaces.
Regards,
Dara
On Tue, Feb 26, 2008 at 11:42 PM, Tony Schaffran (GS)
<groupstudy@cconlinelabs.com> wrote:
Actually, I do not think that is load-balancing.
Those are just redundant paths and the primary will always be selected as
the candidate path unless that interface actually goes down.
If there is a problem in the path and that interface stays up, the route
(marked with *) will not be deleted and your traffic will not get out.
That is how I understand what you are showing. If I am wrong, please
enlighten me.
Tony Schaffran
Network Analyst
CCIE #11071
CCNP, CCNA, CCDA,
NNCDS, NNCSS, CNE, MCSE
www.cconlinelabs.com
Your #1 choice for online Cisco rack rentals.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Sadiq Yakasai
Sent: Tuesday, February 26, 2008 9:46 AM
To: Rik Guyler
Cc: Cisco certification
Subject: Re: outbound load-balancing
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 <http://192.168.1.0/24R1>
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:50 ARST