From: Peter van Oene (pvo@xxxxxxxxxxxx)
Date: Wed Jul 31 2002 - 21:15:27 GMT-3
My testing indicates that cisco may not use BGP router-id, but might
instead use Peer-ID. I'm hopeful to be proven otherwise, but can't see
asking any of the folks who wrote it. They more than likely forget anyway.
At 03:30 PM 7/31/2002 -0700, David wrote:
>match BGP's router ID with the originator's OSPF router ID...
>so make R1's BGP router ID match R3's OSPF router ID and vice versa
>
>At 07:51 PM 7/31/2002 +0300, TK-Network Gvz|mleri wrote:
>>Yep,
>>
>>there is no problem with the router id's. I van see all the routes at
>>the R3.
>>Also I can see 71.71.71.0 at R3's route table !!!
>>But it shows not snchronised. Funny ?
>>See the route table :
>>
>>R3---------------------------------------------------------------
>>R3#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/24 is subnetted, 2 subnets
>>O 1.1.1.0 [110/58] via 1.1.2.2, 01:53:47, Ethernet0/0
>>C 1.1.2.0 is directly connected, Ethernet0/0
>> 71.0.0.0/24 is subnetted, 1 subnets
>>O 71.71.71.0 [110/59] via 1.1.2.2, 01:53:47, Ethernet0/0
>> 81.0.0.0/24 is subnetted, 1 subnets
>>O 81.81.81.0 [110/11] via 1.1.2.2, 01:53:47, Ethernet0/0
>> 10.0.0.0/24 is subnetted, 3 subnets
>>O 10.2.2.0 [110/11] via 1.1.2.2, 01:53:47, Ethernet0/0
>>O 10.1.1.0 [110/59] via 1.1.2.2, 01:53:48, Ethernet0/0
>>C 10.3.3.0 is directly connected, Loopback0
>>
>>
>>it is there 71.71.71.0 but why it is not snchronised I couldn't
>>understood.
>>Best Regards
>>umit
>>
>>-----Original Message-----
>>From: Brett Rilling [mailto:BRilling@nshorenet.com]
>>Sent: Wednesday, July 31, 2002 19:17
>>To: '\mit Askan (TK-Network Gvz|mleri)'
>>Subject: RE: BGP with OSPF Synch
>>
>>
>>I am not the best at this stuff but here goes ;)
>>
>>Are you advertising the router id's into the igp? This way IGP knows
>>about
>>these IP's and should sych them with the BGP. If IGP doesn't know them
>>then
>>it cant sych the BGP route.
>>
>>Do a sh ip route... do you see the router ID's? Can you ping them?
>>
>>
>>
>>
>>
>>
>>
>>-----Original Message-----
>>From: \mit Askan (TK-Network Gvz|mleri)
>>[mailto:umit.askan@probil.com.tr]
>>Sent: Wednesday, July 31, 2002 10:41 AM
>>To: Ccie (E-mail)
>>Subject: BGP with OSPF Synch
>>
>>
>>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:48:13 GMT-3