Prevent route-reflector loops with cluster and originator attributes

Frame this document as a source-led configuration and assurance check: Prevent route-reflector loops with cluster and originator attributes. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• A route reflector creates ORIGINATOR_ID from the original speaker’s BGP Identifier, and a router should ignore a route whose ORIGINATOR_ID equals its own identifier. The research record locates this support at Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID.
• Each reflector must prepend its local cluster ID to CLUSTER_LIST and should ignore an advertisement whose list already contains that local ID. The research record locates this support at Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST.
• Route selection treats ORIGINATOR_ID as the advertising speaker’s identifier and should prefer the shorter CLUSTER_LIST before the next tie-break step. The research record locates this support at Section 9 (Impact on Route Selection).

Only the traced statements above are asserted as source facts. Apply the review to address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains after confirming that the source and deployed context match.

What the source does not establish

This RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. A correct source interpretation can still be inapplicable to a particular design. Confirm DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 9 (Impact on Route Selection), which observable configuration, record, or test can confirm applicability here?
• Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?
• Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and sanitize protected material before retention.

Verification and evidence

Build a reproducible chain from Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID; Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST; Section 9 (Impact on Route Selection) to the observed environment. Useful domain evidence includes configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results; label every item with scope, timestamp, collector, and stable identifier.

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

Official references

• RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) — RFC Editor / Internet Engineering Task Force