Question 770
At a managed network team troubleshooting an internet edge, a Junos specialist investigates this scenario: An iBGP session over loopbacks fails because the outgoing TCP connection uses a physical-interface source address. The diagnosis must distinguish a healthy BGP session from eligible received routes. What is the most likely design-related cause?
Explanation
Correct Answer
For a managed network team troubleshooting an internet edge, the governing mechanism is: Both ends of a loopback-based BGP session must reach and recognize the configured local addresses. It explains the reported symptom: An iBGP session over loopbacks fails because the outgoing TCP connection uses a physical-interface source address. The intended response is: Set the BGP local-address to the intended routable loopback and verify remote peer configuration. Verification: show BGP neighbor reports the expected local source and established peer endpoint.
Incorrect Answers
Route reflector cluster identifiers participate in loop detection on reflected BGP paths. This alternative mechanism does not match the current fault.
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.
BGP MED can signal a preferred ingress point to a neighboring AS subject to the neighbor's selection policy. 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 diagnosis must distinguish a healthy BGP session from eligible received routes.