In a message dated 12/12/00 1:31:04 PM Eastern Standard Time,
[EMAIL PROTECTED] writes:
> I have configured Eigrp on some routers in our WAN
> > (i.e the one that i want
> > to have eigrp working), but some of the routes are
> > not advertised
> > ,everything else is correct ie same AS Number same
> > Hello-interval and hold
> > Time plus all routers form neighbor relationships,
> > When running sh ip eigrp topology the following is
> > what i get on the problem
> > routers:
> >
> > P 192.168.8.128/26, 0 successors, FD is Inaccessible
> > via 192.168.1.65 (22073600/11561472),
> > Serial0/0
> > P 192.168.9.128/26, 0 successors, FD is Inaccessible
> > via 192.168.1.65 (22073600/21561600),
> > Serial0/0
> > P 192.168.9.64/26, 0 successors, FD is Inaccessible
> > via 192.168.1.65 (22073600/21561600),
> > Serial0/0
> > P 192.168.1.60/30, 1 successors, FD is 21024000
> > via 192.168.1.65 (21024000/1761792),
> > Serial0/0
> > P 192.168.1.12/30, 1 successors, FD is 21536000
> > via 192.168.1.65 (21536000/2273792),
> > Serial0/0
> > P 192.168.1.20/30, 1 successors, FD is 21536000
> > via 192.168.1.65 (21536000/11023872),
> > Serial0/0
> > P 192.168.1.208/30, 1 successors, FD is 21536000
> > via 192.168.1.65 (21536000/11023872),
> > Serial0/0
> > P 172.16.0.0/19, 1 successors, FD is 21587200
> >
> > The routes that are not advertised are the one with
> > FD is Inaccessible
> > can you please tell me what is wrong ??
>
Ok lets start to break this down. Who is that 192.168.1.65? On that device,
are there any access lists preventing these certain routes? From looking
closer, it seems the Net of 192.168.1.x has no issues getting through via
192.168.1.65, but the 192.168.9.x and 192.168.8.x networks do. Are you sure
you didn't overlook these being on different subnets and maybe forgot to
advertise them separately? Try checking out your network statements and being
absolutely sure they are correct. You may then want to try and debug ip
eigrp... There could be many things wrong and I'd like to help but you have
to be sure that the basics are checked and there are no simple issues at play
here. You may want to give us a config example also...good hunting...
PS, Let me know what interface these networks are on. For example, they are
trying to get there via s0/0. I'm guessing that the 192.168.1.x net it on
s0/0 and the 192.168.9.x and 192.168.8.x networks are on a different
interface...hmmm, just thinking out loud...let us know.
Mark Zabludovsky ~ CCNA, CCDA, 1/2-NP
<A HREF="mailto: [EMAIL PROTECTED]">[EMAIL PROTECTED]</A>
"Even if I knew I had only 1 more week to live, I would still schedule
my CCIE lab. I would just have to work a little harder I guess. After all,
without any goals in life, I'm dead already."
~Mark Zabludovsky~
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
