[c-nsp] Receiving BGP communities

[Arie Vayner (avayner)]

Seth,

You can use the "debug ip bgp updates" command (if you are getting a big
table, you can use an ACL to filter it out...).
If you get communities from your upstream, you would see it. If not,
just send them the output, and let them worry about it.

Arie 

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Seth Mattinen
Sent: Saturday, September 06, 2008 20:20 PM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Receiving BGP communities

On Sat, September 6, 2008 00:52, Ran Liebermann wrote:
> Maybe you have an ingress route-map setting new communities without 
> the "additive" suffix?
>

Here's what my ingress route-map looks like:

ip as-path access-list 2 permit ^3561$

route-map set-localpref permit 10
 match as-path 2
 set local-preference 200
 set community 11170:3561 additive
!
route-map set-localpref permit 20
 set community 11170:3561 additive
!
route-map set-localpref permit 30
!

I'll admit I'm quite new to BGP communities, but I *can* see 11170:3561
within my own network, just nothing upstream says they're sending.

~Seth

_______________________________________________
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/