From: Lupi, Guy (Guy.Lupi@eurekaggn.com)
Date: Mon Oct 14 2002 - 19:26:50 GMT-3
From the following link:
http://www.cisco.com/warp/public/459/16.html#A24.0
Usually, a cluster of clients will have a single RR. In this case, the
cluster will be identified by the router ID of the RR. In order to increase
redundancy and avoid single points of failure, a cluster might have more
than one RR. All RRs in the same cluster need to be configured with a 4 byte
cluster-id so that a RR can recognize updates from RRs in the same cluster.
A cluster-list is a sequence of cluster-ids that the route has passed. When
a RR reflects a route from its clients to non-clients outside of the
cluster, it will append the local cluster-id to the cluster-list. If this
update has an empty cluster-list the RR will create one. Using this
attribute, a RR can identify if the routing information is looped back to
the same cluster due to poor configuration. If the local cluster-id is found
in the cluster-list, the advertisement will be ignored.
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:47 GMT-3