Re: BGP synchronisation

From: CiscoCCNP3@xxxxxxx
Date: Sat Mar 23 2002 - 01:35:48 GMT-3


   
hiya,

maybe i can help you get started as to where you need to investigate the lack
of synch. basically, the source of the learned route has to be synchronized.
in the below output, there is a route, known by ospf and bgp, and notice the
FROM in the output. these have to be the same, aka synched. in this first
example, the route, 206.11.0.0/16, an aggregate, was learned from two sources;

R5#sh ip bgp
* i206.11.0.0/16 10.1.52.2 10000 100 0 300 500 i
*> 206.11.20.65 0 300 500 i
*> 20.1.1.0/24 10.1.43.4 0 100 0 (10600) 100 i
R5#

R5#sh ip bgp 206.11.0.0
BGP routing table entry for 206.11.0.0/16, version 52
Paths: (2 available, best #2, table Default-IP-Routing-Table)
  Advertised to non peer-group peers:
  10.1.43.4 10.1.52.2
  300 500, (aggregated by 300 1.1.1.1), (received & used)
    10.1.52.2 from 10.1.52.2 (2.2.2.2)
      Origin IGP, metric 10000, localpref 100, valid, internal, not
synchronized

  300 500, (aggregated by 300 1.1.1.1), (received & used)
    206.11.20.65 from 206.11.20.65 (1.1.1.1) <-------------NOTE
      Origin IGP, localpref 100, valid, external, best <--------------NOTE
R5#
R5#sh ip route 206.11.0.0
Routing entry for 206.11.0.0/16, supernet
  Known via "bgp 10060", distance 20, metric 0
  Tag 300, type external
  Redistributing via rip
  Advertised by rip metric 14 route-map 300_only
  Last update from 206.11.20.65 3d08h ago
  Routing Descriptor Blocks:
  * 206.11.20.65, from 206.11.20.65, 3d08h ago <----------NOTE
      Route metric is 0, traffic share count is 1
      AS Hops 2

R5#

with regards to the second route, 24.1.1.0/24, learned from the other side of
the network, we see this

R4#sh ip route 24.1.1.0
Routing entry for 24.1.1.0/24
  Known via "bgp 10600", distance 20, metric 0
  Tag 100, type external
  Redistributing via rip, ospf 4
  Advertised by rip metric 5 route-map R6_BGP
                ospf 4 metric 6 subnets
  Last update from 192.19.15.6 1d09h ago
  Routing Descriptor Blocks:
  * 192.19.15.6, from 192.19.15.6, 1d09h ago <------------NOTE
      Route metric is 0, traffic share count is 1
      AS Hops 1

R4#sh ip bgp 24.1.1.0
BGP routing table entry for 24.1.1.0/24, version 5
Paths: (1 available, best #1, table Default-IP-Routing-Table)
  Advertised to non peer-group peers:
  10.1.32.2 10.1.53.5
  100, (received & used)
    192.19.15.6 from 192.19.15.6 (6.6.6.6) <-----------NOTE
      Origin IGP, metric 0, localpref 100, valid, external, best
R4#

that's what it needs to look like to be synched, hope that helps ;)

peace \/
joey r
ccnp/dp/si/wannabeie



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:19 GMT-3