From: Roman Rodichev (rodic000@xxxxxxxxxxx)
Date: Sun May 20 2001 - 15:54:32 GMT-3
Roddie Thank you!
I was about to go to my lab and do exactly the same thing that you just did.
Set-up hub, two spokes, ip ospf netw point-to-multipoint on all 3 routers,
no frame maps on the spokes to other spokes. This is enough for spokes to
access other spokes and their routes.
John, do you still disagree?
I think the problem of our discussion was simply the matter of how one
understands the given question or problem. I will repeat myself again. I I
think that when you are not allowed to use frame maps, "ip ospf network"
will save you by doing frame map's job at Layer3. Frame map will point one
spoke to another spoke via certain DLCI. Your traffic will be going across
HUB. "ip ospf network" will create /32 routes that will point one spoke to
another spoke via hub's IP address.
And since we weren't allowed to use "ip ospf network", we had to use the
third way - policy routing.
And please stop mentioning timers, NBMA, DR election. I know that we need to
specify OSPF prirority 0 on spokes, and that we need to match timers on all
routers. This is not what we were talking about!
Good luck on your lab, Roddie, and thank you one more time, you saved me a
trip to my lab.
Roman
>From: Roddie Hasan <roddie@krweb.net>
>To: John Kaberna <jkaberna@netcginc.com>
>CC: Roman Rodichev <rodic000@hotmail.com>, <ccielab@groupstudy.com>
>Subject: Re: Redistributing OSPF into IGRP - Policy routing
>Date: Sun, 20 May 2001 12:26:15 -0500 (CDT)
>
>John - "The ip ospf network command only sets the timers. Go look it up."
>
>Roman - "This command is not just about timers. Can some one back me up?"
>
>Roman - "Are you saying that if you couldn't use frame maps on the spokes
>and could use "ip ospf network statement we would still have a problem?"
>
>John - "Your wrong. I'll let everyone else try and help you. I give up.
>Good luck! LOL"
>
>Now, I don't know if it was just a matter of John not reading carefully or
>really understanding what Roman was saying (see third quote above) or
>what. I'm not here to settle any arguments except to make sure that any
>candidates don't walk away with inaccurate technical information about
>OSPF - That is, the power of the "ip ospf network" command.
>
>R14 - hub
>R3 - spoke
>R5 - spoke
>
>Configs at the bottom..
>
>R3#ping 1.1.1.5
>Type escape sequence to abort.
>Sending 5, 100-byte ICMP Echos to 1.1.1.5, timeout is 2 seconds:
>!!!!!
>
>Host entry in R3's routing table:
>O 1.1.1.5/32 [110/128] via 1.1.1.14, 00:11:48, Serial1
>
>R5#ping 1.1.1.3
>Type escape sequence to abort.
>Sending 5, 100-byte ICMP Echos to 1.1.1.3, timeout is 2 seconds:
>!!!!!
>
>Host entry in R5's routing table:
>O 1.1.1.3/32 [110/128] via 1.1.1.14, 00:13:05, Serial1
>
>All Routers
>-----------
>router ospf 1
> network 0.0.0.0 255.255.255.255 area 0
>
>R14
>---
>interface Serial0.1 multipoint
> ip address 1.1.1.14 255.255.255.0
> ip ospf network point-to-multipoint
> ip ospf priority 200
>
>R3
>--
>interface Serial1
> ip address 1.1.1.3 255.255.255.0
> encapsulation frame-relay
> ip ospf network point-to-multipoint
>
>R5
>--
>interface Serial1
> ip address 1.1.1.5 255.255.255.0
> encapsulation frame-relay
> ip ospf network point-to-multipoint
>
>And for those who bothered to read down this far ;-)
>
>/home/roddie$ sh datescript
>* 2 days left until the lab! *
>
>Regards, Roddie
>--
><>> Roddie Hasan CCNP, CCDP, SCSA, MCSE - Sprint E|Solutions
><>> Technology Solutions Consultant - Dallas, Texas
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:46 GMT-3