From: Norma Schutt (nschutt@xxxxxxxxxxxxxxxxx)
Date: Sat May 05 2001 - 02:48:54 GMT-3
I read somewhere but can't remember where it was now that you can't use a
default route to set up your EBGP sessions. If you aren't using the
directly connected interfaces, then you must have a specific route to the
EBGP neighbor's loopback.
3 days and 7 hours.......
Norma Schutt
At 10:55 AM 5/4/2001, mcaplan.cs@clearstream.com wrote:
>HI,
>
>I have a very simple set up
>
>(lo 0)R1----frame PVC-----R2(lo 0)
>
>Configs ar shown below. I am setting up EBGP between R1 and R2, using Lo 0
>as the peer IP address in both cases. I can do an extended ping from R1 to
>R2 usng Lo 0 as the source address. The neighbor relationship however will
>not progress beyond active.
>The following is the output from debug ip bgp
>
>03:59:52: BGP: 11.11.11.11 multihop open delayed 19344ms (no route)
>
>There is a route, but it just happens to be the default route. It all works
>fine if I put a more precise route onto R1 or R2. Why does it fail with
>default routes, when extended ping works fine ?
>
>
>R1
>
>interface Loopback0
> ip address 10.10.10.10 255.255.255.255
> no ip directed-broadcast
>!
>interface Serial0
> ip address 12.1.1.1 255.0.0.0
> no ip directed-broadcast
> encapsulation frame-relay
>!
>router bgp 1
> neighbor 11.11.11.11 remote-as 2
> neighbor 11.11.11.11 ebgp-multihop 255
> neighbor 11.11.11.11 update-source Loopback0
>!
>ip classless
>ip route 0.0.0.0 0.0.0.0 12.2.2.2
>
>Gateway of last resort is 12.2.2.2 to network 0.0.0.0
>
> 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
>C 10.10.10.10/32 is directly connected, Loopback0
>C 10.1.0.0/16 is directly connected, TokenRing0
>C 12.0.0.0/8 is directly connected, Serial0
>S* 0.0.0.0/0 [1/0] via 12.2.2.2
>
>R2
>
>interface Loopback0
> ip address 11.11.11.11 255.255.255.255
> no ip directed-broadcast
>!
>interface Serial0
> ip address 12.2.2.2 255.0.0.0
> no ip directed-broadcast
> encapsulation frame-relay
> no ip route-cache
> no ip mroute-cache
> logging event subif-link-status
> logging event dlci-status-change
> no fair-queue
> clockrate 2000000
>!
>router bgp 2
> neighbor 10.10.10.10 remote-as 1
> neighbor 10.10.10.10 ebgp-multihop 255
> neighbor 10.10.10.10 update-source Loopback0
>!
>ip classless
>ip route 0.0.0.0 0.0.0.0 12.1.1.1
>
>Gateway of last resort is 12.1.1.1 to network 0.0.0.0
>
> 11.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
>C 11.11.11.11/32 is directly connected, Loopback0
>C 11.1.0.0/16 is directly connected, Ethernet0
>C 12.0.0.0/8 is directly connected, Serial0
>S* 0.0.0.0/0 [1/0] via 12.1.1.1
>
>
>Any advice with this strange behaviour ?
>
>Cheers
>
>Mark
>
>
>Visit us at http://www.clearstream.com
>
>IMPORTANT MESSAGE
>
>Internet communications are not secure and therefore Clearstream
>International does not
>accept legal responsibility for the contents of this message.
>
>The information contained in this e-mail is confidential and may be
>legally privileged. It is
>intended solely for the addressee. If you are not the intended recipient,
>any disclosure,
>copying, distribution or any action taken or omitted to be taken in
>reliance on it, is
>prohibited and may be unlawful. Any views expressed in this e-mail are
>those of the
>individual sender, except where the sender specifically states them to be
>the views of
>Clearstream International or of any of its affiliates or subsidiaries.
>
>END OF DISCLAIMER
>**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:34 GMT-3