From: William Darkwah (william.darkwah@xxxxxxx)
Date: Thu Jun 15 2000 - 17:45:47 GMT-3
Xu,
I have run into the same problem before. I think ospf and bgp has this
kind of problem. I also found that
route-reflectors and ospf with frame-relay also have this kind of problem.
It is suppose to synchronise and send it
out but it does not. The only solution is to disable synchronization.
William
----- Original Message -----
From: xuping <cnmiecxu@public.bta.net.cn>
To: <ccielab@groupstudy.com>
Sent: Thursday, June 15, 2000 9:36 AM
Subject: BGP sync
> Hi all
>
> Thank you everybody for answer my question, thank you Mendoza, I read
"Page
> 135 Halabi's Internet Routing Architecture" again.
>
> BUT, most of you seemed to misunderstand my original post, since the list
> has down for 3 days, I like to post it again with more details.
>
> please see attached diagram
>
> R1 iBGP peering with R3
> loopback0 of R1 (192.168.1.1/24) is included in RIP domain and
redistribute
> into bgp by network 192.168.1.0 command.
> R2 do RIP vs OSPF mutual redistubution, no BPG running on R2.
>
> R1's config
> !
> interface loopback0
> ip address 192.168.1.1 255.255.255.0
> !
> interface Serial1
> ip address 192.168.12.1 255.255.255.0
> clock rate 64000
> !
> router rip
> network 192.168.1.0
> network 192.168.12.0
>
> rouer bgp 33
> network 192.168.1.0
> neighbor 192.168.23.3 remote-as 33
>
> R1#show ip bgp
> Network Next Hop Metric LocPrf Weight Path
> *> 192.168.1.0 0.0.0.0 0 32768 i
>
> R3's config
> !
> interface Ethernet0
> ip address 192.168.23.3 255.255.255.0
> !
> router ospf 1
> networ 192.168.23.0 0.0.0.255 area 0
> !
> router bgp 33
> neighbor 192.168.12.1 remote-as 33
>
> R3#show ip route
> Gateway of last resort is not set
>
> O E2 192.168.12.0/24 [110/20] via 192.168.23.2, 00:24:10, Ethernet0
> C 192.168.23.0/24 is directly connected, Ethernet0
> O E2 192.168.1.0/24 [110/20] via 192.168.23.2, 00:24:11, Ethernet0
>
> R3#show ip bgp
> Network Next Hop Metric LocPrf Weight Path
> * i192.168.1.0 192.168.12.1 0 100 0 i
>
> R3#show ip bgp 192.168.1.0
> BGP routing table entry for 192.168.1.0/24, version 0
> Paths: (1 available, no best path)
> Not advertised to any peer
> Local
> 192.168.12.1 (metric 20) from 192.168.12.1 (192.168.1.1)
> Origin IGP, metric 0, localpref 100, valid, internal, not
> synchronized, ref2
>
> My puzzle is on R3, R3 learn 192.168.1.0/24 via IGP(Ospf E2), at the same
> time, R3 learn 192.168.1.0/24 via iBGP; yet R3 still think the route
> 192.168.1.0/24 is unsyncronized. I am not trying to redistrubute anything,
> the route 192.168.1.0/24 is already in both IGP and BGP table of R3; I
just
> try to convince R3 that it is syncronized so that R3 may advise it to its
> EBPG peer.
>
> without "no sync" how can I make R3 think 192.168.1.0/24 is syncronized ?
>
> TIA
> xuping
>
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:42 GMT-3