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

Saku Ytti saku at ytti.fi
Thu Sep 29 07:29:42 EDT 2016

On 29 September 2016 at 10:09, Adam Vitkovsky
<Adam.Vitkovsky at gamma.co.uk> wrote:
> Since Junos can't generate update msg based on commonalities in egress policies (i.e. "dynamic update peer-groups"), I believe it will put each neighbour in its own update-group and generate update message for each peer independently, even though multiple peers might request the same set of RTs (i.e. have same set of egress policies).

I don't believe this is true.

You can do show 'show bgp group | match Name' and you should see which
neighbours are part of same update-group. You may have several
update-groups with same Name but different index and different set of


More information about the juniper-nsp mailing list