One campus router learns a cloud prefix by eBGP. A second campus router never sees it. There is no iBGP session between the two campus routers. Both can reach the cloud tunnel router. What is missing?
Select an answer to reveal the explanation.
Short Explanation
The first campus router has the prefix and has nobody to tell. You add iBGP between the two campus routers so the prefix can be passed. The second router can already reach the tunnel, and it was never offered the route.
Full Explanation
eBGP on one campus router does not automatically populate the other campus router. Without iBGP the second router never sees the cloud prefix, even though it can reach the tunnel. Build the iBGP session and make sure the next hop is reachable from the second router. A second eBGP session from the cloud is optional redundancy. It is not required for the first router to share what it already learned, and iBGP can carry that prefix. The virtual private gateway does not run OSPF between the campus routers. The IKE lifetime does not advertise routes. Exam caveat: iBGP split horizon means this session shares the prefix between these two routers. It does not, by itself, feed a third campus router that is only their peer. Operational check: show ip bgp summary on both campus routers should show the iBGP session Established, and the second router should install the cloud prefix.