On 29 September 2016 at 10:09, Adam Vitkovsky <adam.vitkov...@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 neighbours. -- ++ytti _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
