Question 540
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. When would the described mechanism be appropriate?
Explanation
Correct Answer
For a managed network team troubleshooting an internet edge, this mechanism fits the requirement: Use stable loopback addresses for resilient internal BGP sessions. The design is appropriate because: Both ends of a loopback-based BGP session must reach and recognize the configured local addresses. In this scenario, the observed issue is: An iBGP session over loopbacks fails because the outgoing TCP connection uses a physical-interface source address. The corresponding implementation is: Set the BGP local-address to the intended routable loopback and verify remote peer configuration.
Incorrect Answers
A nonadjacent eBGP neighbor may require a compatible multihop TTL and suitable route to the remote endpoint. The appropriate correction for the reported case is: Set the BGP local-address to the intended routable loopback and verify remote peer configuration.
IBGP requires compatible local and remote AS settings, TCP reachability and correct neighbor addresses. 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 address-family negotiation determines whether IPv6 unicast NLRI can be exchanged. 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. When would the described mechanism be appropriate.