Question

An engineer configures eBGP between two directly connected routers, R1 (AS 100) and R2 (AS 200), using the interface IP addresses on the shared 10.1.1.0/30 link. R2 advertises 192.168.50.0/24 to R1. On R1, the BGP table shows the 192.168.50.0/24 prefix as valid but with a status of 'inaccessible' and it is not installed in the routing table. The neighbor is in the Established state and other prefixes are learned fine. What is the MOST likely cause?

Accepted Answer

R1 has no route to reach the BGP next-hop address advertised for 192.168.50.0/24, so the recursive lookup fails

Answer

The eBGP session requires the 'ebgp-multihop' command because the routers are directly connected

Answer

R2 must be configured with 'next-hop-self' for the eBGP session to install the prefix

Answer

The prefix is being filtered by an inbound distribute-list on R1