Objectives
The simulator ticks each one as soon as the network meets it.
On R1, read display bgp peer while the session to 3.3.3.3 is down.
Fix R1: source the session to 3.3.3.3 from LoopBack0 (peer 3.3.3.3 connect-interface LoopBack0). It reaches Established.
R1 learns 8.8.8.0/24 with next hop 10.0.34.4, which OSPF does not know. Fix it on R3: peer 1.1.1.1 next-hop-local. R1 installs the route.
PC1 pings 8.8.8.8.
Rate this lab
No ratings yet.
Sign in to rate this lab and keep track of the labs you finish.
Before you start
An iBGP session between loopbacks must be sourced from the loopback on both ends (connect-interface), or each side sees the other arrive from an unexpected address. iBGP keeps the eBGP next hop unchanged; next-hop-local on the border router replaces it with its own address.
Concept
iBGP: update-source and next-hop-self
Inside one AS, routers share BGP routes over iBGP. Two details trip people up: sessions should run between loopbacks so they survive a link failure, and iBGP keeps the external next hop, which internal routers may not be able to reach.