Question 260
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 underlying technical condition best accounts for this evidence?
Explanation
Correct Answer
The default eBGP directly connected peer assumptions do not support this multiple-hop session. That explains the specific symptom at the Harborview media campus. A direct corrective action is: Configure eBGP multihop and reliable loopback reachability for the non-direct peer as appropriate.
Incorrect Answers
That diagnosis belongs to bgp inbound prefix filtering, while the observation at the Harborview media campus points to ebgp non-direct neighbor multihop.
The observation at the Harborview media campus does not point to bgp local preference path policy; it points to a different condition. The default eBGP directly connected peer assumptions do not support this multiple-hop session.
That diagnosis belongs to ibgp next-hop reachability, while the observation at the Harborview media campus points to ebgp non-direct neighbor multihop.