From: Luca Hall (lhall@setnine.com)
Date: Tue May 27 2008 - 14:54:36 ART
run bgp full mesh or redistribute those bgp routes into igp, this
is the exact reason for bgp sync.
if you have a---b---c with a & c running bgp knowing a bgp route 1.2.3.0
and b not running bgp and not knowing 1.2.3.0 theres no way b will
ever know what to do with it.
----- Original Message -----
From: Chris Gray <chris.gray@ozonenetworks.net>
To: ccielab@groupstudy.com
Sent: Tue, 27 May 2008 13:41:44 -0400 (EDT)
Subject: Having a bad moment with BGP / IGP
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
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2008 - 06:59:18 ART