From: Voss, David (dvoss@heidrick.com)
Date: Sat Feb 15 2003 - 00:11:10 GMT-3
ebgp multihop is required for systems that are not in the same AS, so that
will not resolve this problem. next-hop-self is a good idea for
advertisement within an as, but won't solve this problem.
you have two options here:
#1, change the nei statements to point to the serial interface ip address of
the nei
or
#2, make sure each router can ping the loopback of the other router before
troubleshooting bgp via additional static route statements
remember, when creating bgp neighbors, you MUST have connectivity to the nei
ip you are programming in your router bgp statement. to say 'nei 1.1.1.1'
and then not have connectivity to 1.1.1.1 is taking the cart before the
horse.
the horse... connectivity to the loopback
the cart... neighbor statements to the loopback
don't forget update-source loopback0 in a neighbor statement for good
measure.
-----Original Message-----
From: D. J. Jones [mailto:meganac@attbi.com]
Sent: Friday, February 14, 2003 8:36 PM
To: Janto Cin; sascha.lemberg@degussa.com
Cc: ccielab@groupstudy.com; nobody@groupstudy.com
Subject: Re: Antwort: BGP neighbor
I believe you need to use ebgp-multihop since the interface you want to peer
with is not directly connected.
----- Original Message -----
From: "Janto Cin" <jantocin@datacomm.co.id>
To: <sascha.lemberg@degussa.com>
Cc: <ccielab@groupstudy.com>; <nobody@groupstudy.com>
Sent: Friday, February 14, 2003 4:24 AM
Subject: Re: Antwort: BGP neighbor
> still doesn't solve the problem.
> any idea?
> btw thanks for your reply.
>
> janto
> ----- Original Message -----
> From: <sascha.lemberg@degussa.com>
> To: "Janto Cin" <jantocin@datacomm.co.id>
> Cc: <ccielab@groupstudy.com>; <nobody@groupstudy.com>
> Sent: Friday, February 14, 2003 7:17 PM
> Subject: Antwort: BGP neighbor
>
>
>
> add an next-hop-self entry.
>
> router bgp 1
> neighbor 44.1.1.1 remote 1
> neighbor 44.1.1.1 update lo0
> neighbor 44.1.1.1 next-hop-self
>
> router bgp 1
> neighbor 10.33.1.1 remote 1
> neighbor 10.33.1.1 update lo0
> neighbor 10.33.1.1 next-hop-self
>
>
>
> Mit freundlichen Gr|_en / Best regards
>
>
> Sascha Lemberg
>
>
> its.on
> Global Network Services
> T +49.(0)69 218 5663
> E-Mail: sascha.lemberg@degussa.com
>
>
>
>
>
>
> "Janto Cin"
> <jantocin@datac An:
<ccielab@groupstudy.com>
> omm.co.id> Kopie:
> Gesendet von: Thema: BGP neighbor
> nobody@groupstu
> dy.com
>
>
> 14.02.2003
> 13:04
>
> Bitte antworten
> an "Janto Cin"
>
>
>
>
>
> Dear All,
>
> Please help on my problem below:
>
> (lo0)R1(s0)-------------(s0)R2(lo0)
>
> R1(lo0): 10.33.1.1/24
> R1(s0): 173.168.40.1/24
> R2(s0): 173.168.40.2/24
> R2(lo0): 44.1.1.1/24
>
> R1
> ----
> ip route 0.0.0.0 0.0.0.0 173.168.40.2
>
> router bgp 1
> neighbor 44.1.1.1 remote 1
> neighbor 44.1.1.1 update lo0
>
> R2
> ----
> ip route 0.0.0.0 0.0.0.0 173.168.40.1
>
> router bgp 1
> neighbor 10.33.1.1 remote 1
> neighbor 10.33.1.1 update lo0
>
> I can ping R1 lo0 from R2 and vice-versa, but why the bgp connection still
> not
> established?
> I turn on debug ip bgp on both routers and get this:
> on R1
> --------
> 01:45:46: BGP: 44.1.1.1 multihop open delayed 17789ms (no route)
>
> on R2
> --------
> 01:35:20: BGP: 10.33.1.1 multihop open delayed 11888ms (no route)
>
>
> TIA,
> Janto
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:24 GMT-3