Hi Guys,
Any mechanism in place on RR to prevent sending updates to client whom it
received from?
RRC1--------RR-------RRC2
Assume RR is configured with a peer-group, to which RRC1 and RRC2 belongs
if RRC1 sends update to RR, is there any mechanism on RR that prevents it
from replicating back towards RRC1?
I know there is a loop prevention on RRC1 in that if it sees its
originatorID/clusterID in the updates back from RR, RRC1 will drop it.
Trying to find out if there is a mechanism on RR itself that excludes RRC1
from the update/replication group.
Cheers
Ivan
Blogs and organic groups at http://www.ccie.net
Received on Wed Aug 07 2013 - 14:56:07 ART
This archive was generated by hypermail 2.2.0 : Sun Sep 01 2013 - 08:35:50 ART