[c-nsp] BGP --> EIGRP redistribution

Brant I. Stevens branto at branto.com
Mon Nov 22 17:49:11 EST 2004


There is a default metric already...


On 11/22/2004 05:39 PM, "Rodney Dunn" <rodunn at cisco.com> wrote:

> I don't have time to test this in the lab right
> now but just an idea too.
> 
> Configure a default-metric under
> the EIGRP process and see if the routes
> go in then.
> 
> I can't remember if the metric will be set
> for EIGRP with the set metric command
> in the route-map code.
> 
> Rodney
> 
> On Mon, Nov 22, 2004 at 05:27:40PM -0500, Brant I. Stevens wrote:
>> I have the same problem at work...
>> 
>> The funny thing is that the route in question is originated on another
>> router via static-->bgp redistribution, and makes it into the router that is
>> supposed to take it from BGP and put it into EIGRP.  The prefix is in the
>> routing table, but doesn't get into the EIGRP topology table.  Are these the
>> symptoms you are seeing?
>> 
>> What platform are you using?  One of my team members told be that clearing
>> the route makes it redistribute properly.
>> 
>> 
>> On 11/22/2004 04:03 PM, "Tim Devries" <tdevries at northrock.bm> wrote:
>> 
>>> No, I did not have that command entered.  BGP config in this instance is
>>> extremely simple, sync disabled, and basically the only routes I have in the
>>> table are the two routes I would like to redistribute.
>>> 
>>> What confuses me about the command you suggest is that I also tried to
>>> redistribute these two routes from BGP into EIGRP on my edge router, which
>>> holds these routes in its BGP table as being of external origin.  It didn't
>>> work there either.  From my understanding the command "bgp
>>> redistribute-internal" is only for iBGP learned routes?
>>> 
>>> In any case, thanks for the suggestion!
>>>   
>>> Tim
>>> 
>>> 
>>> -----Original Message-----
>>> From: Earls, Michael [mailto:Michael.Earls at 53.com]
>>> Sent: Monday, November 22, 2004 4:56 PM
>>> To: 'Tim Devries'; 'cisco-nsp'
>>> Subject: RE: [c-nsp] BGP --> EIGRP redistribution
>>> 
>>> 
>>> 
>>> Can you add your BGP config? Do you have "bgp redistribute-internal" under
>>> router bgp ASN.
>>> 
>>> Michael
>>> 
>>> Michael
>>> 
>>> PGP Info: KeyID 0x0DFD993C
>>> Fingerprint F903 0325 5105 2CDB 4BF4 C88B 72F7 BA7A 28CC 598A
>>> 
>>> 
>>> -----Original Message-----
>>> From: Tim Devries [mailto:tdevries at northrock.bm]
>>> Sent: Monday, November 22, 2004 3:42 PM
>>> To: 'cisco-nsp'
>>> Subject: [c-nsp] BGP --> EIGRP redistribution
>>> 
>>> 
>>> Hi,
>>> 
>>> I've recently attempted redistribution of two networks learned from bgp into
>>> 
>>> my igp (EIGRP) using a route map.
>>> 
>>> Basic configuration looks like this:
>>> 
>>> !
>>> router eigrp xxxyy
>>>  redistribute connected
>>>  redistribute static
>>>  redistribute bgp xxxyy route-map BGP-EIGRP-Redist
>>> !
>>> !
>>> route-map BGP-EIGRP-Redist permit 1
>>>  match ip address prefix-list GlobalNetworks
>>>  set metric 6500 1 255 1 1500
>>> !
>>> 
>>> ip prefix-list GlobalNetworks seq 1 permit 206.x.x.x/17
>>> ip prefix-list GlobalNetworks seq 2 permit 152.x.x.x/16
>>> 
>>> 
>>> When I do a 'show ip eigrp top 206.x.x.x/17', it returns "%
>>> IP-EIGRP (AS xxxyy): Route not in topology table".
>>> 
>>> On this router the bgp routes are learned via iBGP, however I have tried to
>>> redistribute these two routes into EIGRP on other routers in my AS that
>>> learn these routes directly from the peer (routes are tagged
>>> external) and I've had no luck there either.
>>> 
>>> Is there something I am missing?  I feel like I have tried every
>>> configuration from here to sundry, but nothing will redistribute from BGP
>>> into EIGRP.  The connected and static networks redistribute without issue.
>>> 
>>> Thanks in advance,
>>> 
>>> Tim
>>> _______________________________________________
>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>> 
>>> 
>>> This e-mail transmission contains information that is confidential and may
>>> be privileged.   It is intended only for the addressee(s) named above. If
>>> you receive this e-mail in error, please do not read, copy or disseminate it
>>> in any manner. If you are not the intended recipient, any disclosure,
>>> copying, distribution or use of the contents of this information is
>>> prohibited. Please reply to the message immediately by informing the sender
>>> that the message was misdirected. After replying, please erase it from your
>>> computer system. Your assistance in correcting this error is appreciated.
>>> _______________________________________________
>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>> 
>> 
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/




More information about the cisco-nsp mailing list