[j-nsp] router reflector clients and non-clients
sander at steffann.nl
Wed May 30 04:36:01 EDT 2018
> But in this scenario, a client will send an update both to RR1 and
> RR2, and RR1 will reflect this update to RR2, and RR2 will reflect it
> to RR1, and voila! We have a routing loop.
The moment it loops back to an RR that it has already been through it will see its own cluster-id in the list and ignore it. So RR1 and RR2 learn from each other, but the update won't loop.
More information about the juniper-nsp