Re: distance command under ospf

Hey Joe,

Sure didn't. I thought about doing that, but the context sesitive help
implied "source of the route" and asked for a wildcard mask. I can't
remember exactly what it said, I'm not in front of the console at the
moment. But if the router ID is required.... this is probably what was
messing me up!

If it needs a router ID what do I put for the wildcard mask? 0.0.0.0 ?

Chris

On Sun, May 17, 2009 at 8:54 PM, Joe Astorino <jastorino_at_ipexpert.com>wrote:

> Hey Chris, remember that with OSPF and distance you have to specify the RID
> of the advertising router, not necessarily the ip address. Did you do that?
>
>
> Regards,
>
> Joe Astorino
> CCIE #24347 (R&S)
> Sr. Support Engineer  IPexpert, Inc.
> URL: http://www.IPexpert.com <http://www.ipexpert.com/>
>
>
> -----Original Message-----
> From: Chris Breece <cbreece1_at_gmail.com>
>
> Date: Sun, 17 May 2009 18:56:25
> To: Cisco certification<ccielab_at_groupstudy.com>
> Subject: distance command under ospf
>
>
> Guys,
>
> I was working on a scenario today and got some results I wasn't expecting.
> I
> didn't save my exact configs, but I put together the basics of how it was
> setup below. If there are any typos, sorry, I did it in notepad.
>
>
> R1
> router ospf 1
> network 10.10.10.1 0.0.0.0 area 0
> redis connected route-map redis-connected metric 10 metric-type 1 subnets
> !
> interface fa0/0
> ip address 10.10.10.1 255.255.255.0
> !
> interface fa0/1
> ip address 192.168.0.1 255.255.255.0
> !
> route-map redis-connected permit 10
> match interface fa0/1
>
>
> R2
> router ospf 1
> network 10.10.10.2 0.0.0.0 area 0
> distance 180 10.10.10.0 0.0.0.255 external-routes
> !
> int fa0/0
> ip address 10.10.10.2 255.255.255.0
> !
> ip access-list standard external-routes
> permit 192.168.0.0 0.0.0.255
>
>
> The scenario was that I wanted any routes learned by R2 from R1 that were
> "external" to have an AD of 180. The two routers are connected via their
> Fa0/0 interfaces. R1's Fa0/1 has the subnet that will be brought into OSPF
> as an external... and I was attempting to match this route via the
> access-list attached to the distance command under the OSPF process on R2.
>
> After I set this up, I looked at R2's routing table and R2 had learned it
> via OSPF with an AD of 110. If I changed the 192.168.0.0/24 subnet to be
> apart of Area 0, rather than an external it changed the AD to 180.
>
> Also, when I used "distance ospf external 180" this worked fine. However,
> it
> messed up some other requirements in the scenario, so I couldn't use it.
>
>
> Is this behavior normal? Does the "distance" command not work with
> externals? Or is it that I was probably just doing something wrong
> elsewhere?
>
> Chris
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Sun May 17 2009 - 21:03:13 ART