Question 550
At an enterprise core exchanging BGP routes over redundant WAN paths, a Junos specialist investigates this scenario: Two route reflectors use inconsistent cluster settings and reflected path behavior differs after failover. The chosen route must have a valid data-plane next hop. For which use case is this feature the best match?
Explanation
Correct Answer
For an enterprise core exchanging BGP routes over redundant WAN paths, this mechanism fits the requirement: Use consistent cluster-ID design for redundant route reflectors in one cluster. The design is appropriate because: Route reflector cluster identifiers participate in loop detection on reflected BGP paths. In this scenario, the observed issue is: Two route reflectors use inconsistent cluster settings and reflected path behavior differs after failover. The corresponding implementation is: Align the designed cluster identifier among redundant reflectors serving the same cluster.
Incorrect Answers
BGP NLRI family selection must include inet-unicast for eligible IPv4 unicast prefixes. The appropriate correction for the reported case is: Align the designed cluster identifier among redundant reflectors serving the same cluster.
A BGP prefix-limit control detects or constrains excessive received NLRI from a peer. Fixing that different mechanism would not address the current root cause: route reflector cluster identifiers participate in loop detection on reflected BGP paths.
Ordinary iBGP split-horizon rules avoid re-advertising routes between iBGP peers; route reflectors provide controlled reflection. Its verification is distinct from the reported condition: Two route reflectors use inconsistent cluster settings and reflected path behavior differs after failover. The chosen route must have a valid data-plane next hop.