Glad the video helped clear things up for you, and thanks so much for subscribing! Best of luck with your CCNP studies-keep up the hard work, and feel free to reach out if you have any questions along the way!
Hi Lazaros! If R2 wants to join 20.20.20.0/24, the route installed in the routing table will be learned from another routing protocol with a lower AD right? Like OSPF, or directly connected. Are there any case where iBGP installs such a route in the routing table? In other words, a redistributed route will always have a better AD than iBGP so it won't be chosen. What do I miss? Cheers
If we were to look at the routing table of R2, it is likely that we would see the 20.20.20.0/24 as a directly connected network. The iBGP learned route (which is learned because of the `network` command) appears in the BGP table, but does not get installed in the routing table, because iBGP has an AD of 200 while directly connected routes have an AD of 0. So you're right, as far as the routing table goes, that is what would happen. But looking at the BGP table, you will still find that the route is learned via BGP and the route is advertised to other iBGP peers as a result. So are there any cases wherre iBGP will install this route in the routing table? Yes, if the link between R2 and the 20.20.20.0/24 network fails, then that iBGP route will indeed enter the routing table. But remember, other than allowing R2 to get to that route, the purpose of iBGP is also to advertise that route to the rest of the AS, and in turn, via eBGP, to advertise that route to other ASes. Does that make sense?
Interesting one. I have read subjects about EIGRP Split Horizon feature but I am unsure about "iBGP Split Horizon" as you have called it in the video. Would you please explain a bit about this term or maybe make a video about it ?
Hello again! Yes, I'll create a video about iBGP split horizon. For now I can tell you that the iBGP split horizon rule prevents a router from advertising a route back to the peer from which it was learned. This mechanism avoids routing loops within an AS by ensuring that routes are not propagated indefinitely among iBGP peers. More to come in a future video!
@@telecomTech.explained Many Thanks! So if I get it right, I think the idea about iBGP Split Horizon is somehow similar to EIGRP Split Horizon as in EIGRP Split Horizon, router will not advertise back the update it received from a particular neighbor.
Best explanations for BGP to date for me
Thanks so much for your kind words. I do my best!
You hav cleared my doubt so well, i am so thankful for your videos
I'm so happy that the video was so helpful for you! I'm thankful for your comment!
Studying for my CCNP currently. This video helped to clear any confusion I had. Thank you :) Just subscribed!
Glad the video helped clear things up for you, and thanks so much for subscribing! Best of luck with your CCNP studies-keep up the hard work, and feel free to reach out if you have any questions along the way!
Thanks very much for sharing, I just found out about your youtube page and I have just subscribed.
Hello Benedict! Great, thanks for subscribing! I hope you find the content useful!
Hi Lazaros! If R2 wants to join 20.20.20.0/24, the route installed in the routing table will be learned from another routing protocol with a lower AD right? Like OSPF, or directly connected. Are there any case where iBGP installs such a route in the routing table?
In other words, a redistributed route will always have a better AD than iBGP so it won't be chosen. What do I miss?
Cheers
If we were to look at the routing table of R2, it is likely that we would see the 20.20.20.0/24 as a directly connected network. The iBGP learned route (which is learned because of the `network` command) appears in the BGP table, but does not get installed in the routing table, because iBGP has an AD of 200 while directly connected routes have an AD of 0. So you're right, as far as the routing table goes, that is what would happen.
But looking at the BGP table, you will still find that the route is learned via BGP and the route is advertised to other iBGP peers as a result.
So are there any cases wherre iBGP will install this route in the routing table? Yes, if the link between R2 and the 20.20.20.0/24 network fails, then that iBGP route will indeed enter the routing table. But remember, other than allowing R2 to get to that route, the purpose of iBGP is also to advertise that route to the rest of the AS, and in turn, via eBGP, to advertise that route to other ASes. Does that make sense?
Interesting one. I have read subjects about EIGRP Split Horizon feature but I am unsure about "iBGP Split Horizon" as you have called it in the video. Would you please explain a bit about this term or maybe make a video about it ?
Hello again! Yes, I'll create a video about iBGP split horizon. For now I can tell you that the iBGP split horizon rule prevents a router from advertising a route back to the peer from which it was learned. This mechanism avoids routing loops within an AS by ensuring that routes are not propagated indefinitely among iBGP peers. More to come in a future video!
@@telecomTech.explained Many Thanks! So if I get it right, I think the idea about iBGP Split Horizon is somehow similar to EIGRP Split Horizon as in EIGRP Split Horizon, router will not advertise back the update it received from a particular neighbor.