From: Stephen C. Feldberg (scfeldberg@xxxxxxxxxxx)
Date: Thu Dec 13 2001 - 16:40:05 GMT-3
I believe that the router that originates the session must have the
destination peer network in it's routing table. In a scenario with only 1
static route, only that peer will be able to initiate the BGP session.
I don't know what implications this has on the BGP session, if any. That's
a good question for the group.
Steve
----- Original Message -----
From: "Krake, Kris" <KKrake@AEGONUSA.com>
To: "Stephen C. Feldberg" <scfeldberg@hotmail.com>
Sent: Thursday, December 13, 2001 2:22 PM
Subject: RE: bgp peering
> I haven't seen this documented anywhere. Makes sense I suppose but I
> figured I'd have come across that in my reading. The other thing is why
> does adding only one static fix it. Wouldn't I have problems with the the
> other router?
>
> Kris
>
> -----Original Message-----
> From: Stephen C. Feldberg [mailto:scfeldberg@hotmail.com]
> Sent: Thursday, December 13, 2001 2:32 PM
> To: Krake, Kris; ccielab@groupstudy.com
> Subject: Re: bgp peering
>
>
> Peer's network address must be in routing table for BGP TCP session to be
> established. Default routes will not get it done.
>
> Steve
> ----- Original Message -----
> From: "Krake, Kris" <KKrake@aegonusa.com>
> To: <ccielab@groupstudy.com>
> Cc: "Krake, Kris" <KKrake@aegonusa.com>
> Sent: Thursday, December 13, 2001 1:35 PM
> Subject: bgp peering
>
>
> > I am working with two routers and setting up BGP peering between them
and
> > found something interesting regarding static routes. I am wondering if
I
> > have something misconfigured or if Both routers are peering with
> loopback
> > 0 interface.
> >
> > Loop0 10.10.1.1/32 Loop0 10.20.1.1/32
> > I I
> > I I
> > I I
> > Router A ---------------BGP------------RouterB
> >
> >
> > Router A and Router B both have default static routes to each other.
> > =-=-=-=-=-=-=-=
> > Router A
> >
> > int loopback 0
> > ip address 10.10.1.1 255.255.255.255
> >
> > Int s0
> > ip address 192.168.1.1 255.255.255.252
> >
> > Router BGP 1
> > neighbor 10.20.1.1 remote-as 1
> > neighbor 10.20.1.1 update-source loopback 0
> >
> > Ip route 0.0.0.0 0.0.0.0 192.168.1.2
> >
> > =-=-=-=-=-=-=-=-=-
> > Router B
> >
> > int looback 0
> > ip address 10.20.1.1 255.255.255.255
> >
> > Int s0
> > ip address 192.168.1.2 255.255.255.252
> >
> > Router BGP 1
> > neighbor 10.10.1.1 remote-as 1
> > neighbor 10.10.1.1 update-sourch loopback 0
> >
> > ip route 0.0.0.0 0.0.0.0 192.168.1.1
> >
> > =-=-=-=-=-=-=-=
> >
> > Here's the kicker...I can ping from one loopback to the other no
problems.
> > Verified with an extended ping. But I cannot establish a TCP connection
> > between the two routers unless I add a static route to one of the
> loopbacks
> > from the other router...which router makes no difference... (eg.)
> >
> > Router A
> > ip route 10.20.1.1 255.255.255.255 192.168.1.2
> >
> > or (not and !!!)
> >
> > Router B
> > ip route 10.10.1.1 255.255.255.255 192.168.1.1
> >
> > Anyone seen this...I can't find any documentation that would say this is
> > necessary. Router A is running 12.0(7) and Router B is running
12.1(5)T7
> >
> > Thanks for any input....
> >
> > KK
> >
> >
> >
> >
> >
> >
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > Kris A. Krake
> > WAN Engineer
> > AEGON Technology Services - NECS
> > 502.560.2716
> > kkrake@aegonusa.com
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:43 GMT-3