From: McCallum, Robert (Robert.McCallum@xxxxxxxxxxxxxxxxxx)
Date: Fri Feb 01 2002 - 16:07:28 GMT-3
can you do a show ip ospf. This will let us know what your router id in ospf s
peak is. If it is different from the router-id that you show ip bgp reports th
en, voila that is why they will never synchronise.
-----Original Message-----
From: Bob Sinclair [mailto:bsin@erols.com]
Sent: 01 February 2002 17:53
To: ccielab@groupstudy.com
Subject: BGP Sync
List:
Wonder if anyone can spot why these bgp routes are not synced. I am leaving sy
nc on for lab purposes. Below, it can be seen that, for example, 140.10.2.0 is
not being advertised to any peer because not synced. But, next hop can be reac
hed (172.16.61.6) and 140.10.2.0 is in the ip routing table.
140.10.2.0 got into the routing table by the following redistribution: ebgp>is
is>ospf.
Thanks.
Below will probably be easier to read if you maximize this email.
R2#sh ip b
BGP table version is 1, local router ID is 172.16.22.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
* i140.10.2.0/24 172.16.61.6 0 100 0 500 i
* i140.10.3.0/24 172.16.61.6 0 100 0 500 i
* i140.10.4.0/24 172.16.61.6 0 100 0 500 i
* i140.10.5.0/24 172.16.61.6 0 100 0 500 i
* i172.0.0.0/8 172.16.61.6 100 0 i
R2#sh ip b 140.10.2.0
BGP routing table entry for 140.10.2.0/24, version 0
Paths: (1 available, no best path)
Not advertised to any peer
500
172.16.61.6 (metric 20) from 172.16.61.6 (172.16.61.6)
Origin IGP, metric 0, localpref 100, valid, internal, not synchronized
R2#i
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
O E2 201.201.1.0/24 [110/20] via 172.16.12.1, 00:21:31, Serial0.1
140.10.0.0/24 is subnetted, 4 subnets
O E2 140.10.4.0 [110/20] via 172.16.12.1, 00:21:31, Serial0.1
O E2 140.10.5.0 [110/20] via 172.16.12.1, 00:21:31, Serial0.1
O E2 140.10.2.0 [110/20] via 172.16.12.1, 00:21:31, Serial0.1
O E2 140.10.3.0 [110/20] via 172.16.12.1, 00:21:31, Serial0.1
172.16.0.0/16 is variably subnetted, 10 subnets, 2 masks
O E2 172.16.61.0/28 [110/20] via 172.16.12.1, 00:21:31, Serial0.1
O E2 172.16.36.0/24 [110/20] via 172.16.12.3, 00:21:32, Serial0.1
O E2 172.16.35.0/24 [110/20] via 172.16.12.3, 00:21:32, Serial0.1
C 172.16.22.0/24 is directly connected, TokenRing0
O E2 172.16.16.0/24 [110/20] via 172.16.12.1, 00:21:32, Serial0.1
C 172.16.12.0/24 is directly connected, Serial0.1
O 172.16.13.0/24 [110/3562] via 172.16.12.3, 00:21:34, Serial0.1
[110/3562] via 172.16.12.1, 00:21:34, Serial0.1
O E2 172.16.6.0/24 [110/20] via 172.16.12.1, 00:21:34, Serial0.1
O E2 172.16.7.0/24 [110/20] via 172.16.12.1, 00:21:34, Serial0.1
O E2 172.16.1.0/24 [110/20] via 172.16.12.1, 00:21:34, Serial0.1
O E2 192.168.2.0/24 [110/20] via 172.16.12.1, 00:21:34, Serial0.1
O E2 192.168.3.0/24 [110/20] via 172.16.12.1, 00:21:34, Serial0.1
O E2 172.0.0.0/8 [110/20] via 172.16.12.1, 00:21:34, Serial0.1
R2#
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:10 GMT-3