Solved

a question with BGP loopback neighbor establishement

Posted on 2011-09-14
6
1,199 Views
Last Modified: 2012-05-12
hello,

i have 2 routers on GNS3, i want to configure BGP based on the loopback of each router, but it never comes to Established status, it is stuck in "Active" here is my topology:


                               R1 =================
                                                                   //================== R2

Config:

R1:

R1#show run
Building configuration...

Current configuration : 1048 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
ip cef
no ip domain lookup
!
!
!
!        
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
 ip address 1.1.1.1 255.255.255.0
!        
interface Serial0/0
 ip address 192.168.12.1 255.255.255.0
 serial restart-delay 0
!
interface Serial0/1
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial0/2
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial0/3
 no ip address
 shutdown
 serial restart-delay 0
!
router bgp 1
 no synchronization
 bgp router-id 1.1.1.1
 bgp log-neighbor-changes
 network 192.168.12.0
 neighbor 2.2.2.2 remote-as 2
 neighbor 2.2.2.2 ebgp-multihop 2
 neighbor 2.2.2.2 update-source Loopback1
 no auto-summary
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!        
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

R1#

=================================================================


R2:

R2#show run
Building configuration...

Current configuration : 1048 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
ip cef
no ip domain lookup
!
!
!
!        
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
 ip address 2.2.2.2 255.255.255.0
!        
interface Serial0/0
 ip address 192.168.12.2 255.255.255.0
 serial restart-delay 0
!
interface Serial0/1
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial0/2
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial0/3
 no ip address
 shutdown
 serial restart-delay 0
!
router bgp 2
 no synchronization
 bgp router-id 2.2.2.2
 bgp log-neighbor-changes
 network 192.168.12.0
 neighbor 1.1.1.1 remote-as 1
 neighbor 1.1.1.1 ebgp-multihop 2
 neighbor 1.1.1.1 update-source Loopback1
 no auto-summary
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!        
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

R2#

0
Comment
Question by:zakar1a
  • 3
  • 3
6 Comments
 
LVL 24

Expert Comment

by:Ken Boone
Comment Utility
The problem is that either router does not have a route to the other's BGP loopback address.  You have to be able to at least reach your BGP peer and right now you cannot.  Add a static route on each router to reach the other's BGP peer ip address and then it should come up.
0
 
LVL 7

Author Comment

by:zakar1a
Comment Utility
i got this from debug:


*Mar  1 01:24:06.947: BGP: 2.2.2.2 active open failed - no route to peer, open active delayed 26593ms (35000ms max, 28% jitter)
0
 
LVL 24

Accepted Solution

by:
Ken Boone earned 500 total points
Comment Utility
That is exactly what I mean:

On rtr 1 you need:
ip route 2.2.2.2 255.255.255.0 192.168.12.2

On rtr 2 you need:
ip route 1.1.1.1 255.255.255.0 192.168.12.1

Then each router will have a route to the other's loopback and then it will come up.
0
Network it in WD Red

There's an industry-leading WD Red drive for every compatible NAS system to help fulfill your data storage needs. With drives up to 8TB, WD Red offers a wide array of solutions for customers looking to build the biggest, best-performing NAS storage solution.  

 
LVL 7

Author Comment

by:zakar1a
Comment Utility
you meant :

ip route 2.2.2.2 255.255.255.255 192.168.12.2
ip route 1.1.1.1 255.255.255.255 192.168.12.1

right?
0
 
LVL 24

Expert Comment

by:Ken Boone
Comment Utility
yea correct.
0
 
LVL 7

Author Closing Comment

by:zakar1a
Comment Utility
thank you
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

In the world of WAN, QoS is a pretty important topic for most, if not all, networks. Some WAN technologies have QoS mechanisms built in, but others, such as some L2 WAN's, don't have QoS control in the provider cloud.
PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now