16.03.2014 Views

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Junos 10.4 <strong>Policy</strong> <strong>Framework</strong> <strong>Configuration</strong> <strong>Guide</strong><br />

Table 25: IPv4 Firewall Filter Match Conditions (continued)<br />

Match Condition<br />

Description<br />

interface-set<br />

interface-set-name<br />

(MX Series routers and routers with Enhanced IQ2 [IQ2E] PICs only) Interface set on which the packet<br />

was received. An interface set is a set of logical interfaces used to configure hierarchical class-of-service<br />

schedulers. For information about configuring an interface set, see the Junos Class of Service<br />

<strong>Configuration</strong> <strong>Guide</strong> and the Junos Network Interfaces <strong>Configuration</strong> <strong>Guide</strong>.<br />

ip-options values<br />

IP optional header fields. In place of the numeric value, you must specify one of the following text<br />

synonyms: any, loose-source-route, route-record, router-alert, security, stream-id, strict-source-route, or<br />

timestamp.<br />

Do not use a numerical value for any of the IP optional header fields. Use only the text values.<br />

NOTE: For most interfaces, packets that match any of values for the ip-options match condition—except<br />

for the any option—are sent to the Routing Engine for processing. Use the ip-options option any to<br />

ensure that packets are sent to the Packet Forwarding Engine for processing.<br />

Interfaces configured on the 10-Gigabit Ethernet Modular Port Concentrator (MPC), 60-Gigabit Ethernet<br />

MPC, 60-Gigabit Queuing Ethernet MPC, and 60-Gigabit Ethernet Enhanced Queuing MPC on MX<br />

Series routers do send all packets that match any of the supported ip-options match conditions to the<br />

Packet Forwarding Engine.<br />

is-fragment<br />

This condition matches if the packet is a trailing fragment; it does not match the first fragment of a<br />

fragmented packet. To match both first and trailing fragments, you can use two terms.<br />

loss-priority level<br />

Packet loss priority (PLP) level. Specify a single level or multiple levels: low, medium-low, medium-high,<br />

or high.<br />

Supported on MX Series routers; M120 and M320 routers; and M7i and M10i routers with the Enhanced<br />

CFEB (CFEB-E).<br />

On M320 routers, you must enable the tricolor statement at the [edit class-of-service] hierarchy level<br />

to commit a PLP configuration with any of the four levels specified. If the tricolor statement is not<br />

referenced, you can only configure the high and low levels. This applies to all protocol families.<br />

For information about using behavior aggregate (BA) classifiers to set the PLP level of incoming packets,<br />

see the Junos Class of Service <strong>Configuration</strong> <strong>Guide</strong>.<br />

loss-priority-except<br />

level<br />

Do not match on the packet loss priority level. Specify a single level or multiple levels: low, medium-low,<br />

medium-high, or high.<br />

For information about using behavior aggregate (BA) classifiers to set the PLP level of incoming packets,<br />

see the Junos Class of Service <strong>Configuration</strong> <strong>Guide</strong>.<br />

packet-length bytes<br />

Length of the received packet, in bytes. The length refers only to the IP packet, including the packet<br />

header, and does not include any Layer 2 encapsulation overhead.<br />

port number<br />

TCP or UDP source or destination port field. You cannot specify both the port match and either the<br />

destination-port or source-port match conditions in the same term.<br />

Normally, you specify this match in conjunction with the protocol match statement to determine which<br />

protocol is being used on the port. For more information, see “Overview of Protocol Match Conditions”<br />

on page 217.<br />

In place of the numeric value, you can specify one of the text synonyms listed under destination-port.<br />

200<br />

Copyright © 2010, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!