3.7.b Implement and troubleshoot IBGP and EBGP

bgp next-hop-self

the lab is beneath the arrow.

bgp_next-hop-self

down arrow smaller

bgp_next_hop_self

follow the instructions on the diagram carefully. below is the state you are achieving.

bgp_next-hop_sh_bgp

when i was just getting started with bgp next-hop-self gave me a friggin headache. next-hop-who, myself, hisself, next-hop-whoself?

note the asterisk for the 3 network. it’s valid but that dog don’t hunt. the next hop field is vital; from r2’s perspective, to get to r3’s 3 network it will have to bypass r1 completely and mysteriously find 100.1.1.3 to get to 3.3.3.3. it’s r1’s job to make it right. r1 IS THE next hop for r2 to get to r3.

R1(config-router)#neighbor 2.2.2.2 next-hop-self
R1(config-router)#!!! to get to 3.3.3.3, use me, abuse me!!!
R1(config-router)#

bgp_next-hop2r3

R2(config-router)#do ping 3.3.3.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/30/44 ms

i still don’t like next-hop-self…