Question 660
At an enterprise core exchanging BGP routes over redundant WAN paths, a Junos specialist investigates this scenario: A valid BGP path is present but a more preferred static route prevents that BGP path from being advertised. The chosen route must have a valid data-plane next hop. What protocol behavior accounts for this failure?
Explanation
Correct Answer
For an enterprise core exchanging BGP routes over redundant WAN paths, the governing mechanism is: Junos normally exports active routes; supported advertise-inactive can announce an eligible inactive BGP route in some cases. It explains the reported symptom: A valid BGP path is present but a more preferred static route prevents that BGP path from being advertised. The intended response is: Enable advertise-inactive only for the intentional peer context and test its effect. Verification: The neighbor receives the required BGP route despite a competing active non-BGP route.
Incorrect Answers
Junos BGP best-path logic generally prefers the external route when preceding comparisons tie. This alternative mechanism does not match the current fault.
BGP OPEN messages carry AS information and external peers must agree on their intended local and remote AS relationship. Fixing that different mechanism would not address the current root cause: junos normally exports active routes; supported advertise-inactive can announce an eligible inactive BGP route in some cases.
Route reflector cluster identifiers participate in loop detection on reflected BGP paths. Its verification is distinct from the reported condition: A valid BGP path is present but a more preferred static route prevents that BGP path from being advertised. The chosen route must have a valid data-plane next hop.