another thing to check however is ensure the no auto summary command :).

Regards,

Jason Baker
Network Engineer
MCSE, CCNA


-----Original Message-----
From: Jason Baker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 13, 2000 9:23 AM
To: 'Kevin Wigle'; cisco
Subject: RE: EIGRP


Hi Kevin,

i have found this happens on version 11 of the IOS. However that will
work on version 12 :).

Regards,

Jason Baker
Network Engineer
MCSE, CCNA

-----Original Message-----
From: Kevin Wigle [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 13, 2000 7:36 AM
To: cisco
Subject: EIGRP


Group,

In the lab again looking at a scenario.

At first, I configured a transit link with a /24 mask.

Later I thought - gee that's going to be a /29 or /30 in real life so I went
to change it.

However, the router wouldn't accept "network 200.1.1.0 0.0.0.7" under
"router eigrp 10".  It fails with the caret pointing at the first zero in
the wildcard mask.

doing a "?" after "network 200.1.1.0" just comes up with a <cr>.

However, on CCO I see examples of both statements - some with the mask
others without.

Has the behavior of EIGRP changed lately even so that CCO has conflicting
examples or am I missing some connection?

All routers have ip classless and ip subnet-zero configured.

By the way, my lab scenario has OSPF redistributing the EIGRP. Looking at an
upstream routing table it shows the EIGRP network as a /29 even though there
is no "mask" in the statement.

So what am I missing?

Kevin Wigle


_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to