From: Gustavo Novais (gustavo.novais@novabase.pt)
Date: Mon Mar 20 2006 - 12:09:50 GMT-3
For OSPF and BGP, the sync rule also states that the router-id of the router that announces the net to OSPF must be the same of the one (iBGP peer) who injects it to BGP.
Check it on
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094431.shtml#background
or TCP/IP Vol2
HTH
Gustavo Novais
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of CCIEin2006
Sent: segunda-feira, 20 de Margo de 2006 15:01
To: ccielab@groupstudy.com
Subject: BGP synchronization rule not working
Hey guys,
I'm doing a lab in which BGP synchronization must be enabled.
I know the rule states that a route must be in the IGP table before
advertised to BGP peer.
In this case I have an OSPF E2 route in my routing table:
Rack1R6#show ip route 139.1.5.0
Routing entry for 139.1.5.0/24
Known via "ospf 1", distance 110, metric 20, type extern 2, forward metric
129
Last update from 139.1.0.3 on FastEthernet0/1, 13:21:38 ago
Routing Descriptor Blocks:
* 139.1.0.3, from 150.1.5.5, 13:21:38 ago, via FastEthernet0/1
Route metric is 20, traffic share count is 1
But BGP is saying the route is not synchronized:
Rack1R6#show ip bgp 139.1.5.0
BGP routing table entry for 139.1.5.0/24, version 0
Paths: (1 available, no best path)
Not advertised to any peer
Local
139.1.45.5 (metric 20) from 150.1.4.4 (150.1.4.4)
Origin IGP, metric 1, localpref 100, valid, internal, not synchronized
Rack1R6#
It is clearly being learned by OSPF, so why does BGP not consider
it synchronized?!?
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3