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 619 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

414 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!


Forum Replies

  1. Hi Rene,

    I think that in configuration there is missing a static route to each of the peer’s loopback addresses.

    George

  2. Hi George,

    That’s right, this example only shows a “before” and “after” of using peer groups. You will need static routes to reach the loopback addresses of the remote peers.

    Rene

  3. Hi,

    I have a problem in R1 he doesn’t create any neighbor relationship:

    These are the logs:

    *Jul  9 17:58:35.187: BGP: ses global 3.3.3.3 (0x655EF9CC:0) act Reset (Active open failed).
    *Jul  9 17:58:35.199: BGP: 3.3.3.3 active went from Active to Idle
    *Jul  9 17:58:35.199: BGP: nbr global 3.3.3.3 Active open failed - open timer running
    *Jul  9 17:58:35.203: BGP: nbr global 3.3.3.3 Active open failed - open timer running
    

    Example for R3 but it’s the same for R2 and R4:

    router bgp 1
     bgp log-neighbor-changes
     neighbor R2_R3_R4 peer-group
     neighbor
    ... Continue reading in our forum

  4. Hi Zeko,

    I just added the static routes to the post, those are indeed required.

    Which exact commands did you remove? Do you still have your final config?

  5. Hi Zeko,

    I see it now, the final configs of R2, R3, and R4 were wrong. They have to use 1.1.1.1 as the destination and source BGP from their own loopbacks. Just fixed this. Sorry for the confusion!

    Rene

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