Question 270
At an enterprise core exchanging BGP routes over redundant WAN paths, a Junos specialist investigates this scenario: An iBGP session over loopbacks fails because the outgoing TCP connection uses a physical-interface source address. The chosen route must have a valid data-plane next hop. Which configuration adjustment should be made first to address this issue?
Explanation
Correct Answer
For an enterprise core exchanging BGP routes over redundant WAN paths, the direct corrective action is: Set the BGP local-address to the intended routable loopback and verify remote peer configuration. This addresses the mechanism: Both ends of a loopback-based BGP session must reach and recognize the configured local addresses. Confirm by checking: show BGP neighbor reports the expected local source and established peer endpoint. During rollout, ensure underlay IGP reachability to loopbacks before pinning the session source.
Incorrect Answers
BGP AS-path loop detection normally prevents accepting routes already traversing the local autonomous system. The appropriate correction for the reported case is: Set the BGP local-address to the intended routable loopback and verify remote peer configuration.
AS-path prepending lengthens a path in selected outbound advertisements and may influence upstream BGP selection. Fixing that different mechanism would not address the current root cause: both ends of a loopback-based BGP session must reach and recognize the configured local addresses.
Junos BGP best-path logic generally prefers the external route when preceding comparisons tie. Its verification is distinct from the reported condition: An iBGP session over loopbacks fails because the outgoing TCP connection uses a physical-interface source address. The chosen route must have a valid data-plane next hop.