area area-id

Matches a route learned from the specified OSPF area during the exporting of OSPF routes into other protocols.

color preference

Matches a 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.

external [type metric-type]

Matches external OSPF routes, including routes exported from one level to another. In this match condition, 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.

internal

Matches a routing policy against the internal flag for simplified next-hop self policies.

local-preference value

Matches a BGP local preference attribute. The preference value can be from 0 through 4,294,967,295 (2³² – 1).

neighbor address

Matches the address of one or more neighbors (peers).

For BGP export policies, the address can be for a directly connected or indirectly connected peer. For all other protocols, the address is for the neighbor from which the advertisement is received.

origin value

Matches the 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.

protocol protocol

Matches the 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.

area area-id

Standard

(Open Shortest Path First [OSPF] only) Area identifier.

In a from statement used with an export policy, match a route learned from the specified OSPF area when exporting OSPF routes into other protocols.

as-path-group group-name

Extended

(BGP only) Name of an AS path group regular expression. For more information, see Understanding AS Path Regular Expressions for Use as Routing Policy Match Conditions.

community-count value (equal | orhigher | orlower)

Standard

(BGP only) Number of community entries required for a route to match. The count value can be a number in the range of 0 through 1,024. Specify one of the following options:

• equal—The number of communities must equal this value to be considered a match.
• orhigher —The number of communities must be greater than or equal to this value to be considered a match.
• orlower—The number of communities must be less than or equal to this value to be considered a match.

Note: If you configure multiple community-count statements, the matching is effectively a logical AND operation.

Note: The community-count attribute only works with standard communities. It does not work with extended communities.

You cannot specify this match condition.

external [ type metric-type ]

Standard

(OSPF and IS-IS only) Match IGP external routes. For IS-IS routes, the external condition also matches routes that are exported from one IS-IS level to another. The type keyword is optional and is applicable only to OSPF external routes. When you do not specify type, the external condition matches all IGP external (OSPF and IS-IS) routes. When you specify type, the external condition matches only OSPF external routes with the specified OSPF metric type. The metric type can either be 1 or 2.

To match BGP external routes, use the route-type match condition.

instance instance-name

Standard

Name of one or more routing instances.

Match a route learned from one of the specified instances.

Name of one or more routing instances.

Match a route to be advertised over one of the specified instances.

level level

Standard

(Intermediate System-to-Intermediate System [IS-IS] only) IS-IS level.

Match a route learned from a specified level.

(IS-IS only) IS-IS level.

Match a route to be advertised to a specified level.

metric metric metric2 metric metric3 metric metric4 metric

Standard

Metric value. You can specify up to four metric values, starting with metric (for the first metric value) and continuing with metric2, metric3, and metric4.

(BGP only) metric 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

Standard

Address of one or more neighbors (peers).

For BGP, 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.

Note: The neighbor address match condition is not valid for the Routing Information Protocol (RIP).

Address of one or more neighbors (peers).

For BGP import policies, specifying to neighbor produces the same result as specifying from neighbor.

For BGP export policies, specifying the neighbor match condition has no effect and is ignored.

For all other protocols, the to statement matches the neighbor to which the advertisement is sent.

Note: The neighbor address match condition is not valid for the Routing Information Protocol (RIP).

next-hop-type merged

Standard

LDP generates a next hop based on RSVP and IP next hops available to use, combined with forwarding-class mapping.

You cannot specify this match condition.

origin value

Standard

(BGP only) BGP origin attribute, which is the origin of the AS path information. The value can be one of the following:

• egp—Path information originated in another AS.
• igp—Path information originated within the local AS.
• incomplete—Path information was learned by some other means.

preference preference preference2 preference

Standard

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.

To specify even finer-grained preference values, see the color and color2 match conditions in this table.

prefix-list-filter prefix-list-name match-type

Extended

Named prefix list. You can specify prefix length qualifiers for the list of prefixes in the prefix list.

For information about this extended match condition, see Understanding Prefix Lists for Use in Routing Policy Match Conditions.

You cannot specify this match condition.

rib routing-table

Standard

Name of a routing table. The value of routing-table can be one of the following:

• inet.0—Unicast IPv4 routes
• instance-name inet.0—Unicast IPv4 routes for a particular routing instance
• inet.1—Multicast IPv4 routes
• inet.2—Unicast IPv4 routes for multicast reverse-path forwarding (RPF) lookup
• inet.3—MPLS routes
• mpls.0—MPLS routes for label-switched path (LSP) next hops
• inet6.0—Unicast IPv6 routes

route-type value

Standard

Type of BGP route. The value can be one of the following:

• external—External route.
• internal—Internal route.

To match IGP external routes, use the external match condition.

source-address-filter destination-prefix match-type <actions>

Extended

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. For more information, see Understanding Route Filters for Use in Routing Policy Match Conditions.

You cannot specify this match condition.

tag string tag2 string

Standard

Tag value. You can specify two tag strings: tag (for the first string) and tag2. These values are local to the router and can be set on configured routes or by using an import routing policy.

You can specify multiple tags under one match condition by including the tags within a bracketed list. For example: from tag [ tag1 tag2 tag3 ];

For OSPF routes, thetag action sets the 32-bit tag field in OSPF external link-state advertisement (LSA) packets.

For IS-IS routes, the tag action sets the 32-bit flag in the IS-IS IP prefix type length values. (TLV).

OSPF stores the INTERNAL route's OSPF area ID in thetag2 attribute. However, for EXTERNAL routes, OSPF does not store anything in the tag2attribute.

You can configure a policy term to set the tag2 value for a route. If the route, already has a tag2 value (for example, an OSPF route that stores area id in tag2), then the original tag2 value is overwritten by the new value.

When the policy contains the "from area" match condition, for internal OSPF routes, where tag2 is set, based on the OSPF area- ID, the evaluation is conducted to compare the tag2 attribute with the area ID. For external OSPF routes that do not have the tag2 attribute set, the match condition fails.