From: Lachlan Kidd (lkidd@xxxxxxxxxxxxxxxxxxx)
Date: Sun Apr 01 2001 - 20:43:23 GMT-3
Hi Marcos,
At a guess (and I've only had a brief look) the problem lies with the f
act
that BGP will only publish a route if the next-hop is reachable (pingable)
from the router rx'ing the route.
BGP: 132.4.14.14 send UPDATE 132.4.80.0/24 -- unreachable
BGP: 132.4.14.14 send UPDATE 132.4.112.0/24 -- unreachable
BGP: 132.4.14.14 send UPDATE 172.168.80.0/24 -- unreachable
I would suggest you check the 'next-hop' address of these routes and make
sure you can ping them. You may need next-hop-self to fix this. I know the
message indicates 'not syncd' but I don't think you are facing a synch
issue.
Regards,
Lachlan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
marcosp@attglobal.net
Sent: Sunday, 1 April 2001 11:05:PM
To: CCIE- Lab
Subject: BGP Syncronization
Hi There,
I am having trouble with BGP syncronization. What Halabi tells me is
that BGP only will ads a route to a external peer if this route exists
at IGP okay? So way my router keeps telling me that one of my routes is
not synchronized? The routes are 132.4.80.0 and 132.4.81.0.
Here are the shows and the configs. Any tip , guess or whatever are
welcome.: ) Take a breath is a loooooong post.
r8----ebgp----r6--ospf---r5--ospf---r7--ebgp---r1
|
|--ibgp--r14
This is bootcamp lab 8 design
*****
R7 Config
!
router ospf 100
redistribute bgp 2 subnets route-map bgp
network 132.4.7.7 0.0.0.0 area 2
network 132.4.112.7 0.0.0.0 area 2
network 200.200.200.0 0.0.0.255 area 2
!
router bgp 2
redistribute ospf 100 route-map ospf
neighbor 132.4.6.6 remote-as 2
neighbor 132.4.6.6 route-reflector-client
neighbor 132.4.6.6 update-source Loopback0
neighbor 132.4.6.6 next-hop-self
neighbor 132.4.14.14 remote-as 2
neighbor 132.4.14.14 route-reflector-client
neighbor 132.4.14.14 update-source Loopback0
neighbor 132.4.14.14 next-hop-self
neighbor 132.4.170.1 remote-as 3
neighbor 132.4.170.1 update-source Loopback0
no auto-summary
!
no ip classless
access-list 7 permit 172.168.70.0
access-list 17 permit 172.168.80.0
access-list 17 permit 132.4.80.0
access-list 17 permit 132.4.81.0
route-map ospf deny 5
match ip address 17
!
route-map ospf permit 10
!
route-map bgp permit 10
match ip address 7
!
******
R7 route table
Rack4R7#o
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, * - candidate
default
U - per-user static route, o - ODR
Gateway of last resort is not set
172.168.0.0/24 is subnetted, 2 subnets
B 172.168.70.0 [20/170] via 132.4.170.1, 00:06:02
O E1 172.168.80.0 [110/1573] via 132.4.112.5, 00:06:22, Serial9
132.4.0.0/16 is variably subnetted, 19 subnets, 5 masks
O E1 132.4.130.16/28 [110/1662] via 132.4.112.5, 00:06:22, Serial9
C 132.4.170.0/24 is directly connected, Ethernet0
O IA 132.4.204.32/27 [110/3125] via 132.4.112.5, 00:05:45, Serial9
O IA 132.4.4.4/32 [110/3125] via 132.4.112.5, 00:06:05, Serial9
O IA 132.4.14.14/32 [110/3125] via 132.4.112.5, 00:06:22, Serial9
O IA 132.4.6.6/32 [110/1573] via 132.4.112.5, 00:06:23, Serial9
O IA 132.4.5.5/32 [110/1563] via 132.4.112.5, 00:06:23, Serial9
O E1 132.4.5.0/24 [110/1662] via 132.4.112.5, 00:06:23, Serial9
C 132.4.7.0/24 is directly connected, Loopback0
O IA 132.4.51.35/32 [110/1562] via 132.4.112.5, 00:06:23, Serial9
O IA 132.4.51.34/32 [110/3124] via 132.4.112.5, 00:06:06, Serial9
O E1 132.4.51.32/27 [110/1662] via 132.4.112.5, 00:06:24, Serial9
O IA 132.4.51.36/32 [110/3124] via 132.4.112.5, 00:06:24, Serial9
O E1 132.4.51.16/28 [110/1662] via 132.4.112.5, 00:06:24, Serial9
O IA 132.4.64.0/20 [110/1572] via 132.4.112.5, 00:06:24, Serial9
******
Here are the two route at OSPF
O E1 132.4.80.0/24 [110/1573] via 132.4.112.5, 00:06:24, Serial9
O E1 132.4.81.0/24 [110/1582] via 132.4.112.5, 00:06:24, Serial9
******
C 132.4.112.0/24 is directly connected, Serial9
C 132.4.112.5/32 is directly connected, Serial9
C 200.200.200.0/24 is directly connected, Loopback2
Rack4R7#
Rack4R7#sb
BGP table version is 38, local router ID is 200.200.200.1
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
* i132.4.4.4/32 132.4.6.6 1573 100 0 ?
*> 132.4.112.5 3125 32768 ?
* i132.4.5.0/24 132.4.6.6 110 100 0 ?
*> 132.4.112.5 1662 32768 ?
* i132.4.5.5/32 132.4.6.6 11 100 0 ?
*> 132.4.112.5 1563 32768 ?
*> 132.4.6.6/32 132.4.112.5 1573 32768 ?
* i132.4.14.14/32 132.4.6.6 1573 100 0 ?
*> 132.4.112.5 3125 32768 ?
* i132.4.51.16/28 132.4.6.6 110 100 0 ?
*> 132.4.112.5 1662 32768 ?
* i132.4.51.32/27 132.4.6.6 110 100 0 ?
*> 132.4.112.5 1662 32768 ?
* i132.4.51.34/32 132.4.6.6 1572 100 0 ?
*> 132.4.112.5 3124 32768 ?
* i132.4.51.35/32 132.4.6.6 10 100 0 ?
*> 132.4.112.5 1562 32768 ?
* i132.4.51.36/32 132.4.6.6 1572 100 0 ?
*> 132.4.112.5 3124 32768 ?
*> 132.4.64.0/20 132.4.112.5 1572 32768 ?
*>i132.4.80.0/24 132.4.6.6 0 100 0 1 i
*>i132.4.81.0/24 132.4.6.6 0 100 0 1 i
*>i132.4.112.0/24 132.4.6.6 1572 100 0 ?
* i132.4.130.16/28 132.4.6.6 110 100 0 ?
*> 132.4.112.5 1662 32768 ?
* i132.4.204.32/27 132.4.6.6 1573 100 0 ?
*> 132.4.112.5 3125 32768 ?
*> 172.168.70.0/24 132.4.170.1 170 0 3 i
*>i172.168.80.0/24 132.4.6.6 0 100 0 1 i
*> 200.200.200.0 0.0.0.0 0 32768 ?
Rack4R7#
****
R7- Debug ip BGP Events and Debug ip BGP updates
Rack4R7#sh debug
Rack4R7#debug ip bgp up
BGP updates debugging is on
Rack4R7#debug ip bgp ev
BGP events debugging is on
Rack4R7#clear ip bgp 132.4.6.6
Rack4R7#
BGP: 132.4.6.6 reset requested
BGP: no valid path for 132.4.80.0/24
BGP: no valid path for 132.4.81.0/24
BGP: no valid path for 132.4.112.0/24
BGP: no valid path for 172.168.80.0/24
BGP: 132.4.6.6 reset due to User reset request
BGP: 132.4.6.6 went from Established to Idle
BGP: nettable_walker 132.4.80.0/255.255.255.0 no best path selected
BGP: nettable_walker 132.4.81.0/255.255.255.0 no best path selected
BGP: nettable_walker 132.4.112.0/255.255.255.0 no best path selected
BGP: nettable_walker 172.168.80.0/255.255.255.0 no best path selected
BGP: 132.4.6.6 went from Idle to Active
BGP: 132.4.14.14 computing updates, neighbor version 29, table version
34, start
ing at 0.0.0.0
BGP: 132.4.14.14 send UPDATE 132.4.80.0/24 -- unreachable
BGP: 132.4.14.14 send UPDATE 132.4.112.0/24 -- unreachable
BGP: 132.4.14.14 send UPDATE 172.168.80.0/24 -- unreachable
BGP: 132.4.14.14 1 updates enqueued (average=35, maximum=35)
BGP: 132.4.14.14 update run completed, ran for 8ms, neighbor version 29,
start v
ersion 34, throttled to 34, check point net 0.0.0.0
BGP: 132.4.170.1 computing updates, neighbor version 29, table version
34, start
ing at 0.0.0.0
BGP: 132.4.170.1 send UPDATE 132.4.80.0/24 -- unreachable
BGP: 132.4.170.1 send UPDATE 132.4.112.0/24 -- unreachable
BGP: 132.4.170.1 send UPDATE 172.168.80.0/24 -- unreachable
BGP: 132.4.170.1 1 updates enqueued (average=35, maximum=35)
BGP: 132.4.170.1 update run completed, ran for 12ms, neighbor version
29, start
version 34, throttled to 34, check point net 0.0.0.0
Rack4R7#
BGP: 132.4.6.6 went from Active to OpenSent
BGP: 132.4.6.6 went from OpenSent to OpenConfirm
BGP: 132.4.6.6 went from OpenConfirm to Established
BGP: 132.4.6.6 computing updates, neighbor version 0, table version 34,
starting
at 0.0.0.0
BGP: 132.4.6.6 send UPDATE 132.4.4.4/32, next 132.4.7.7, metric 3125,
path
BGP: 132.4.6.6 send UPDATE 132.4.5.0/24, next 132.4.7.7, metric 1662,
path
BGP: 132.4.6.6 send UPDATE 132.4.5.5/32, next 132.4.7.7, metric 1563,
path
BGP: 132.4.6.6 send UPDATE 132.4.6.6/32, next 132.4.7.7, metric 1573,
path
BGP: 132.4.6.6 send UPDATE 132.4.14.14/32, next 132.4.7.7, metric 3125,
path
BGP: 132.4.6.6 send UPDATE 132.4.51.16/28, next 132.4.7.7, metric 1662,
path
BGP: 132.4.6.6 send UPDATE 132.4.51.32/27, next 132.4.7.7, metric 1662,
path
BGP: 132.4.6.6 send UPDATE 132.4.51.34/32, next 132.4.7.7, metric 3124,
path
BGP: 132.4.6.6 send UPDATE 132.4.51.35/32, next 132.4.7.7, metric 1562,
path
BGP: 132.4.6.6 send UPDATE 132.4.51.36/32, next 132.4.7.7, metric 3124,
path
BGP: 132.4.6.6 send UPDATE 132.4.64.0/20, next 132.4.7.7, metric 1572,
path
BGP: 132.4.6.6 send UPDATE 132.4.130.16/28, next 132.4.7.7, metric 1662,
path
BGP: 132.4.6.6 send UPDATE 132.4.204.32/27, next 132.4.7.7, metric 3125,
path
BGP: 132.4.6.6 send UPDATE 172.168.70.0/24, next 132.4.7.7, metric 170,
path 3
BGP: 132.4.6.6 send UPDATE 200.200.200.0/24, next 132.4.7.7, metric 0,
path
BGP: 132.4.6.6 15 updates enqueued (average=70, maximum=73)
BGP: 132.4.6.6 update run completed, ran for 44ms, neighbor version 0,
start ver
sion 34, throttled to 34, check point net 0.0.0.0
BGP: 132.4.6.6 rcv UPDATE about 132.4.204.32/27, next hop 132.4.6.6,
path metri
c 1573
BGP: 132.4.6.6 rcv UPDATE about 132.4.14.14/32, next hop 132.4.6.6,
path metric
1573
BGP: 132.4.6.6 rcv UPDATE about 132.4.4.4/32, next hop 132.4.6.6, path
metric 1
573
BGP: 132.4.6.6 rcv UPDATE about 132.4.51.35/32, next hop 132.4.6.6,
path metric
10
BGP: 132.4.6.6 rcv UPDATE about 132.4.5.5/32, next hop 132.4.6.6, path
metric 1
1
BGP: 132.4.6.6 rcv UPDATE about 132.4.112.0/24, next hop 132.4.6.6,
path metric
1572
BGP: 132.4.6.6 rcv UPDATE about 132.4.51.36/32, next hop 132.4.6.6,
path metric
1572
BGP: nettable_walker 132.4.112.0/255.255.255.0 calling revise_route
BGP: revise route installing 132.4.112.0/255.255.255.0 -> 132.4.6.6
BGP: 132.4.6.6 rcv UPDATE about 132.4.51.34/32, next hop 132.4.6.6,
path metric
1572
BGP: 132.4.6.6 rcv UPDATE about 132.4.80.0/24, next hop 132.4.6.6, path
1 metric
0
BGP: 132.4.6.6 rcv UPDATE about 132.4.81.0/24, next hop 132.4.6.6, path
1 metric
0
BGP: 132.4.6.6 rcv UPDATE about 172.168.80.0/24, next hop 132.4.6.6,
path 1 metr
ic 0
BGP: 132.4.6.6 rcv UPDATE about 132.4.130.16/28, next hop 132.4.6.6,
path metri
c 110
BGP: 132.4.6.6 rcv UPDATE about 132.4.51.32/27, next hop 132.4.6.6,
path metric
110
BGP: 132.4.6.6 rcv UPDATE about 132.4.51.16/28, next hop 132.4.6.6,
path metric
110
BGP: 132.4.6.6 rcv UPDATE about 132.4.5.0/24, next hop 132.4.6.6, path
metric 1
10
******
Here are the problem. 132.4.81.0 is not syn but 132.4.80 is. This
driving me crazy!! : )
BGP: nettable_walker 132.4.80.0/255.255.255.0 calling revise_route
BGP: revise route installing 132.4.80.0/255.255.255.0 -> 132.4.6.6
BGP: nettable_walker 132.4.81.0/255.255.255.0 not synchronized
******
BGP: nettable_walker 172.168.80.0/255.255.255.0 calling revise_route
BGP: revise route installing 172.168.80.0/255.255.255.0 -> 132.4.6.6
BGP: 132.4.14.14 computing updates, neighbor version 34, table version
38, start
ing at 0.0.0.0
BGP: 132.4.14.14 send UPDATE 132.4.80.0/24, next 132.4.6.6, metric 0,
path 1
BGP: 132.4.14.14 send UPDATE 132.4.112.0/24, next 132.4.6.6, metric
1572, path
BGP: 132.4.14.14 send UPDATE 172.168.80.0/24, next 132.4.6.6, path 1
BGP: 132.4.14.14 2 updates enqueued (average=73, maximum=77)
BGP: 132.4.14.14 update run completed, ran for 12ms, neighbor version
34, start
version 38, throttled to 38, check point net 0.0.0.0
BGP: 132.4.6.6 computing updates, neighbor version 34, table version 38,
startin
g at 0.0.0.0
BGP: 132.4.6.6 send UPDATE 132.4.80.0/24 -- unreachable
BGP: 132.4.6.6 send UPDATE 132.4.112.0/24 -- unreachable
BGP: 132.4.6.6 send UPDATE 172.168.80.0/24 -- unreachable
BGP: 132.4.6.6 1 updates enqueued (average=35, maximum=35)
BGP: 132.4.6.6 update run completed, ran for 8ms, neighbor version 34,
start ver
sion 38, throttled to 38, check point net 0.0.0.0
Rack4R7#un all
All possible debugging has been turned off
**NOTE** All LAB SWAP messages should now be sent to the
LAB SWAP Message board on groupstudy.com.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:38 GMT-3