From: Sandro Ciffali (sandyccie@xxxxxxxxx)
Date: Wed Jul 31 2002 - 15:16:24 GMT-3
Umit,
This has been discussed before on the groupstudy.com,
For a IBGP route to get synced in the router id's of
the route learned from both BGP and IGP has to match.
In your case you hade router R1, R2 and R3, with R2 as
a RR, So when a network is advertised by R1 on BGP,
Bgp adv. is sent to R2, Since R2 is a RR, It sends the
network to R3 with itself as the router id. R3 is rec.
this route in two ways, One from R2 on Ibgp and other
from R1 through OSPF, Since Ospf route has id of R1
and IBGP route has id of R2 this route is never
synced.
To the best of my knowledge the only way to get this
route synced is to use confed instead of RR or to
enter network statement under bgp on R3 for all the
network on R1 and filter them from propogating back to
R2.
Sandeep
8988
--- \mit_A~kan_(TK-Network_Gvz|mleri)
<umit.askan@probil.com.tr> wrote:
> I tried before. nothing !
>
> -----Original Message-----
> From: Song Mu [mailto:songmu@yahoo.com]
> Sent: Wednesday, July 31, 2002 20:06
> To: \mit_A~kan_; Ccie (E-mail)
> Subject: Re: BGP with OSPF Synch
>
>
> try to add next-hop-self on R2 neighbor to R3 and
> see what happen
>
> Thanks,
>
> Song
> --- \mit_A~kan_(TK-Network_Gvz|mleri)
> <umit.askan@probil.com.tr> wrote:
> > Hi,
> >
> > I have got a problem with OSPF-BGP-Synch. topology
> looks like :
> >
> > R1---R2(RR)---R3 all are in AS1, R2 is RR. all
> nei on loopback IPs,
> > 10.1.1.1, 10.2.2.2, 10.3.3.3
> > BGP router id and OSPF router id are same at the
> routers. Synch is
> > on.
> > after i advertise one block from R1, I can see it
> on the BGP table of
> > R3.
> > But when I look the route it is not schronized.
> Any ideas ?
> >
> > R1-----------------------------------------------
> > router ospf 1
> > router-id 10.1.1.1
> > log-adjacency-changes
> > network 0.0.0.0 255.255.255.255 area 0
> > !
> > router bgp 1
> > synchronization
> > bgp router-id 10.1.1.1
> > bgp log-neighbor-changes
> > network 71.71.71.0 mask 255.255.255.0
> > neighbor 10.2.2.2 remote-as 1
> > neighbor 10.2.2.2 update-source Loopback0
> > no auto-summary
> >
>
R2----------------------------------------------------
> > router ospf 1
> > router-id 10.2.2.2
> > log-adjacency-changes
> > network 0.0.0.0 255.255.255.255 area 0
> > !
> > router bgp 1
> > bgp router-id 10.2.2.2
> > bgp cluster-id 167837954
> > bgp log-neighbor-changes
> > network 81.81.81.0 mask 255.255.255.0
> > neighbor 10.1.1.1 remote-as 1
> > neighbor 10.1.1.1 update-source Loopback0
> > neighbor 10.1.1.1 route-reflector-client
> > neighbor 10.3.3.3 remote-as 1
> > neighbor 10.3.3.3 update-source Loopback0
> > neighbor 10.3.3.3 route-reflector-client
> > no auto-summary
> >
>
R3----------------------------------------------------
> > router ospf 1
> > router-id 10.3.3.3
> > log-adjacency-changes
> > network 0.0.0.0 255.255.255.255 area 0
> > !
> > router bgp 1
> > bgp log-neighbor-changes
> > neighbor 10.2.2.2 remote-as 1
> > neighbor 10.2.2.2 update-source Loopback0
> > no auto-summary
> >
> > R3#sh ip bgp
> > BGP table version is 2, local router ID is
> 10.3.3.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
> > * i71.71.71.0/24 10.1.1.1 0
> 100 0 i
> > *>i81.81.81.0/24 10.2.2.2 0
> 100 0 i
> > R3#sh ip bgp 71.71.71.0
> > BGP routing table entry for 71.71.71.0/24, version
> 0
> > Paths: (1 available, no best path)
> > Not advertised to any peer
> > Local
> > 10.1.1.1 (metric 59) from 10.2.2.2 (10.2.2.2)
> > Origin IGP, metric 0, localpref 100, valid,
> internal, not
> > synchronized
> > Originator: 10.1.1.1, Cluster list: 10.1.1.2
> > R3#sh ip bgp 81.81.81.0
> > BGP routing table entry for 81.81.81.0/24, version
> 2
> > Paths: (1 available, best #1, table
> Default-IP-Routing-Table)
> > Not advertised to any peer
> > Local
> > 10.2.2.2 (metric 11) from 10.2.2.2 (10.2.2.2)
> > Origin IGP, metric 0, localpref 100, valid,
> internal,
> > synchronized, best
> >
> > Best Regards
> >
> > Umit Askan
> > Consulting Network Engineer
> > CCNP, CCDP, CCNP-Security, CCNP-Voice Access
> >
> > > Probil Bilgi Islem Destek ve Danismanlik San. ve
> Tic. A.S.
> > Eski Buyukdere Caddesi Dilaver Sokak No.4
> > Otosanayi 4. Levent 80660 Istanbul
> >
> > Tel: +90 (212) 317 61 00 (219)
> > Direkt : +90 (212) 317 62 19
> > Faks: +90 (212) 325 55 15
> > E-Mail: umit.askan@probil.com.tr
> > Web: www.probil.com.tr
> >
>
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:50 GMT-3