Policy Framework Configuration Guide - Juniper Networks

Junos 10.4 Policy Framework Configuration Guide
Table 10: Routing Policy Match Conditions (continued)
Match Condition
Match
Condition
Category
from Statement Description
to Statement Description
prefix-list
prefix-list-name
ip-addresses
Extended
Named list of IP addresses. You can
specify an exact match with incoming
routes.
You cannot specify this match condition.
For information about this extended match
condition, see “Configuring Prefix Lists for
Use in Routing Policy Match Conditions”
on page 116.
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.
You cannot specify this match condition.
For information about this extended match
condition, see “Configuring Prefix Lists for
Use in Routing Policy Match Conditions”
on page 116.
protocol protocol
Standard
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: access, access-internal, aggregate, bgp, direct,
dvmrp, isis, local, ospf, ospf2, ospf3, pim-dense, pim-sparse, rip, ripng, or static.
NOTE: The ospf2 statement matches on OSPFv2 routes. The ospf3 statement matches
on OSPFv3 routes. The ospf statement matches on both OSPFv2 and OSPFv3 routes.
For more information about access routes and access-internal routes, see “Example:
Importing and Exporting Access and Access-Internal Routes in a Routing Policy” on
page 74.
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-filter
destination-prefix
match-type
Extended
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. For
more information, see “Configuring Route
Lists for Use in Routing Policy Match
Conditions” on page 119.
You cannot specify this match condition.
46
Copyright © 2010, Juniper Networks, Inc.