[c-nsp] BGP outbound loadsharing

[Alasdair McWilliam]

Hello,

Apologies if this is a duplicate post, the original message went wrong and
unsure if the list actually forwarded it on or not!

This is a bit of an extension from the original post, but what would be
considered best practice for outbound routing, if you had one link to two
ISPs?

For example, if you were downloading a full BGP table from both ISPs and
assigned local preference to some routes, traffic from a customer could
arrive on ISP1 and return traffic be sent via ISP2. Is this generally
considered to be acceptable or is it preferential for return traffic to be
routed the same ISP from which it came into your network?

Cheers
Alasdair




On Fri, Jan 23, 2009 at 4:00 PM, Kevin Loch <kloch at kl.net> wrote:

> If you are taking full routes you can do manual traffic engineering
> (localpref certain as-paths higher/lower between the two links).
> There are also commercial products that will do this automatically
> for you (Avaya CNA, Internap FCP etc).
>
> If you have connections to differnt ISPs and cannot
> take full routes then requesting partial routes
> and/or filtering received routes may enable you to
> do some path based TE.
>
> If you have multiple links to the same ISP you can
> set maximum-paths for bgp to install multiple next-hops
> for the same path in the fib.
>
> - Kevin
>
>
> Dracul wrote:
>
>> Hi List,
>>
>> Does anyone have a recommended design (configuration) for BGP to
>> utilize/loadshare all outbound traffic? usually the behaviour i'm getting
>> is
>> that my BGP only utilizes
>> one link for outbound. is OER ( Performance Routing ) recommended?
>>
>> regards,
>> chris
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at 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 at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>