From: CCIEin2006 (ciscocciein2006@gmail.com)
Date: Mon Mar 20 2006 - 12:20:47 GMT-3
I did not originate this route from the local router, but once I did
originate the route locally via the network command it started to be
advertised.
Looks like it has to do with the rule that Gustavio stated which was the
OSPF route and BGP must be originated by the same router....
On 3/20/06, Schulz, Dave <DSchulz@dpsciences.com> wrote:
>
> Are bringing this into the bgp process by the network command? Can you
> share the configs on this router?
>
>
> Dave Schulz,
> Email: dschulz@dpsciences.com
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> CCIEin2006
> Sent: Monday, March 20, 2006 10:01 AM
> 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?!?
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3