[c-nsp] BGP redistribution into EIGRP

[Tim DeVries]

I thought of that but as far as I am aware that command under EIGRP
simply enforces whether or not the IGP will accept the default inbound
or outbound, it does not _originate_ the default IIRC.

Summarization is on because that is how the client had it configured, it
can be turned off.

I believe the correct answer to my problem is to redistribute with a
metric or use a default metric under EIGRP as Piotr mentioned.

Regards,

Tim

 

-----Original Message-----
From: Brant I. Stevens [mailto:branto at branto.com] 
Sent: Thursday, October 05, 2006 12:12 PM
To: Shakeel Ahmad; Tim DeVries
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] BGP redistribution into EIGRP


If you receive the default from BGP, why not use the
"default-information originate" under EIGRP instead of redistribution?
So long as the router has a default route, it will be announced in the
EIGRP domain.

On a separate note, any particular reason why you are using auto-summary
on your EIGRP process?


On 10/5/06 9:29 AM, "Shakeel Ahmad" <shakeelahmad at gmail.com> wrote:

> Can you verify on router-2 your 0.0.0.0 next hop (of RTR1) is
accessible ?
> 
> On 10/5/06, Tim DeVries <tdevries at icsbermuda.com> wrote:
>> 
>> 
>> Hi,
>> 
>> I'm working with a bit of a hokey setup w/ a private AS, and I need 
>> to redistribute the default into EIGRP from iBGP.  I'm working with -

>> Cisco Internetwork Operating System Software IOS (tm) C2600 Software 
>> (C2600-IK9O3S3-M), Version 12.3(6), RELEASE SOFTWARE (fc3).
>> 
>> So far I've configured it as follows:
>> -------------------------------------
>> router eigrp 100
>> redistribute static
>> redistribute bgp 65509 route-map check-def network 10.10.9.0 
>> 0.0.0.255 network 10.10.10.0 0.0.0.3 network 10.228.164.0 0.0.0.3 
>> network 10.228.170.0 0.0.0.31 network 10.228.171.0 0.0.0.255 network 
>> 10.228.181.0 0.0.0.3 auto-summary
>> 
>> router bgp 65509
>> no synchronization
>> bgp log-neighbor-changes
>> bgp redistribute-internal
>> neighbor 10.228.164.2 remote-as 65509 neighbor 10.228.164.2 
>> route-reflector-client neighbor 10.228.164.2 next-hop-self neighbor 
>> 10.228.164.2 distribute-list net_tovic out neighbor 207.228.x.y 
>> remote-as 65509 no auto-summary
>> 
>> ip prefix-list def-route seq 5 permit 0.0.0.0/0
>> 
>> route-map check-def permit 10
>> match ip address prefix-list def-route
>> ---------------------------------------------------
>> 
>> This setup is straight from a link I found on Cisco.
>> 
>> When I do a show ip eigrp top | inc 0.0.0.0 the route isn't making it

>> into  the EIGRP process.
>> 
>> However doing a sh ip route 0.0.0.0 shows it thinks it is being 
>> redistributed....
>> 
>> RTR2#sh ip route 0.0.0.0
>> Routing entry for 0.0.0.0/0, supernet Known via "bgp 65509", distance

>> 200, metric 0, candidate default path Tag 38xy, type internal 
>> Redistributing via eigrp 100  <-------------- Last update from 
>> 199.172.x.y 15:39:07 ago Routing Descriptor Blocks:
>> * 199.172.x.y, from 207.228.x.y, 15:39:07 ago
>>      Route metric is 0, traffic share count is 1
>>      AS Hops 1
>> 
>> RTR2#sh ip eigrp top 0.0.0.0/0
>> % IP-EIGRP (AS 100): Route not in topology table
>> ----------------------------------------------------------------
>> 
>> So, is there something else I need to do to make this work, or is 
>> this related to my version?  Anyone else had success with this?
>> 
>> Regards,
>> 
>> 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/
>> 
> _______________________________________________
> 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/