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 />

Overview of Class-Based Match Conditions<br />

Class-based filter conditions match packet fields based on source class or destination<br />

class. A source class is a set of source prefixes grouped together and given a class name.<br />

A destination class is a set of destination prefixes grouped together and given a class<br />

name.<br />

Use the source-class class-name statement to match on one or more source classes.<br />

Use the destination-class class-name statement to match on one or more destination<br />

classes.<br />

NOTE: Both match conditions are supported for IPv4 and IPv6 traffic.<br />

You can specify the destination class in the following ways:<br />

• Destination-class usage (DCU) enables you can track how much traffic is sent to a<br />

specific prefix in the core of the network originating from one of the specified interfaces<br />

However, DCU limits your ability to keep track of traffic moving in the reverse direction.<br />

It can account for all traffic that arrives on a core interface and heads toward a specific<br />

customer, but it cannot count traffic that arrives on a core interface from a specific<br />

prefix.<br />

• Source-class usage (SCU) enables you to monitor the amount of traffic originating<br />

from a specific prefix. With this feature, usage can be tracked and customers can be<br />

billed for the traffic they receive<br />

You can specify a source class or destination class for an output firewall filter. Although<br />

you can specify a source class and destination class for an input firewall filter, the counters<br />

are incremented only if the firewall filter is applied on the output interface.<br />

The class-based filter match condition works only for output filters, because the SCU<br />

and DCU are determined after route lookup.<br />

NOTE: SCU and DCU are not supported on the interfaces you configure as<br />

the output interface for tunnel traffic for transit packets exiting the router<br />

through the tunnel.<br />

For more information about SCU and DCU, see the Source Class Usage Feature <strong>Guide</strong>.<br />

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

219

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

Saved successfully!

Ooh no, something went wrong!