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.

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

Table 32: VPLS Firewall Filter Match Conditions (continued)<br />

Match Condition<br />

vlan-ether-type-except<br />

value<br />

Description<br />

Do not match on the VLAN Ethernet type field of a VPLS packet.<br />

Related<br />

Documentation<br />

• How to Specify Firewall Filter Match Conditions on page 220<br />

Configuring Layer 2 Bridging Match Conditions for MX Series Ethernet Services Routers<br />

Table 33 on page 214 describes the firewall filter match conditions supported for Layer 2<br />

bridging traffic on MX Series routers.<br />

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

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

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

Table 33: Layer 2 Bridging Firewall Filter Match Conditions (MX Series Ethernet Services Routers<br />

Only)<br />

Match Condition<br />

destination-mac-address<br />

address<br />

Description<br />

Destination media access control (MAC) address of a Layer 2 packet in a bridging environment.<br />

destination-port number<br />

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

conditions in the same term.<br />

dscp number<br />

Differentiated Services code point (DSCP). The DiffServ protocol uses the type-of-service (ToS) byte<br />

in the IP header. The most significant 6 bits of this byte form the DSCP. For more information, see the<br />

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

You can specify a numeric value from 0 through 63. To specify the value in hexadecimal form, include<br />

0x as a prefix. To specify the value in binary form, include b as a prefix.<br />

In place of the numeric value, you can specify one of the following text synonyms (the field values<br />

are also listed):<br />

• RFC 3246, An Expedited Forwarding PHB (Per-Hop Behavior), defines one code point: ef (46).<br />

• RFC 2597, Assured Forwarding PHB Group, defines 4 classes, with 3 drop precedences in each class,<br />

for a total of 12 code points:<br />

af11 (10), af12 (12), af13 (14),<br />

af21 (18), af22 (20), af23 (22),<br />

af31 (26), af32 (28), af33 (30),<br />

af41 (34), af42 (36), af43 (38)<br />

ether-type value<br />

Ethernet type field of a Layer 2 packet in a bridging environment.<br />

ether-type-except value<br />

Do not match on the Ethernet type field of a Layer 2 packet.<br />

214<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!