[c-nsp] BGP Announce Partial Routes
Nick Shah
Nick.Shah at aapt.com.au
Thu Aug 18 03:17:36 EDT 2005
Simple way: Use BGP communities to tag the routes based on their source.
Then you can filter based on community lists. This is just one of the
uses. You can publish the list of communities to your customers so they
can filter however they wish.
Complex (but highly scalable) way: Check out RPSL - Router policy
specification language. It's a pain to get going, but once you have it,
it will give you God-like control :)
http://www.irr.net/docs/rpsl.html
rgds
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Alexander C.
Fossa
Sent: Tuesday, 16 August 2005 6:03 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] BGP Announce Partial Routes
Hi,
I'm after a bit of advice / help with my BGP configuration.
Basically we have 3 full route upstreams and two partial route upstreams
and about 200 private peerings. We have one customer who we announce our
'best mix' to and we receive their prefix and announce it to our
upstreams / peers. How can I limit the routes that I announce to a
customer, as we have one interested in purchasing only peering routes
off us. For example some how tagging the routes when we receive from our
two partial upstreams and private peers and then creating an announce
list and only sending that to a partial routes customer.
I hope you understand what I mean!
Best Regards,
Alexander Fossa
_______________________________________________
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/
This communication, including any attachments, is confidential. If
you are not the intended recipient, you should not read it - please
contact me immediately, destroy it, and do not copy or use any part of
this communication or disclose anything about it.
More information about the cisco-nsp
mailing list