Question 60
At the Harborview media campus, R-HAR-DIST1 must peer by eBGP with a reachable loopback on R-INL-DIST2 multiple routed hops away; TCP never reaches Established using default TTL behavior. Which operational change most directly addresses the fault described?
Explanation
Correct Answer
The fault at the Harborview media campus has a specific cause. The default eBGP directly connected peer assumptions do not support this multiple-hop session. Configure eBGP multihop and reliable loopback reachability for the non-direct peer as appropriate. Confirm success against this result: BGP reaches Established over the loopback path and exchanges authorized prefixes.
Incorrect Answers
This is appropriate for a different routing or network-control issue: BGP local preference is examined before AS-path length, and the present attributes favor the wrong exit. The stated evidence at the Harborview media campus instead concerns ebgp non-direct neighbor multihop.
This could help where ibgp next-hop reachability is the issue, but not for the evidence reported at the Harborview media campus. The default eBGP directly connected peer assumptions do not support this multiple-hop session.
That change targets bgp inbound prefix filtering, not the reported ebgp non-direct neighbor multihop fault at the Harborview media campus. The default eBGP directly connected peer assumptions do not support this multiple-hop session.