[j-nsp] Load Balancing via BGP outbound at Colo

[Erdem Sener]

a little remark:

adding 'no-export' community to your advertised routes to ISP #x will
guarantee that ISP #x won't advertise these prefixes to any of its
ebgp peer, meaning "his peers won't use ISP #x to get to you".

On the other hand, this doesn't mean that ISP #x will certainly use
its direct link towards you for your prefixes, since his route
selection will be based on his own import rules (as-path, local pref
etc.)

Also, it's always a good idea to check with a peer before sending out
community information and to make sure he's not "resetting" it (using
a import filter)

Cheers,
Erdem

On 3/15/07, Chuck Anderson <cra at wpi.edu> wrote:
> On Thu, Mar 15, 2007 at 02:28:20PM +0200, Tim Nagy wrote:
> > You'd like to send and receive all traffic on the links to ISP #1 except for
> > traffic that terminates in ISPs #2, #3, #10, or #20. Is that correct?
> >
> > For inbound, things are more complicated.  The only way that you can really
> > influence your inbound traffic across multiple ISPs is through AS path
> > prepending. You could advertise all of your routes to all ISPs, but prepend
> > your AS multiple times to ISPs #2, #3, #10, and #20. That would reduce the
> > traffic flow in from those ISPs and make your ISP #1 links the primary
> > inbound points.
>
> You could also attach the well-known community NO EXPORT to routes you
> send to ISP #2, #3, #10 and #20 so that those ISPs use your routes to
> get back to you directly, but they won't readvertise your routes to
> their upstreams and peers.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>