We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Full Access to our 568 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)


317 New Members signed up the last 30 days!


100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!


Forum Replies

  1. Well Done man. I was reading the same topic on the TCP/IP Vol II but the topology used there was quite confusing. Here you used a simple topology and explained to concept of it in a nice and clean way.

  2. Dear Rene,

    Nice explanation. I am bit confused about the use of the command bgp confederation identifier 2

    Should we use this command only to that router (R2) connecting to EBGP peers-R1 (the External Autonomous System, in this case 1 )?

    Or should we use the command also in the routers connecting to Sub-AS (inside the IBGP)?

    I saw you have used the command in all Routers. But do we need to use in all the sub-as routers? I am bit confused. Your help is highly appreciated.


  3. Hi Rene

    Thank you for this article.

    I had a question though

    When R1 advertises route to R2 that's external and learned via ebgp. For ibgp protocol states that next hop advertised by ebgp should be carried into ibgp. So when R1 advertises to R2 it uses next hop address as So when R2 advertises this route to its ibgp peers it should have next hop as and not as .
    Is this case we can also use next-hop-self command ? or using igp like ospf is the only option?

    thank you

  4. andrew says:

    Hi Kandhla,
    Yes, you can absolutely use the next-help-self option with iBGP. In fact, in some circumstances you might HAVE to. For example, let's say you have a router (R1) with an external BGP relationship with an ISP, and your highly available site has been given two separate circuits from that ISP. To ensure that R1's BGP neighborship with the ISP is also highly available, you have configured R1 to use the ISP's router's loopback address (you would also have to use the ebgp-multihop option for this). To do this you would create static routes on R1 to get to the ISP's loopback through both of your circuits.

    Now, suppose that R1 also has an iBGP relationship with other routers you have inside your company (say, R2 and R3). What would happen to all the routes that R1 would learn from the ISP, when it shares them with R2 and R3? The answer is that the routes would not appear in the routing table, and the reason is the next-hop attribute associated with the routes.

    In order for BGP to consider a route valid, the very first thing it checks for is the reachability of the next-hop address. From the perspective of R2 and R3, they have no idea how to get to the loopback of the ISP's BGP router. The best way to fix this would be to do what you said--turn on the "next-hop-self" option for R1.


12 more replies! Ask a question or join the discussion by visiting our Community Forum