[j-nsp] Limit content of bgp.l3vpn.0

[Dragan Jovicic]

Hi,

By default route-reflector will reflect/refresh all vpn routes to a PE
router, even if PE doesn't need those routes (doesn't import target
community).
Route-target family allows PE to give route-reflector a permission to send
only those routes for which import target exists.
The fact that this family works across all other vpn families (l2vpn,
inet-vpn, inet6-vpn, etc) make this almost a necessity in large networks.

BR,

Dragan

On Wed, Sep 28, 2016 at 4:05 PM, Dan Peachey <dan at peachey.co> wrote:

> On 28 September 2016 at 14:47, Saku Ytti <saku at ytti.fi> wrote:
> > On 28 September 2016 at 16:38, Johan Borch <johan.borch at gmail.com>
> wrote:
> >
> >> Will router-target-family work even if it is cisco in one end?
> >
> > Yes, IOS supports route-target SAFI.
> >
> > --
> >   ++ytti
>
>
> Hi,
>
> I may be missing something, but shouldn't the default behaviour be to
> drop all VPN routes that are not locally imported into a VRF? Unless
> you configure "keep all" or the PE is also configured as an RR.
>
> A quick test on a PE not running as an RR:
>
> Before "keep all" configured on the BGP group:
>
> --
> admin at lab1> show route table bgp.l3vpn.0
>
> bgp.l3vpn.0: 37 destinations, 37 routes (37 active, 0 holddown, 0 hidden)
> --
>
> After "keep all" configued on the BGP group:
>
> --
> admin at lab1> show route table bgp.l3vpn.0
>
> bgp.l3vpn.0: 165562 destinations, 165562 routes (165562 active, 0
> holddown, 0 hidden)
> --
>
> Cheers,
>
> Dan
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>