If you really want to use route-maps to force your traffic down a certain interface at least use it with verify-availability incase your hop goes down so you have a back up path, no point forcing traffic down a dsl line that has died.

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gtpbrtrk.html


----- Original Message ----- From: "Dan Letkeman" <[EMAIL PROTECTED]>
To: "Ben Steele" <[EMAIL PROTECTED]>; <cisco-nsp@puck.nether.net>
Sent: Thursday, July 24, 2008 7:42 AM
Subject: Re: [c-nsp] combining multiple dsl lines


The adsl connections are PPPoE and they do not support multilink.  I
am using nat on the router as well.

I guess I will stick with route-map's for now as I know how to
configure it and it works well in this configuration.

Thanks for the info!
Dan.

On Tue, Jul 22, 2008 at 11:18 PM, Ben Steele
<[EMAIL PROTECTED]> wrote:
Depends a lot on the adsl connections, are they ppp ? does the remote end
support multilink? if so then multilink ppp is a good option providing all 4
lines are the same characteristics.

Otherwise other options are cef load balancing, what type will depend on
whether you are using NAT or not as you want to make sure the packet flow
takes the right path, load balancing using the source/dest port algorithm
works quite well though, probably wouldn't reccomend per packet over adsl.

The route-map way is ok but wouldn't utilise the links as well as cef load
balancing or ppp multlink could.

Another option worth throwing in is the use of ip sla on your routes so as to remove them from the equation should one link go down, can also be done
with the route-map using verify-availability on the next-hop option.

Ben

On 23/07/2008, at 1:39 PM, Dan Letkeman wrote:

I have a customer that is wanting to combine 4 adsl connection through
one router.  In the past I have setup systems where I have taken
groups of ip's from the internal network and have route-map'd them to
different adsl connections.  Is there a way to "combine" the dsl
connections or is using route-map's still the better way to go?

Thanks,
Dan.
_______________________________________________
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/




_______________________________________________
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to