From: John Neiberger (neiby@xxxxxxxxxx)
Date: Wed Mar 13 2002 - 00:12:10 GMT-3
The only thing I can think of is that the ethernet interface
wasn't up/up so it probably wasn't in the routing table of
either router.
Well, I just thought of one other thing. You don't have a
default-metric set and I think EIGRP requires a default metric
before redistribution will occur.
Regards,
John
---- On Tue, 12 Mar 2002, Sundar Palaniappan
(sundar_palaniappan@hotmail.com) wrote:
> There are two routers running EIGRP in a hub-and-spoke
topology with a
> frame-relay connection between them.
>
>
> Here is the configuration:
>
> Router A:
>
> interface serial0.2
> ip address 192.168.10.1 255.255.255.252
>
> router eigrp 200
> network 192.168.10.0
> no auto-summary
>
>
> Router B:
>
> interface e0
> ip address 172.16.0.1 255.255.0.0
>
> interface serial0.1
> ip address 192.168.10.2 255.255.255.252
>
> router eigrp 200
> network 192.168.10.0 (serial0.1)
> redistribute connected
> no auto-summary
>
>
>
> EIGRP neighbor relationship is established. With this setup,
I am
> thinking I
> should be able to ping the ethernet interface of Router B but
I can't.
>
> I checked the route table on Router A and I don't see a route
to
> 172.16.0.0
> subnet.
>
> When I removed "redistribute connected" and put the network
statement
> (172.16.0.0) under the EIGRP process on Router B and it WORKS.
>
> Just curious to know why "redistribute connected" doesn't
work.
>
> Thanks,
> Sundar
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:02 GMT-3