From: DAN DORTON (DHSTS68@xxxxxxxxxxxxxxx)
Date: Wed Apr 24 2002 - 12:25:35 GMT-3
Does the EBGP router have routes back to the IBGP router that you are
pinging from?
Try a default-originate in the neighbor statement at the IBGP router
peering with the EBGP router, redistribute IGP routes into BGP, or
inject all the hops between the EBGP router & the IBGP router into BGP.
>>> Babacar Diop <babacard2000@yahoo.com> 04/24/02 09:34AM >>>
Thanks Lupy, i am understanding this better.
Based on what you said, if i were to advertise the
network connected to the ebgp neighbor in my igp then
the routers should get the routes.
After doing that, i still cannot ping the ebgp
neighbor from any ibgp neigh
Thanks
--- "Lupi, Guy" <Guy.Lupi@eurekaggn.com> wrote:
> If your routes are being passed to an IBGP neighbor
> from an EBGP neighbor,
> the next hop attribute remains the IP address that
> the EBGP neighbor is
> configured to send. If your IBGP neighbor does not
> know how to get to this
> address, the routes will never get installed. When
> you do the next-hop-self
> command, the router sends the update with itself as
> the next hop to the
> neighbor for which it is configured, so you are
> probably seeing a case where
> your internal router does not know how to get to the
> next hop of the EBGP
> routes, but when you give the next hop self command
> on the upstream router
> it can now get to the next hop and so installs the
> routes.
>
> ~-----Original Message-----
> ~From: Babacar Diop [mailto:babacard2000@yahoo.com]
> ~Sent: Wednesday, April 24, 2002 9:41 AM
> ~To: cciegroup
> ~Subject: neighbor next-hop-self
> ~
> ~
> ~Group,
> ~
> ~I am trying to understand the "neighbor
> next-hop-self"
> ~command. I know that it changes the next hop
> addrress
> ~on routing updates but how does it help me get
> routes
> ~(it is getting me routes that i would not get
> unless i
> ~put this command in).
> ~
> ~Thanks
> ~
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:18 GMT-3