[c-nsp] BGP Announce Partial Routes

[Kim Onnel]

Distribute list : http://www.cisco.com/warp/public/459/22.html


On 8/16/05, Pavel Narozhnyy <paveln at gmail.com> wrote:
> Dear Alexander,
>   best way to do this is to "tag" incoming routes. You can use community
> policy-map mechanism and community tag for this.
>  I hope, search on cisco.com <http://cisco.com> will give good results based
> on this two keywords.
> 
> 
>  On 8/15/05, Alexander C. Fossa <alex at xifos.net> wrote:
> >
> > 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/
> >
> _______________________________________________
> 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/
>