[139747] in North American Network Operators' Group
Re: eigrp set next hop
daemon@ATHENA.MIT.EDU (Matt Newsom)
Mon Apr 18 22:44:18 2011
From: Matt Newsom <matt.newsom@RACKSPACE.COM>
To: David Swafford <david@davidswafford.com>
Date: Tue, 19 Apr 2011 02:43:23 +0000
In-Reply-To: <BANLkTikx7ma=m8_Sps75s-mJc62O9N-P=Q@mail.gmail.com>
Cc: Nanog <nanog@nanog.org>, Andrey Khomyakov <khomyakov.andrey@gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
How many bgp prefixes do you have? Can you just put statics on router 2?
On Apr 18, 2011, at 8:26 PM, "David Swafford" <david@davidswafford.com> wro=
te:
> What's the real goal behind this? What your describing sounds like a
> horrible band-aid....
>=20
> David.
>=20
> On Mon, Apr 18, 2011 at 5:08 PM, Andrey Khomyakov <
> khomyakov.andrey@gmail.com> wrote:
>=20
>> Hi nanog
>>=20
>> I need to advertise EIGRP route with a different next-hop value than self
>>=20
>> Due to how the connections are setup, I have to run BGP between two peers
>> that are 3 hops away from each other.
>>=20
>> router1--router2--firewall--router3
>> I'm running EBGP between router1 and router3
>> router1 is redistributing into EIGRP that's running with router2
>>=20
>> The problem is that now router2 thinks that router3 routes are reachable
>> via
>> router1 so I have myself a route loop.
>>=20
>> Is there a way to advertise an EIGRP route with next hop of router3 (or
>> firewall for that matter) rather than router1 which is what EIGRP does by
>> default
>>=20
>> Thank you in advance for advice.
>>=20
>> --
>> Andrey Khomyakov
>> [khomyakov.andrey@gmail.com]
>>=20
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of t=
he
individual or entity to which this message is addressed, and unless otherwi=
se
expressly indicated, is confidential and privileged information of Rackspac=
e.
Any dissemination, distribution or copying of the enclosed material is proh=
ibited.
If you receive this transmission in error, please notify us immediately by =
e-mail
at abuse@rackspace.com, and delete the original message.
Your cooperation is appreciated.
