From: Peter van Oene (pvo@xxxxxxxxxxxx)
Date: Thu Aug 01 2002 - 10:10:12 GMT-3
If all routers are in their own sub-as's, then you run confed-ebgp between
all routers. futher, as i believe (and really should confirm this one of
these days) that cisco is using the BGP peer address to match the OSPF-RID,
this solves the problem.
Pete
At 04:04 PM 8/1/2002 +1000, Hunt Lee wrote:
>Hello Sandro,
>
>Can you please elaborate a bit more on how you would use Confed to fix this
>problem?? If you split off RTA, RTB & RTC into a Confed Sub-AS and RTD, RTE
>& RTF into another Confed Sub-AS, it still won't fix the problem... RTB
>would still not be able to sync. the route from RTC (i.e. 2.2.2.2/32) & vice
>versa for RTC.
>
>Thanks so much for your help in advance,
>
>Best Regards,
>Hunt Lee
>
>
>-----Original Message-----
>From: Sandro Ciffali [mailto:sandyccie@yahoo.com]
>Sent: Wednesday, 31 July 2002 10:43 PM
>To: Omer Ansari; Hunt Lee
>Cc: ccielab@groupstudy.com
>Subject: Re: Route Reflector Client problem with sync
>
>
>This has been discussed before in the groupstudy, This
>is a typical problem where the ospf router id is
>different from BGP router id and hence the route does
>not get synced. If you remove the right half of your
>diagram (Rtd, Rte and Rtf) you still will have the
>same issue.
>There are two solutions to this issue, One is to use
>confed instead of route reflector. Second is to enter
>the network command under bgp for those networks, For
>example try entering network 2.2.2.2/32 under bgp
>process of Rtb and then see what happens. I have not
>done this myself but I am more inclined towards the
>routes will get synced. As far as confed solution is
>concerned it works fine.
>
>Hope this helps, You will get more info on this issue
>if you search the archives on the bgp/ospf router id
>issues.
>
>Sandeep
>8988
>--- Omer Ansari <omer@ansari.com> wrote:
> > Hunt,
> >
> > my previous post did not solve the issue as i
> > thought it would.
> > however, after much deliberation, and searching
> > google:
> >
> >
>http://www.groupstudy.com/archives/ccielab/200204/msg00018.html
> >
> > On Tue, 30 Jul 2002, Omer Ansari wrote:
> >
> > > Hunt,
> > > I was able to replicate this issue.
> > >
> > > The problem is resolved by putting ip ospf network
> > point-to-point on the
> > > loopback interfaces for those /32 networks
> > >
> > > that evidently produces a summary net link lsa for
> > those networks as seen
> > > in show ip ospf database which was not there prior
> > to putting the command
> > > in.
> > >
> > >
> > > On Sun, 28 Jul 2002, [iso-8859-1] Hunt Lee wrote:
> > >
> > > > Hi all,
> > > >
> > > > 1.1.1.1/32 - RTB RTE - 3.3.3.3/32
> > > > \ /
> > > > RTA -- RTD
> > > > / \
> > > > 2.2.2.2/32 - RTC RTF - 4.4.4.4/32
> > > >
> > > >
> > > > All routers are in AS 1, and the 1.1.1.1/32,
> > 2.2.2.2/32, 3.3.3.3/32 &
> > > > 4.4.4.4/32 are being advertised by BGP's network
> > command (all 4 of
> > > > them are loopback interfaces created on
> > respective routers).
> > > >
> > > > RTA & RTD are Route Reflector, in which RTB &
> > RTC are RR client of
> > > > RTA, and RTE & RTF are RR client of RTD.
> > > >
> > > > OSPF is running on all routers (also covers
> > those 4 networks
> > > > advertised by BGP).
> > > >
> > > > The neighbor update-source command has been used
> > to establish BGP
> > > > connections. The IP address that each router
> > uses is:-
> > > >
> > > > RTA - 172.16.1.1
> > > > RTB - 172.16.1.2
> > > > RTC - 172.16.1.3
> > > >
> > > > RTD - 172.17.1.1
> > > > RTE - 172.17.1.2
> > > > RTF - 172.17.1.3
> > > >
> > > >
> > > > With Synchorization turned on at all routers...
> > I found that each RR
> > > > client cannot sync. the BGP route from the other
> > RR Client, who is a
> > > > member of the same Route Reflector.
> > > >
> > > > RouterB#sh ip bgp
> > > > BGP table version is 28, local router ID is
> > 172.16.1.2
> > > > Status codes: s suppressed, d damped, h history,
> > * valid, > best, i -
> > > > internal
> > > > Origin codes: i - IGP, e - EGP, ? - incomplete
> > > >
> > > > Network Next Hop Metric LocPrf
> > Weight Path
> > > > *> 1.1.1.1/32 0.0.0.0 0
> > 32768 i
> > > > * i2.2.2.2/32 172.16.1.3 0 100
> > 0 i
> > > > *>i3.3.3.3/32 172.17.1.2 0 100
> > 0 i
> > > > *>i4.4.4.4/32 172.17.1.3 0 100
> > 0 i
> > > > *>i10.1.1.0/30 172.16.1.1 0 100
> > 0 i
> > > > *>i10.1.2.0/30 172.16.1.1 0 100
> > 0 i
> > > > *>i20.1.1.0/24 172.16.1.1 0 100
> > 0 i
> > > > *>i30.1.1.0/30 172.17.1.1 0 100
> > 0 i
> > > > *>i30.1.2.0/30 172.17.1.1 0 100
> > 0 i
> > > >
> > > >
> > > > RouterB#sh ip bgp 2.2.2.2/32
> > > > BGP routing table entry for 2.2.2.2/32, version
> > 0
> > > > Paths: (1 available, no best path)
> > > > Not advertised to any peer
> > > > Local
> > > > 172.16.1.3 (metric 129) from 172.16.1.1
> > (172.16.1.1)
> > > > Origin IGP, metric 0, localpref 100,
> > valid, internal, not
> > > > synchronized
> > > > Originator: 172.16.1.3, Cluster list:
> > 172.16.1.1
> > > >
> > > >
> > > > RouterB#sh ip route
> > > > Codes: C - connected, S - static, I - IGRP, R -
> > RIP, M - mobile, B -
> > > > BGP
> > > > D - EIGRP, EX - EIGRP external, O - OSPF,
> > IA - OSPF inter area
> > > >
> > > > N1 - OSPF NSSA external type 1, N2 - OSPF
> > NSSA external type 2
> > > > E1 - OSPF external type 1, E2 - OSPF
> > external type 2, E - EGP
> > > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS
> > level-2, ia - IS-IS
> > > > inter area
> > > > * - candidate default, U - per-user
> > static route, o - ODR
> > > > P - periodic downloaded static route
> > > >
> > > > Gateway of last resort is not set
> > > >
> > > > 1.0.0.0/32 is subnetted, 1 subnets
> > > > C 1.1.1.1 is directly connected, Loopback5
> > > > 2.0.0.0/32 is subnetted, 1 subnets
> > > > O 2.2.2.2 [110/129] via 10.1.1.1,
> > 01:24:29, Serial0
> > > > 3.0.0.0/32 is subnetted, 1 subnets
> > > > O IA 3.3.3.3 [110/139] via 10.1.1.1,
> > 00:59:54, Serial0
> > > > 4.0.0.0/32 is subnetted, 1 subnets
> > > > O IA 4.4.4.4 [110/139] via 10.1.1.1,
> > 00:57:52, Serial0
> > > > 20.0.0.0/24 is subnetted, 1 subnets
> > > > O IA 20.1.1.0 [110/74] via 10.1.1.1,
> > 01:24:29, Serial0
> > > > 172.17.0.0/32 is subnetted, 3 subnets
> > > > O IA 172.17.1.1 [110/75] via 10.1.1.1,
> > 01:24:28, Serial0
> > > > O IA 172.17.1.2 [110/139] via 10.1.1.1,
> > 01:24:28, Serial0
> > > > O IA 172.17.1.3 [110/139] via 10.1.1.1,
> > 01:24:03, Serial0
> > > > 172.16.0.0/32 is subnetted, 3 subnets
> > > > O IA 172.16.1.1 [110/65] via 10.1.1.1,
> > 01:24:30, Serial0
> > > > O 172.16.1.3 [110/129] via 10.1.1.1,
> > 01:24:30, Serial0
> > > > C 172.16.1.2 is directly connected,
> > Loopback1
> > > > 10.0.0.0/30 is subnetted, 2 subnets
> > > > O 10.1.2.0 [110/128] via 10.1.1.1,
> > 01:24:30, Serial0
> > > > C 10.1.1.0 is directly connected, Serial0
> > > > 30.0.0.0/30 is subnetted, 2 subnets
> > > > O IA 30.1.2.0 [110/138] via 10.1.1.1,
> > 01:24:13, Serial0
> > > > O IA 30.1.1.0 [110/138] via 10.1.1.1,
> > 01:24:29, Serial0
> > > > RouterB#
> > > >
> > > >
> > > > RouterC#sh ip bgp
> > > > BGP table version is 28, local router ID is
> > 172.16.1.3
> > > > Status codes: s suppressed, d damped, h history,
> > * valid, > best, i -
> > > > internal
> > > > Origin codes: i - IGP, e - EGP, ? - incomplete
> > > >
> > > > Network Next Hop Metric LocPrf
> > Weight Path
> > > > * i1.1.1.1/32 172.16.1.2 0 100
> > 0 i
> > > > *> 2.2.2.2/32 0.0.0.0 0
> > 32768 i
> > > > *>i3.3.3.3/32 172.17.1.2 0 100
> > 0 i
> > > > *>i4.4.4.4/32 172.17.1.3 0 100
> > 0 i
> > > > *>i10.1.1.0/30 172.16.1.1 0 100
> > 0 i
> > > > *>i10.1.2.0/30 172.16.1.1 0 100
> > 0 i
> > > > *>i20.1.1.0/24 172.16.1.1 0 100
> > 0 i
> > > > *>i30.1.1.0/30 172.17.1.1 0 100
> >
>=== message truncated ===
>
>
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:13 GMT-3