Network & Infrastructure / BGP Policy & Internet Edge
Detect route-reflector cluster-ID and originator suppression
A reflected route disappears at one client despite healthy sessions and apparently permissive route maps. The omission can result from loop-prevention attributes rather than prefix filtering.
Environment and inputs: BGP speakers and route reflectors; policy syntax, RPKI integration and address-family behavior depend on the implementation. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Record originator ID, cluster list, router IDs and reflector client relationships for the missing prefix. Compare the same attributes before and after each reflection boundary.
Explain the result
A router suppresses routes that indicate a reflection loop. Reused identifiers or an unintended reflector hierarchy can make a legitimate path look like its own reflected advertisement.
Plan the fix
Correct identifier ownership and the documented reflection topology through a coordinated change. Do not strip loop-prevention attributes to force acceptance of the route.
Check the result and rollback
Verify both redundant reflection paths and deliberately test an exit failure in a maintenance exercise. Restore the prior topology if route propagation becomes cyclic or duplicate advertisements grow unexpectedly.