From: Adam Quiggle (aquiggle@xxxxxxxxx)
Date: Sun Jan 13 2002 - 16:01:21 GMT-3
Stevie,
Small clarification, how is this the opposite? You are taking a RIP route
and distributing it into EIGRP, that's exactly how I'd configure a
distribute list using IP.
Thanks,
AQ
p.s. nice solution.
At 01:17 PM 1/13/02, Stephen Oliver wrote:
>Redistribution and distribute lists work opposite in IPX from how they
>work in IP.
>
>This will work for what you want.
>
>On R4
>
>
>ipx router eigrp 1
>distribute-list 800 out rip
>network DAB
>
>access-list 800 permit AAAA
>access-list 800 deny -1
>
>DAB is my EIGRP network from R4 to R1.
>The command in effect says use list 800 for redistribution OUT of RIP and
>into EIGRP
>
>Stevie.
>
>
>>From: "Markus Haas" <mh@nmc-m.dtag.de>
>>Reply-To: "Markus Haas" <mh@nmc-m.dtag.de>
>>To: "Ccielab" <ccielab@groupstudy.com>
>>Subject: Filtering IPX networks between RIP and EIGRP
>>Date: Sun, 13 Jan 2002 17:38:05 +0100
>>
>>Hi,
>>
>>I'am playing with manual redistribution between IPX RIP and IPX EIGRP.
>>
>>Scenario:
>>
>>
>>|--- IPX-RIP --- <R4> --- IPX EIGRP --- <R1>
>>
>>
>>R1 knows some IPX networks via IPX RIP. From this IPX networks I only want to
>>propagate one into EIGRP.
>>I tried this via an distribute-list out on the RIP process, but the networks
>>will not be filtered
>>and I still see all RIP networks on R1 learned via EIGRP.
>>
>>Anyone knows a solution for me ?
>>
>>
>>
>>Config R4:
>>==========
>>
>>access-list 800 permit AAAA
>>access-list 800 deny -1
>>!
>>!
>>!
>>ipx router eigrp 100
>> network 103
>> network 101
>> log-neighbor-changes
>>!
>>!
>>ipx router rip
>> no redistribute eigrp 100
>> distribute-list 800 out eigrp 100
>> no network 101
>> no network 103
>>
>>
>>
>>R4# sh ipx route
>>Codes: C - Connected primary network, c - Connected secondary network
>> S - Static, F - Floating static, L - Local (internal), W - IPXWAN
>> R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate
>> s - seconds, u - uses, U - Per-user static
>>
>>13 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
>>
>>No default route known.
>>
>>C 10 (SNAP), Et0
>>C 101 (PPP), Se0
>>C 103 (FRAME-RELAY), Se1
>>E 102 [2681856/0] via 101.1111.1111.1111, age 00:02:09,
>> 1u, Se0
>>E 104 [2707456/1] via 103.0005.0033.1c1c, age 00:02:09,
>> 1u, Se1
>>E 204 [270336000/2] via 103.0005.0033.1c1c, age 00:02:09,
>> 1u, Se1
>>E 205 [270336000/2] via 103.0005.0033.1c1c, age 00:02:09,
>> 1u, Se1
>>R AAAA [02/01] via 10.0000.0c05.6009, 11s, Et0
>>R BBBB [02/01] via 10.0000.0c05.6009, 11s, Et0
>>R CCCC [02/01] via 10.0000.0c05.6009, 11s, Et0
>>R DDDD [02/01] via 10.0000.0c05.6009, 32s, Et0
>>R EEEE [02/01] via 10.0000.0c05.6009, 32s, Et0
>>R FFFF [02/01] via 10.0000.0c05.6009, 32s, Et0
>>R4#
>>
>>
>>This see R1:
>>============
>>
>>R1#sh ipx route
>>Codes: C - Connected primary network, c - Connected secondary network
>> S - Static, F - Floating static, L - Local (internal), W - IPXWAN
>> R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate
>> s - seconds, u - uses, U - Per-user static
>>
>>13 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
>>
>>No default route known.
>>
>>[SNIP]
>>
>>E AAAA [269824000/2] via 101.4444.4444.4444, age 00:01:04,
>> 1u, Se0
>>E BBBB [269824000/2] via 101.4444.4444.4444, age 00:01:04,
>> 1u, Se0
>>E CCCC [269824000/2] via 101.4444.4444.4444, age 00:01:04,
>> 1u, Se0
>>E DDDD [269824000/2] via 101.4444.4444.4444, age 00:01:04,
>> 1u, Se0
>>E EEEE [269824000/2] via 101.4444.4444.4444, age 00:01:04,
>> 1u, Se0
>>E FFFF [269824000/2] via 101.4444.4444.4444, age 00:01:04,
>> 1u, Se0
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:27 GMT-3