VPNv4 prefixes that do not match import filters for any configured VRF will
get filtered by default. In certain situations, such as on
route-reflectors, this will cause issues.
You can disable the behavior with:
'no bgp default route-target filter'
Try configuring that on R3 (I'm assuming it is disabled by on R1 by virtue
of its RR configuration).
-Yuri
*-*
On Wed, Mar 6, 2013 at 10:34 PM, Kalpesh Chheda <kalpeshchheda_at_live.com>wrote:
> I have 3 routers connected serially. All three routers are PE.
>
> R1 ---- R2 ---- R3
>
> R1 is exporting some routes and R3 is importing that routes. R2 and R3 are
> able to see vpnv4 routes in there vpnv4 table.
>
> But if R3 stops importing routes from R1 in to is VRF table. Routes are
> not even seen in its VPNv4 table. why?
>
> Because R2 have that VPNv4 routes by R1 in its table whether it is
> importing or not. p 5
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Wed Mar 06 2013 - 22:57:40 ART
This archive was generated by hypermail 2.2.0 : Wed Apr 03 2013 - 19:06:19 ART