From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Mon Jan 10 2005 - 19:48:20 GMT-3
Tim,
What part of the solution are you referring to? It says right
there that the network type is changed:
<IEWB-RS>
Task 5.21
R4 (or R5):
router ospf 1
neighbor 130.1.45.5
R4 and R5:
interface BRI0/0
ip ospf network point-to-multipoint non-broadcast
R3 (or R5):
router ospf 1
neighbor 130.1.35.5
R3:
interface Serial1/1
ip ospf network point-to-multipoint non-broadcast
R5:
interface Serial0/0
ip ospf network point-to-multipoint non-broadcast
</IEWB-RS>
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> ccie2be
> Sent: Monday, January 10, 2005 4:36 PM
> To: Group Study
> Subject: IEWB lab 15 - lots of mistakes??
>
> Hey guys,
>
> Is it just me, or are there lots of mistakes in this lab and SG?
>
> For example, task 5.21 says to configure all adjacencies in area 345
in
> such a
> manner that other
>
> devices on the segment can't recieive ospf hello packets.
>
> The SG shows the neighbor 130.1.45.5 command used to do this, but when
I
> try
> to enter that command,
>
> here's what happens:
>
> Rack1R4(config)#router os 1
> Rack1R4(config-router)#nei 130.1.45.5
> OSPF: Neighbor command is allowed only on NBMA and point-to-multipoint
> networks
>
> So, I thought, no big deal. Even though it's not in the SG, I'll just
go
> and
> change the ospf network type
>
> on both sides of the link.
>
> After trying both network types, nbma and p2m, neither worked.
>
> Has anyone gotten the config shown in the solution guide to actually
work?
>
> TIA, Tim
>
>
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:21 GMT-3