From: Bob Sinclair (bsin@cox.net)
Date: Sat Feb 19 2005 - 17:19:07 GMT-3
KC
Could you send the output of "sh ip route 3.0.0.0" ? This will verify the RID
of the OSPF ASBR. I see that the bgp source RID is 172.16.123.1 from
neighbor address 172.16.123.3. The "via" 172.16.123.3 in the sh ip route
output does not necessarily indicate the RID of the OSPF ASBR, however.
Bob Sinclair
CCIE #10427, CCSI 30427, CISSP
www.netmasterclass.net
----- Original Message -----
From: k c
To: ccielab@groupstudy.com
Sent: Saturday, February 19, 2005 11:23 AM
Subject: BGP route cannot advertise to neighor (sync problem)
Hi Group,
R2 cannot advertise 3.0.0.0/8 to R1 due to synchronization. But why? BGP and
ospf router ids are the same. ospf has route 3.0.0.0/8 and bgp has 3.0.0.0/8
route, why it cannot be advertised to R1
R2 config:
router bgp 64600
synchronization
bgp router-id 172.16.123.2
bgp log-neighbor-changes
network 2.2.2.0 mask 255.255.255.0
neighbor 172.16.123.1 remote-as 100
neighbor 172.16.123.3 remote-as 64600
no auto-summary
sh ip route ospf
O IA 3.0.0.0/8 [110/65] via 172.16.123.3, 00:31:32, Serial4/0
sh ip bgp
* i3.0.0.0 172.16.123.3 0 100 0 i
R2#sh ip bgp 3.0.0.0
BGP routing table entry for 3.0.0.0/8, version 14
Paths: (1 available, no best path)
Not advertised to any peer
Local
172.16.123.3 from 172.16.123.3 (172.16.123.1)
Origin IGP, metric 0, localpref 100, valid, internal, not
synchronized
Thanks,
---------------------------------
Yahoo! $u(c&C - $:8m(>$n<u%X5x5!$u/`!I
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 08:51:23 GMT-3