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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 9: Firewall Filter <strong>Configuration</strong><br />

To configure firewall filter match conditions for Layer 2 CCC traffic:<br />

• Include the match-conditions statement at the [edit firewall family ccc filter filter-name<br />

term term-name from hierarchy level.<br />

Table 28: Layer 2 Circuit Cross-Connect Firewall Filter Match Conditions<br />

Match Condition<br />

destination-mac-address<br />

address<br />

Description<br />

(MX Series routers only) Destination media access control (MAC) address of a virtual private LAN<br />

service (VPLS) packet.<br />

To have packets correctly evaluated by this match condition when applied to egress traffic flowing over<br />

a CCC circuit from a logical interface on an I-chip DPC in a Layer 2 virtual private network (VPN) routing<br />

instance, you must make a configuration change to the Layer 2 VPN routing instance. You must explicitly<br />

disable the use of a control word for traffic flowing out over a Layer 2 circuit. The use of a control word<br />

is enabled by default for Layer 2 VPN routing instances to support the emulated virtual circuit (VC)<br />

encapsulation for Layer 2 circuits.<br />

To explicitly disable the use of a control word for Layer 2 VPNs, include the no-control-word statement<br />

at either of the following hierarchy levels:<br />

• [edit routing-instances routing-instance-name protocols l2vpn]<br />

• [edit logical-systems logical-system-name routing-instances routing-instance-name protocols l2vpn]<br />

forwarding-class<br />

class<br />

Forwarding class. Specify assured-forwarding, best-effort, expedited-forwarding, or network-control.<br />

forwarding-class-except<br />

class<br />

Do not match on the forwarding class. Specify assured-forwarding, best-effort, expedited-forwarding,<br />

or network-control.<br />

interface-group<br />

group-number<br />

Interface group on which the packet was received. An interface group is a set of one or more logical<br />

interfaces. For group-number, specify a value from 0 through 255. For information about configuration<br />

interface groups, see “Applying Firewall Filters to Interfaces” on page 235.<br />

interface-group-except<br />

number<br />

Do not match on the interface group in which the packet was received. For group-number, specify a value<br />

from 0 through 255.<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 />

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

207

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

Saved successfully!

Ooh no, something went wrong!