From: Pierrre-Alex GUANEL (pierreg@experttraining.net)
Date: Sat May 10 2003 - 10:28:34 GMT-3
Apparently you can't synchronize route reflector clients even though
the OSPF router ID and the BGP router IDs match. (See exhibit 1)
Someone in the archives (exhibit 2) explained that the " Cisco algorithm
does not looks at the BGP originator, but at the peer ID of the router that
sent it the route. "
If this is true then the task of synchronizing route reflector clients is
not possible.
Any comment / reference to add to my findings?
--------------- Exhibit 1 -----------
R3>show ip bgp
BGP table version is 1, local router ID is 3.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
* i188.1.2.0/24 10.0.70.1 100 0 1 65532 ?
* i 10.0.70.1 100 0 1 65532 ?
R3>
R3>show ip bgp 188.1.2.0
BGP routing table entry for 188.1.2.0/24, version 0
Paths: (2 available, no best path)
Not advertised to any peer
1 65532
10.0.70.1 (metric 71) from 10.200.0.1 (7.7.7.7)
Origin incomplete, localpref 100, valid, internal, not synchronized
Originator: 7.7.7.7, Cluster list: 0.0.0.2
1 65532
10.0.70.1 (metric 71) from 10.100.0.1 (7.7.7.7)
Origin incomplete, localpref 100, valid, internal, not synchronized
Originator: 7.7.7.7, Cluster list: 0.0.0.1
-------------------- Exhibit 2 ---------------
http://www.groupstudy.com/archives/ccielab/200204/msg00218.html
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:40 GMT-3