Go CCIE Go!! - A Cisco Certified Internetwork Expert

Your internal devices will need to either have a route to that prefix, or a default route that funnels in to the correct egress point with connectivity to your destination prefix.
On Tue, May 27, 2008 at 12:41 PM, Chris Gray wrote:
> Hi, > > This may sound like a stupid question, but I have been studying now for 5 > days solid so my brain may be fried.. > > > I seem to have lost grip on BGP and how it interacts with IGP. > > I have a set of routes in by BGP table , for which the next hop is known > and > pingable by my IGP on the same router. When I try and ping the BGP routes I > get timeouts from an intermediate IGP router because it doesn’t know the > route to my BGP destination. It does however know the route to the BGP next > hop. > > If I put a static default route out to my BGP Backbone router in this > intermediate IGP router I get a ping, but this isn’t correct or practical.. > > Have tried all the usual next-hop-self tricks but this just changes the BGP > next hop to another IGP address which is also accessible through my IGP and > I get the same timeout. > > Have also advertised my LO0 networks in BGP and run an extended ping from > my > LO0 as source, makes no difference. > > I am definitely missing something here. > > Where am I going wrong people! > > Thanks in advance > > Kriz > > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html