[c-nsp] MPLS VPN RR Strategies

[Brian Turnbow]

my understanding is that rr-group is used to limit bgp extended communities
propogated globally in the vpvn4 session. You can create 2 rr client
peergroups under your address family and assosciate the  filters to them to
so what you want.
This could get really messy when you add new customer that need to be on
routers that are in
different peergroups. If there are not alot of routes and yu have memory,
put  all the routers in the same group. It'll make it alot easier to add
customers in the future.

regards
Brian


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net]On Behalf Of
rwcrowe at comcast.net
Sent: giovedì 2 settembre 2004 22.20
To: cisco-nsp
Subject: [c-nsp] MPLS VPN RR Strategies


I have a question on MPLS VPN Route Reflectors or most likely on the use of
the "rr-group" command. Say you have 5 PE routers that have 2 seperate
customers MPLS VPNS configured. These 5 PE routers are peering with a route
reflector and you want them to only recieve routes for route target 100:1
(Customer 1) and 100:2 (Customer 2). You would configure the rr-group with
an extended community list matching 100:1 and 100:2. So far so good.
But say you get 2 new customers that want VPNS and you want to use the same
route reflectors for them to peer with. How would you say neighbor 1 and 2
are associated with rr-group 1 which has a community list that only sends
the routes they have VPNS for, and neighbors 2 and 3 are associated with rr
group 2 which has a extended community list that only sends them the routes
for their VPNS ?
>From what I see you can only configure 1 rr-group on a route reflector. Is
there a way to configure rr-groups like peer groups ? So each neighbor or
group of neighbors only gets the routes for which they need ?
--

rwcrowe at comcast.net
_______________________________________________
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/