A network engineer is troubleshooting a BGP route reachability issue. R1 learns the prefix 10.1.1.0/24 via eBGP from R2 with an AD of 20, and via OSPF from R3 with an AD of 110. The engineer notices that R1 installs the OSPF route in the routing table instead of the eBGP route, even though the eBGP route is preferred by default. What is the most likely cause of this behavior?
Trap 1: The OSPF route has a lower metric than the eBGP route.
Administrative distance is compared before metric; eBGP AD 20 is lower than OSPF AD 110 regardless of metric.
Trap 2: The OSPF route is an inter-area route, which has a lower AD than…
OSPF AD is fixed at 110 for all OSPF routes unless modified; inter-area does not change AD.
Trap 3: The eBGP route is not the best path because the next-hop is…
If the next-hop were unreachable, the route would not be installed at all, but the symptom states the OSPF route is installed, not that eBGP is missing.
- A
The OSPF route has a lower metric than the eBGP route.
Why wrong: Administrative distance is compared before metric; eBGP AD 20 is lower than OSPF AD 110 regardless of metric.
- B
The distance bgp 20 200 200 command is configured under the BGP process, increasing the AD of eBGP routes to 200.
This command sets the AD for eBGP routes to 200, making OSPF (AD 110) preferred.
- C
The OSPF route is an inter-area route, which has a lower AD than intra-area routes.
Why wrong: OSPF AD is fixed at 110 for all OSPF routes unless modified; inter-area does not change AD.
- D
The eBGP route is not the best path because the next-hop is unreachable.
Why wrong: If the next-hop were unreachable, the route would not be installed at all, but the symptom states the OSPF route is installed, not that eBGP is missing.