Match and Set Conditions
Each route map statement can have from none to multiple match and set
conditions. If no match condition exists, the statement matches anything,
similar to a �gpermit any�h in an access list. If there is no set condition, the
matching traffic is either permitted or denied, with no other conditions being set.
Multiple match conditions on the same line use a logical OR. For example,
the router interprets match a b c as �gmatch a or b or c.�h Multiple match
conditions on different lines use a logical AND. For example, the router
interprets the following route map statement as �gmatch a and b and c:�h
route-map Logical-AND permit 10
match a
match b
match c
In route redistribution, some common conditions to match include:
�¡ ip address.Refers the router to an access list that permits or denies
networks.
�¡ ip next-hop.Refers the router to an access list that permits or denies
next-hop IP addresses.
�¡ ip route-source.Refers the router to an access list that permits or
denies advertising router IP addresses.
�¡ metric.Permits or denies routes with the specified metric from being
redistributed.
�¡ route-type.Permits or denies redistribution of the route type listed,
such as internal or external.
�¡ tag.Routes can be labeled (tagged) with a number, and route maps
can look for that number.
In route redistribution, some common conditions to set are:
�¡ metric.Sets the metric for redistributed routes.
�¡ metric-type.Sets the type, such as E1 for OSPF.
�¡ tag.Tags a route with a number that can be matched on later by other
route maps.
�¡ level.For IS-IS, sets the IS level for this route.