[Contents] [Prev] [Next] [Index] [Report an Error]

Routing Policy Match Conditions

A match condition defines the criteria that a route must match for an action to take place. Each term can have one or more match conditions. If a route matches all the match conditions for a particular term, the actions defined for that term are processed.

Each term can consist of two statements, to and from, that define match conditions:

In the from statement, you define the criteria that an incoming route must match. You can specify one or more match conditions. If you specify more than one, all conditions must match the route for a match to occur.
In the to statement, you define the criteria that an outgoing route must match. You can specify one or more match conditions. If you specify more than one, all conditions must match the route for a match to occur.

The order of match conditions in a term is not important, because a route must match all match conditions in a term for an action to be taken.

Table 88 summarizes the routing policy match conditions.

Table 88: Summary of Routing Policy Match Conditions

Match Condition	Description
aggregate-contributor	Matches routes that are contributing to a configured aggregate. This match condition can be used to suppress a contributor in an aggregate route.
area area-id	Matches a route learned from the specified OSPF area during the exporting of OSPF routes into other protocols.
as-path name	Name of an AS path regular expression. BGP routes whose AS path matches the regular expression are processed.
color preference	Color value. You can specify preference values that are finer-grained than those specified in the preference match conditions. The color value can be a number from 0 through 4,294,967,295 (2³² – 1). A lower number indicates a more preferred route.
community	Name of one or more communities. If you list more than one name, only one name needs to match for a match to occur. (The matching is effectively a logical OR operation.)
external [type metric-type]	Matches external OSPF routes, including routes exported from one level to another. In this construct type is an optional keyword. The metric-type value can be either 1 or 2. When you do not specify type, this condition matches all external routes.
interface interface-name	Name or IP address of one or more router interfaces. Do not use this qualifier with protocols that are not interface-specific, such as internal BGP (IBGP). Depending on where the policy is applied, this match condition matches routes learned from or advertised through the specified interface.
internal	Matches a routing policy against the internal flag for simplified next-hop self policies.
level level	Matches the IS-IS level. Routes that are from the specified level or are being advertised to the specified level are processed.
local-preference value	BGP local preference attribute. The preference value can be from 0 through 4,294,967,295 (2³² – 1).
metric metric metric2 metric	Metric value. The metric value corresponds to the multiple exit discriminator (MED), and metric2 corresponds to the interior gateway protocol (IGP) metric if the BGP next hop runs back through another route.
neighbor address	Address of one or more neighbors (peers). For BGP export policies, the address can be a directly connected or indirectly connected peer. For all other protocols, the address is the neighbor from which the advertisement is received.
next-hop address	Next-hop address or addresses specified in the routing information for a particular route. For BGP routes, matches are performed against each protocol next hop.
origin value	BGP origin attribute, which is the origin of the AS path information. The value can be one of the following: egp—Path information originated from another AS. igp—Path information originated from within the local AS. incomplete—Path information was learned by some other means.
policy [ policy-names ]	Name of one or more policies to evaluate as a subroutine.
preference preference preference2 preference	Preference value. You can specify a primary preference value (preference) and a secondary preference value (preference2). The preference value can be a number from 0 through 4,294,967,295 (2³² – 1). A lower number indicates a more preferred route.
prefix-list name	Named list of IP addresses configured at the Policy-options level in the configuration hierarchy. This match condition can be used on import policies only.
protocol protocol	Name of the protocol from which the route was learned or to which the route is being advertised. It can be one of the following: aggregate, bgp, direct, dvmrp, isis, local, ospf, pim-dense, pim-sparse, rip, ripng, or static.
route-filter destination-prefix match-type <actions>	List of destination prefixes. When specifying a destination prefix, you can specify an exact match with a specific route or a less precise match using match types. You can configure either a common action that applies to the entire list or an action associated with each prefix. Route filters can be used on import policies only.
route-type value	Type of route. The value can be either external or internal.
source-address-filter destination-prefix match-type <actions>	List of multicast source addresses. When specifying a source address, you can specify an exact match with a specific route or a less precise match using match types. You can configure either a common action that applies to the entire list or an action associated with each prefix. Source-address filters can be used on import policies only.

[Contents] [Prev] [Next] [Index] [Report an Error]