RE: preferring OSPF inter-area compared to intra-area

That's correct, those options are not supported. A lot of the documentation
is repeated syntax-wise for features that may not be actually applicable. For
example the distribute-list with match ip next-hop may not work for OSPF even
though it is still documented under that feature.

You will actually find that a lot of documentation examples are flat out wrong
once you try to implement them. However as a CCIE candidate it's up to you to
actually implement these and find out what's right and wrong ;)

Brian McGahan, CCIE #8593 (R&S/SP/Security)
bmcgahan_at_INE.com<mailto:bmcgahan_at_INE.com>

Internetwork Expert, Inc.
http://www.INE.com

From: ccie99999 [mailto:ccie99999_at_gmail.com]
Sent: Monday, January 07, 2013 9:09 PM
To: Brian McGahan
Cc: Carlos G Mendioroz; Cisco certification
Subject: Re: preferring OSPF inter-area compared to intra-area

Thanks for your reply Brian..
I see your point about filtering the RIB and not what OSPF chooses. ( I didn't
realize this before actually)
What I was complaining is that route-map matching ip next-hop or matching ip
route-source is not working when applied with a distribute list inbound to
ospf.
Strange I don't find any official reference on this scenario.

On Mon, Jan 7, 2013 at 6:08 PM, Brian McGahan
<bmcgahan_at_ine.com<mailto:bmcgahan_at_ine.com>> wrote:
This filters the RIB (routing table), not the OSPF decision process. By the
time you apply this OSPF has already chosen the intra area route over the
inter area one, so all you can do is permit or deny the intra area one.

The only way to really accomplish this is to make the two route types equal.
If you were to change the inter area route to intra area with something like a
virtual link or tunnel then you can modify which path is preferred.

--
@ccie99999
Blogs and organic groups at http://www.ccie.net