On Sun, Mar 30, 2014 at 01:08:12PM +0200, Thorleif Wiik [BCIX] wrote:
> Hi,
>
>
> were running OpenBGPd since a long a time as route servers.
I guess those are configured as route-reflectors. Correct?
> We now want to export certain BGP Communities to all route server peers.
>
> We already set the communities, but according to the documentation,
> I'm unsure how to export them to the peers.
>
> We currently use the following config line to set a community e.g.
> 16374:15 to all peers in the groups "n15-v4" and "n15-v6"
The above paragraph does not match with the example. On is to all peers in
group the other is from all peers in group.
> # remarks: 16374:15 learned at Location Nonnendammallee 15
> match from { group n15-v4, group n15-v6 } set community $ASNUM:15
>
>
> When I look into the prefixes on the production box,
> I'll see the correct communitiy, for example:
>
> >bgpctl sh rib as 48173 detail
>
> ..
> BGP routing table entry for 193.107.120.0/22
> 48173
> Nexthop 193.178.185.33 (via 193.178.185.33) from n15-v4-unbelievable
> (94.198.63.8)
> Origin IGP, metric 1, localpref 100, external, valid, best
> Last update: 05w2d01h ago
> Communities: 16374:15
> ..
>
>
> When the connected peers look into their prefixes received from the route
> server,
> they don't see these communities.
>
> My question: What's the most efficient way
> to export these communities to all my peers, now ?
>
Normally I would set the communities on the originating routes and not on
the route server. At least that way the route is tagged properly from the
start.
--
:wq Claudio
