[j-nsp] Does a L3VPN RR require routing-instance for each VRF?

[Eric Van Tol]

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> bounces at puck.nether.net] On Behalf Of Phil Mayers
> Sent: Tuesday, November 29, 2011 7:38 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Does a L3VPN RR require routing-instance for each
> VRF?
> 
> As per subject line: if we want to use a JunOS box (M7i, running
> 10.4)
> as a route-reflector, it seems to reject inet-vpn routes with:
> 
> bgp_rcv_nlri: 129.x.x.0:4:193.x.x.0/92 rejected due to the lack of a
> valid target community
> 
> I was hoping we could avoid the hassle of defining the VRF on the RRs
> if
> possible, but I guess that is required - am I missing some obvious /
> subtle point why that is the case, or some way of making it work?

Basic question - I'm assuming that you have "cluster x.x.x.x" configured under the BGP group or individual BGP neighbor?  This is the only reason I could see this occurring, is if you were missing the cluster statement, or it was being overridden by something else.

-evt