Re: Regarding EIGRP on Serial FR Link ( R2 <------>. R1)

Do the following steps..
Ping the neighbor router with small packets usually 100 byte and then go on
till 1400 byte packet ..

If this does not work..possible causes would be high cpu, incorrect
interface acl's, layer 1 layer 2 problem interface errors etc.

If it does work, check the routing table entry for neighbor interface ip,
see if it has the correct next hop address. If something is wrong here then
you need to check misconfiguration like the neighbor not being on the
correct physical interface. It would mostly be a routing issue.

Do these checks on both routers.

-Hoogen

On Tue, Aug 25, 2009 at 5:36 PM, Mark Matters <markccie_at_gmail.com> wrote:

> Have you checked your frame maps?
>
> On Tue, Aug 25, 2009 at 6:59 PM, Raghav Bhargava <
> raghavbhargava12_at_gmail.com
> > wrote:
>
> > HI experts,
> > What could be the issue if we get this error message on the serial
> > interface
> > of a Router:-
> >
> > *Mar 27 23:22:33.795: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
> > 183.1.123.1 (Serial1/0) is down: retry limit exceeded
> >
> >
> > --
> > Warm Regards
> > Raghav
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
>
>
> -
> "The more I learn the less I know". This is incredibly frustrating to me.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Tue Aug 25 2009 - 17:52:41 ART