From: Georg Pauwen (pauwen@hotmail.com)
Date: Sat Feb 15 2003 - 06:51:24 GMT-3
Hello Janto,
I rebuilt your config and had the same problem until on one router I put in
a specific static route instead of the default 0.0.0.0. So instead of
ip route 0.0.0.0 0.0.0.0 173.168.40.1
on R2 I added
ip route 10.33.1.1 255.255.255.255 173.168.40.1
That brought up the neighbor right away. Once the BGP relationship was
established, I could even remove the more specific route and just leave the
default in. Not sure what happens, but I got it working that way.
Regards,
Georg
>From: "Janto Cin" <jantocin@datacomm.co.id>
>Reply-To: "Janto Cin" <jantocin@datacomm.co.id>
>To: <ccielab@groupstudy.com>
>Subject: BGP neighbor
>Date: Fri, 14 Feb 2003 19:04:30 +0700
>
>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