Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Came up with new couple of issues in BGP


I am facing two issues in BGP and i need someone to help on this. Please see both the topology and Config files.

First Issue:

Because the link between Vail and Telluride runs iBGP, both routers will learn about the networks in AS 300 and AS 400 through native BGP only and both AS's do reach each other. Both routers are also running OSPF with Aspen and BGP routes are redistributed into OSPF domain. Now, Aspen knows about the networks in AS 300 and AS 400. Now suppose the link between Vail and Telluride fails, both AS 300 and AS 400 can't reach each other anymore. The only solution to this is to redistribute OSPF routes to BGP on Vail and Telluride. But when i did this, only routes with "O" learned by Tahoe and Alta. In other words, Tahoe sees only, and Alta sees only the same routes.

Why the redistribution from OSPF to BGP didn't advertise the O E2 routes?

Second Issue:

This actually was discussed before but i still can't get it. It is not an actual issue.

It is about "Syncronization".

I know that we've said many times to turn on Sync. when we do redistribution from BGP to an IGP to make sure that the routes are installed correctly in the IGP routing table. However, as you notice in the configuration, i didn't enable Sync. on Vail and Telluride for a long time and redistribution still works fine.

So what in heaven is the benefit of Sync.? ... I know that we discussed this before but practically everything works. The thing is that i don't feel it.

Highly appreciate your response.



  • WAN Routing and Switching

Came up with new couple of issues in BGP

Redistribution of external ospf routes requires a different syntax for redistribute.

The link below may resolve some of your issues:



Re: Came up with new couple of issues in BGP


you might also use a loopback address to establish you iBGP peering.

That would fix your problem without redistributing external OSPF prefixes to BGP, I guess.


for details.

Ad Synchronization:

The purpose is to prevent blackhole routing in a case of multiple hops between iBGP peers.



"How BGP Selects Paths:

A router running Cisco IOS Release 12.0 or later does not select or use an iBGP route unless both of the following are true:

•The router has a route available to the next-hop.

•If synchronization is enabled, the router has received synchronized routes from an IGP.

BGP bases it's decision first on whether a path is loop free, then on the policies indicated by the path attributes along with the policies configured on the router. The following summarized how BGP chooses the best path to a given destination.

1 If the next hop is not reachable through an IGP route installed in the routing table, do not consider this prefix for installation in the routing table.

If the only route you have to the next hop indicated in the NEXT_HOP attribute of a prefix is learned through iBGP, the route will oscillate in the routing table. It will be installed by BGP, then removed about 60 seconds later, only to be reinstalled momentarily after it is deleted.

2 If the path is internal, synchronization is enabled, and the route is not in the IGP, do not consider the route."

I.e., imagine in your case:

The line between Vail and Telluride fails.

Your Telluride router would receive an iBGP prefix  for some AS 300 from Vail.

It would forward a packet to Aspen (the direct line to Vail is down).

In a case the Aspen router does not know the AS 300 prefix, it would drop the packet with AS 300 destination address.

When BGP synchronization is ON, the Telluride router will not use the iBGP prefix until it receives the same prefix via OSPF. Then it is sure the IGP router(s) know how to route  to the AS 300 destination.

And only after that it will aslo advertise the AS 300 prefix to the eBGP neighbor Alta.



This widget could not be displayed.