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.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 622 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

401 New Members signed up the last 30 days!

satisfaction-guaranteed

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

Tags:


Forum Replies

  1. Rene,

    If this has been answered by other members I apologize but following your example, the RR works as configured as R3 does learn about the 1.1.1.1/32 prefix but its not being installed in the routing table because it can not reach the next hop address of 192.168.12.1. To resolve this I added the next-hop-self command on R1 and reset the BGP peerings. That still did not resolve this.

    My question is once a RR is configured should all the clients update their next hop to the RR or should the originator of the prefix have the next-hop-self configuration?

    R3#sh 
    ... Continue reading in our forum

  2. Hi Michael,

    In this example R1 originates the prefix so the next hop is 192.168.12.1.

    R2 will reflect this prefix to R3 but it doesn’t change the next hop. Using next-hop self on R1 won’t help here since 192.168.12.1 is already the next hop IP address.

    The route reflector will reduce the number of iBGP peerings but that’s it :slight_smile:

    About your question, let’s imagine that R1 learns 1.1.1.1/32 from an eBGP router. In this case, it would be better to make R1 the RR and use “next hop self” for all other iBGP routers. That would ensure that all iBGP neighbors learn the pr

    ... Continue reading in our forum

  3. Udaya,
    In the case of a router’s being a route reflector client of multiple route reflectors, the client will accept routes from all reflectors. In other words, all learned routes will be present in the BGP topology table. As far as which routes are selected as best routes, and installed in the routing table, the client will use the standard (and complex!) BGP best path selection algorithm.

  4. I need a bit of help, I can’t seem to get this working on Real Equip or GNS3

    I have the following setup; http://imgur.com/a/ZLqCl

    But R1 still cannot ping the 192.168.0.1 address assigned on loopback 0 on R3. I’ve got some outputs below, let me know if you need more :slight_smile: Hope someone can help me figure what i’ve done wrong

    R1 - http://paste.ubuntu.com/23460781/ http://paste.ubuntu.com/23460783/
    R2 - http://paste.ubuntu.com/23460788/ http://paste.ubuntu.com/23460789/
    R3 - http://paste.ubuntu.com/23460791/ http://paste.ubuntu.com/23460793/

    What I can see is R1 is sho

    ... Continue reading in our forum

  5. Hey Ryan,
    The issue you are having is that while R1 knows about the BGP route to R3, it is not installing it into the routing table. You can verify this by going on to R1 and issuing a “show ip bgp” and look for the 192.168.0.0 route (it will be missing the “>” symbol).

    The reason R1 is not installing the route is due to BGP behaving differently than other routing protocols. BGP really isn’t a true routing protocol in the way that OSPF or EIGRP are. BGP is more of an application that tells you WHERE to go to get to a network, but it does not tell HOW to get

    ... Continue reading in our forum

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