Question 200
At a dual-homed business network peering with two upstream providers, a Junos specialist investigates this scenario: A BGP update is received but appears hidden because the announced next-hop address cannot be resolved in the routing table. The routing policy must retain intended primary and backup paths. Which limitation should guide the change control?
Explanation
Correct Answer
For a dual-homed business network peering with two upstream providers, the relevant safeguard is: Avoid setting next hop to self without confirming the chosen egress can actually forward the traffic. It matters while implementing: Repair the underlay route to the received BGP next hop or apply a deliberate next-hop policy. The fault involves: A usable BGP route requires an eligible reachable forwarding next hop before it can become active. The required acceptance result remains: show route hidden detail no longer reports an unreachable next hop and the prefix becomes eligible.
Incorrect Answers
BGP export policy controls which eligible active routes the speaker announces to selected neighbors. The appropriate correction for the reported case is: Avoid setting next hop to self without confirming the chosen egress can actually forward the traffic.
BGP AS-path loop detection normally prevents accepting routes already traversing the local autonomous system. Fixing that different mechanism would not address the current root cause: a usable BGP route requires an eligible reachable forwarding next hop before it can become active.
IBGP propagation may retain the original eBGP next-hop attribute unless policy or configuration changes it. Its verification is distinct from the reported condition: A BGP update is received but appears hidden because the announced next-hop address cannot be resolved in the routing table. The routing policy must retain intended primary and backup paths.