From: Sundar Palaniappan (sundar_palaniappan@xxxxxxxxxxx)
Date: Wed Mar 13 2002 - 01:18:55 GMT-3
Think you replied without reading my entire original post. Can you read the
post before replying.
There is no problem with layer1 or layer2. I clearly stated that "eigrp
neighbor" relationship is established and stable. My question was adding the
"network statement" works and why was "redistribute connected" not working.
Moroever, I didn't paste the entire config and pasted only the relavent
config for the problem to keep it short.
Anyway, I got the answer to that from other fellow members. I think, adding
a "metric" for the "redistribute connected" routes should resolve the
problem. But I won't be able to test that until Thursday as I would be out
on training tommorow.
>From: "Ahmed Mamoor Amimi" <mamoor@ieee.org>
>Reply-To: "Ahmed Mamoor Amimi" <mamoor@ieee.org>
>To: "John Neiberger" <neiby@ureach.com>, "Sundar Palaniappan"
><sundar_palaniappan@hotmail.com>, <ccielab@groupstudy.com>
>Subject: Re: Redistribute connected Question
>Date: Wed, 13 Mar 2002 08:37:48 +0500
>
>First of all troubleshoot from the local.....
>some points :
>- all the DLCI are given to main interface not to the sub, so u have to
>give
>a MAP or frame interface-dlci.
>- eigrp adjency are created as soon as the eigrp send the hello
>packet......
>remeber .... that in ur childhood u have
>learnt in CCNP that eigrp hellos are unreliable and form the adj as they
>send the packet.
>- check ur frame-relay map
>- try to do a refresh on fram-inverse arp ....
>-Now if all the points are ok then check if that
>Most of the troubles are with layer 2 ...... upper layer are friendly.
>
>-Mamoor
>
>
>----- Original Message -----
>From: John Neiberger <neiby@ureach.com>
>To: Sundar Palaniappan <sundar_palaniappan@hotmail.com>;
><ccielab@groupstudy.com>
>Sent: Wednesday, March 13, 2002 8:12 AM
>Subject: Re: Redistribute connected Question
>
>
> > 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:03 GMT-3