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

 

393 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,

    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 R2_R3_R4 ebgp-multihop 2
     neighbor R2_R3_R4 update-source Loopback0
     neighbor 2.2.2.2 remote-as 2
     neighbor 2.2.2.2 peer-group R2_R3_R4
     neighbor 3.3.3.3 remote-as 3
     neighbor 3.3.3.3 peer-group R2_R3_R4
     neighbor 4.4.4.4 remote-as 4
     neighbor 4.4.4.4 peer-group R2_R3_R4
    
  2. Hi Adiel,

    These two lessons might help to understand what is going on:

    BGP Neighbor Adjacency States

    Troubleshooting BGP Neighbor Adjacency

    Is your router able to reach 2.2.2.2, 3.3.3.3 or 4.4.4.4? Are R2, R3 and R4 able to reach 1.1.1.1? That’s something to check. Make sure the BGP configuration on R2, R3 and R4 is also using the loopback address as the source of the connection and that multihop is configured.

    Rene

  3. 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?

  4. still not working how can they become ebgp nei if R1 using his src ip add as its loopack and R2,R3 n R4 using their src ip add as their physical interfaces …

    and by the way u added the static route for R 3 wd wrong next hop maybe
    R3(config)#ip route 1.1.1.1 255.255.255.255 192.168.13.3 the next hope must be 192.168.13.1

  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

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