RE: IE LAB 17 task 4.1 - for the Brians please

From: Plank, Jason (JPlank@concordefs.com)
Date: Mon Apr 17 2006 - 16:00:18 GMT-3


Perhaps you could try labbing it up? As long as the DR/BDR and some other
things are compatabile you shouldn't have a problem. This could even be a
work-around for something in the lab.

 

I just did to confirm what I thought I already knew:

 

R2#show ip ospf int

Serial0 is up, line protocol is up

  Internet Address 192.168.1.2/30, Area 0

  Process ID 1, Router ID 2.2.2.2, Network Type BROADCAST, Cost: 64

  Transmit Delay is 1 sec, State BDR, Priority 1

  Designated Router (ID) 172.16.8.1, Interface address 192.168.1.1

  Backup Designated router (ID) 2.2.2.2, Interface address 192.168.1.2

  Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5

    Hello due in 00:00:11

  Index 1/1, flood queue length 0

  Next 0x0(0)/0x0(0)

  Last flood scan length is 1, maximum is 2

  Last flood scan time is 0 msec, maximum is 4 msec

  Neighbor Count is 1, Adjacent neighbor count is 1

    Adjacent with neighbor 172.16.8.1 (Designated Router)

  Suppress hello for 0 neighbor(s)

Loopback99 is up, line protocol is up

  Internet Address 198.192.7.1/24, Area 0

  Process ID 1, Router ID 2.2.2.2, Network Type LOOPBACK, Cost: 1

  Loopback interface is treated as a stub Host

R2#show ip ro ospf

     172.16.0.0/16 is variably subnetted, 10 subnets, 2 masks

O 172.16.1.1/32 [110/65] via 192.168.1.1, 00:00:20, Serial0

r4#show ip ospf int

Serial0 is up, line protocol is up

  Internet Address 192.168.1.1/30, Area 0

  Process ID 1, Router ID 172.16.8.1, Network Type NON_BROADCAST, Cost: 64

  Transmit Delay is 1 sec, State DR, Priority 1

  Designated Router (ID) 172.16.8.1, Interface address 192.168.1.1

  Backup Designated router (ID) 2.2.2.2, Interface address 192.168.1.2

  Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5

    Hello due in 00:00:18

  Index 1/1, flood queue length 0

  Next 0x0(0)/0x0(0)

  Last flood scan length is 1, maximum is 1

  Last flood scan time is 0 msec, maximum is 0 msec

  Neighbor Count is 1, Adjacent neighbor count is 1

    Adjacent with neighbor 2.2.2.2 (Backup Designated Router)

  Suppress hello for 0 neighbor(s)

Loopback21 is up, line protocol is up

  Internet Address 172.16.1.1/24, Area 0

  Process ID 1, Router ID 172.16.8.1, Network Type LOOPBACK, Cost: 1

  Loopback interface is treated as a stub Host

r4#show ip ro ospf

     198.192.7.0/32 is subnetted, 1 subnets

O 198.192.7.1 [110/65] via 192.168.1.2, 00:01:13, Serial0

 

HTH,

 

-------------------

Jason Plank

Network Engineer

101 Bellevue Parkway

Wilmington, DE 19809

E-mail: JPlank@concordefs.com

Phone: 302-793-5913

 

 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
CCIEin2006
Sent: Monday, April 17, 2006 2:30 PM
To: Plank, Jason
Cc: Brian McGahan; ccielab@groupstudy.com
Subject: Re: IE LAB 17 task 4.1 - for the Brians please

 

You can match the timers to force adjacency but from my experience no routes

will be learned. If you look at the OPSF database it will show "Adv router

is not-reachable." Therefore while the connection might look like its up in

fact you are not learning any routes.

 

Brian can you confirm or negate this statement?

 

 

On 4/17/06, Plank, Jason <JPlank@concordefs.com> wrote:

>

> You can have the network types mismatch, but the TIMERS have to match.

>

> -------------------

> Jason Plank

> Network Engineer

> 101 Bellevue Parkway

> Wilmington, DE 19809

> E-mail: JPlank@concordefs.com

> Phone: 302-793-5913

>

>

> -----Original Message-----

> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of

> CCIEin2006

> Sent: Monday, April 17, 2006 2:01 PM

> To: Brian McGahan

> Cc: ccielab@groupstudy.com

> Subject: Re: IE LAB 17 task 4.1 - for the Brians please

>

> Cool - but won't that result in OSPF network type mismatch? Isn't that a

> bad

> thing?

>

> On 4/17/06, Brian McGahan <bmcgahan@internetworkexpert.com> wrote:

> >

> > Okay so the spokes are using the main interface in Frame Relay

> > which results in the OSPF network type of non-broadcast. R5 has a

> > multipoint subinterface. Restrictions are don't use the neighbor

> statement

> > and don't use any interface commands on R1 and R2. This means that R1

> and

> > R2 will stay non-broadcast with the default timers. So to solve this

> set

> > the OSPF network type to broadcast on R5's interface and match the

> timers

> > with R1 and R2's non-broadcast.

> >

> > HTH,

> >

> > 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/

> >

> > ________________________________________

> > From: CCIEin2006 [mailto:ciscocciein2006@gmail.com]

> > Sent: Monday, April 17, 2006 9:07 AM

> > To: Brian McGahan

> > Cc: ccielab@groupstudy.com

> > Subject: Re: IE LAB 17 task 4.1 - for the Brians please

> >

> > Yes but theworkbook specifically states do not use neighbor

> > statements.Itdid not say do notuse neighbor statements on the spokes

> which

> > would haveled me to believe that itwas okay to use on the hub. Do you

> see

> > what I mean?

> >

> >

> > On 4/15/06, Brian McGahan <bmcgahan@internetworkexpert.com> wrote:

> > It doesn't require neighbor statements on the spokes but it does on the

> > hub.

> >

> > HTH,

> >

> > 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

> > > CCIEin2006

> > > Sent: Saturday, April 15, 2006 12:37 PM

> > > To: ccielab@groupstudy.com

> > > Subject: IE LAB 17 task 4.1 - for the Brians please

> > >

> > > This question is for Brian Dennis or Brian McGahan but anyone else can

> > > feel

> > > free to chime in.

> > >

> > > Regarding IE version 3 Volume 1, Lab 17, task 4.1:

> > >

> > > The task states to configure OSPF between R1, R2, and R5 which are

> > > connected

> > > by a multipoint frame relay network with R5 as the hub.

> > >

> > > The task states to NOT use the neighbor command to accomplish this and

> > it

> > > also states not to use any interface level commands on R1 or R2 (which

> > > rules

> > > out changing the ospf network type on these routers).

> > >

> > > Your solution states to use ospf network type non-broadcast and does

> > not

> > > include any neighbor statements.

> > >

> > > Aren't you required to use neighbor statements when configuring

> > > non-broadcast?

> > >

> > > I tried your solution but adjacency is not being established across

> > the

> > > frame relay network.

> > > What is the correct solution?

> > >

> > > Thanks in advance!

> > >

> > >

> > _______________________________________________________________________

> > > Subscription information may be found at:

> > > http://www.groupstudy.com/list/CCIELab.html

>

> _______________________________________________________________________

> Subscription information may be found at:

> http://www.groupstudy.com/list/CCIELab.html

>

> -----------------------------------------

> The information in this message may be proprietary and/or

> confidential, and protected from disclosure. If the reader of this

> message is not the intended recipient, or an employee or agent

> responsible for delivering this message to the intended recipient,

> you are hereby notified that any dissemination, distribution or

> copying of this communication is strictly prohibited. If you have

> received this communication in error, please notify First Data

> immediately by replying to this message and deleting it from your

> computer.

 



This archive was generated by hypermail 2.1.4 : Mon May 01 2006 - 11:41:57 GMT-3