RE: Route Map Logic

From: Lupi, Guy (Guy.Lupi@xxxxxxxxxxxxx)
Date: Thu Mar 07 2002 - 19:34:02 GMT-3


   
This first entry says match access list 1, if there is a match permit the
route and do nothing to it.

route-map local_only permit 10
 match ip address 1

This second statement says match any route (excluding what was already
matched in access list 1 which would not be passed to this sequence number
of the route map) and set its community to no export.

route-map local_only permit 20
 set community no-export

This could be used for a situation where you have a few routes for which you
don't want no-export set, you match those in the first statement, since
there is a match it does not continue on to the next statement. Then all
other routes have community no export set, matching anything that was not
matched in access list 1. If there is no match statement it means match
everything.

This first entry says match access list 1, and prepend the as path with 300
400 500. Now if the route map stopped here, no routes but those that
matched access list 1 would be advertised.

route-map prepend permit 10
match ip address 1
set as-path prepend 300 400 500
!

This second entry has no match statement, which means match everything.
There is no set statement, so nothing is being done. Essentially this is so
that any other routes that were not matched in a previous entry in the route
map will still be advertised.

route-map prepend permit 20

There are a lot of different ways to accomplish the same thing, hope this
helps.

~-----Original Message-----
~From: Gregg Malcolm [mailto:greggm@sbcglobal.net]
~Sent: Thursday, March 07, 2002 2:28 PM
~To: ccielab@groupstudy.com
~Subject: Route Map Logic
~
~
~I'm pretty sure this has probably been discussed before, but
~I've never seen
~an explanation. I'm stumped by the following :
~
~The first example uses 2 seq # 's to control routing updates
~outside a confed
~
~#1
~route-map local_only permit 10
~ match ip address 1
~!
~route-map local_only permit 20
~ set community no-export
~
~The second example has all the criteria in one seq # (except
~for the permit 20
~with nothing which I also don't understand) to add AS-PATH's to updates
~
~#2
~route-map prepend permit 10
~ match ip address 1
~ set as-path prepend 300 400 500
~!
~route-map prepend permit 20
~
~I've tried both of these with all statements in 1 sequence
~number and with 2
~sequence numbers with 1 statement each. Both will only work
~as done in these
~two examples. Does anyone have a explanation ? Why can't
~both be done with a
~single sequence number ? If there any easy way to remember
~when to use 1 seq
~and when to use 2 seq's ?
~
~TIA, Gregg



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:56 GMT-3