Table of Contents
Advertisement
JUNOSe 11.1.x IP Services Configuration Guide
Match Policy Lists
Match policy lists are very similar to route maps. However, unlike route maps, match
policy lists can contain only match clauses and no set clauses.
You create match policy lists and then reference those lists within route maps. Because
match policy lists share the same match clauses with route maps, they function the
same way, and you can use the same match commands when you create your match
policy lists.
NOTE: For descriptions of all route map match clauses, see "Route Maps" on page 4
.
As in route maps, the match clauses in match policy lists contain permit and deny
statements. When you reference a match policy list within a route map, the route
map evaluates and processes each match clause and permits or denies routes based
on the match policy list configuration.
When you configure match policy lists, keep the following in mind:
ip match-policy-list
20
Match Policy Lists
Use to specify the BGP weight for the routing table.
The weights assigned with the set weight command in a route map override the
weights assigned using the neighbor weight and neighbor filter-list weight
commands.
Example
host1(config-route-map)#set weight 200
Use the no version to delete the set clause from a route map.
See set weight.
A route map evaluates and processes all match statements within any match
policy list that it references.
You can configure multiple match policy lists within a route map, and you can
evaluate each match policy list by using a logical AND or a logical OR.
You can reference match policy lists within a route map that also uses separate
match and set statements (that is, the statements are not part of the match policy
list).
All match policy lists within a route map match on the incoming attribute only.
Use to create an IP match policy list and launch the match policy list configuration
mode.
Example
host1(config)#ip match-policy-list
Advertisement
Table of Contents
