03-13-2021 03:13 AM - edited 03-13-2021 03:16 AM
Hi guys, i am trying to implement a simple bgp example with all ibgp peers having full mesh connectivity. i have tried putting in a static route on R2 for the 10.1.14.0 network, and on R4 . still cannot reach 10.1.14.1 or 1.1.1.1 but can reach 10.1.14.2. r3 can reach both 4.4.4.4 and 10.1.14.1. i got it to work by adding a static route on R4 and redistributing it but i dont think that is a correct way. did not want to use igp's or route reflector.
Solved! Go to Solution.
03-13-2021 07:50 AM - edited 03-13-2021 10:44 AM
Hi Friend,
from R2 ping 10.1.14.1 but 10.1.14.2 not?
why ?
because R1 don't have return back to R2.
R2 will use as source of ping 10.1.23.2, and 10.1.14.1 as destination.
R3 will forward it know this to R4
R4 will forward it to R1
here R1 don't know about 10.1.23.0, so the packet drop.
you not share the Routing table of R1 but i sure this is issue here
03-13-2021 12:43 PM
Hello
For full ibgp connectivity use an igp such as eigrp/ospf to provide NLRI between all peers,Otherwise incorporate Route Reflectors.
03-13-2021 05:55 AM
if I am right
in R4
you need
next-hop-self toward R3
"neighbor R3 next-hop-self"<-this command
03-13-2021 07:20 AM
that is already there
03-13-2021 07:50 AM - edited 03-13-2021 10:44 AM
Hi Friend,
from R2 ping 10.1.14.1 but 10.1.14.2 not?
why ?
because R1 don't have return back to R2.
R2 will use as source of ping 10.1.23.2, and 10.1.14.1 as destination.
R3 will forward it know this to R4
R4 will forward it to R1
here R1 don't know about 10.1.23.0, so the packet drop.
you not share the Routing table of R1 but i sure this is issue here
03-13-2021 12:43 PM
Hello
For full ibgp connectivity use an igp such as eigrp/ospf to provide NLRI between all peers,Otherwise incorporate Route Reflectors.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide