Hi, > 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. Cheers, Sander
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
