Hi Edmar, You should have the same "view" of routes on all your RR. If you want to prefer traffic for a route, (say 10.10.10/24 via PE-A) then you should have the PE-A have a BGP import policy to modify the route attributes when they are learned.
When you have a unique routes (ie. different RD) then the RR's will advertise both of these vpnv4 routes to all the RR clients. Then your PE's (clients) will see both routes and evaluate them. Even though you can have policy on an RR, it's a messy situation to modify anything on RR's, in my personal opinion. Kind regards, Truman On 31/05/2010, at 3:25 PM, Sorilla, Edmar (NSN - AE/Dubai) wrote: > Thanks for the prompt reply Truman. What about if the PE is peered to > two route reflector and we want to manipulate the local preference to > only one RR. > > Br, > Edmar > > -----Original Message----- > From: ext Truman Boyes [mailto:tru...@suspicious.org] > Sent: Monday, May 31, 2010 10:56 AM > To: Sorilla, Edmar (NSN - AE/Dubai) > Cc: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] Policy to Manipulate the Local Preference of VPNV4 > routes > > Do you mean the same route being announced from two different PE's? A > unique RD for each VPN on each PE will help. Then I assume you working > with BGP import policy on the PE ... learning routes from the CE? > > On 30/05/2010, at 9:16 PM, Sorilla, Edmar (NSN - AE/Dubai) wrote: > >> Hi Experts, >> >> Please share if you know how to manipulate local preference of vpnv4 >> route >> >> Thanks, >> Edmar >> >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
