From: ying c (bf5tgh1@xxxxxxxxx)
Date: Thu Aug 15 2002 - 15:27:42 GMT-3
Hi,
>From R2's point of view, you get the route from 2
sources, one from the eigrp redistribution (AD 170),
you also get it from R3's RIP (AD 120). That's why you
get that result. To fix the problem, you can try the
following in R2's rip routing process:
distance 175 192.168.234.3 0.0.0.0 5
access-list 5 permit 0.0.0.0 0.0.0.0
which will only check the default route and raise its
AD to 175 so R2 will select the route from eigrp. R3
is kind of mirroring R2, you have to do apply the same
thing there too.
You may want to check Doyle I's redistribution
chapter, it has more detail explainations.
Chang
--- Claudine DEMAR <lkcnet00@hotmail.com> wrote:
> Scenario & problem: Propagating a default route from
> eigrp to rip caused a
> routing loop ??
>
> |lo0 192.168.1.0/24
> R1
> / \
> / \
> R2 R3
> | |
> -------- 192.168.234.0/24
>
>
> Serial hsrp connections between R1-R2
> (192.168.12.0/24) and R1-R3
> (192.168.13.0/24) are running EIGRP
> R2 and R3 are on an Ethernet segment which is
> running RIPv2.
>
> R1:
> router eigrp 1
> net 192.168.1.0
> net 192.168.13.0
> net 192.168.12.0
>
>
> R2:
> router eigrp 1
> redistribute rip metric 10000 1000 254 1 1500
> net 192.168.12.0
>
> router rip
> ver 2
> redistribute eigrp 1 metric 14
> net 192.168.234.0
>
>
> R3:
> router eigrp 1
> redistribute rip metric 10000 1000 254 1 1500
> net 192.168.13.0
>
> router rip
> ver 2
> redistribute eigrp 1 metric 2
> net 192.168.234.0
>
>
> The problem appeared when the I wanted to propagate
> a default route.
> Lo0 of R1 is supposed the default route.
>
> On R1:
> ip default-net 192.168.1.0
>
> This causes the 192.168.1.0 tagged as the default
> route in the EIGRP cloud.
> This is redistributed in RIP but I did not expect R2
> and R3 to have both
> default routes pointing to each other:
> R2:
> route 0.0.0.0/0 metric 2, next-hop is R3
>
> R3:
> route 0.0.0.0/0 metric 14, next-hop is R2
>
> This default route never times out !!!! I expected
> to have R2 pointing to R3
> but not R3 pointing to R2.
> This RIP and this default route is definitively
> behaving wierdly.
> I know split horizon might be involved but I don't
> understand why there's no
> timeout of the route whereas each router does not
> receive any updates from
> the other ....
>
> Anybody have an explanation for this ??
>
>
> The solution I found was to advertise 0.0.0.0 to R2
> and R3 as a EIGRP
> internal route (distance 90).
> In order to do that I just defined net 0.0.0.0 under
> router eigrp in R1.
> The problem with that is that all connected
> interfaces are advertised with
> that network statement.
>
> Any other suggestions ?
>
>
>
>
>
>
>
>
>
>
>
>
>
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:26 GMT-3