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

three-color-policer<br />

three-color-policer (Applying)<br />

See the following sections:<br />

• three-color-policer (Applying) on page 338<br />

• three-color-policer (Configuring) on page 339<br />

Syntax three-color-policer {<br />

(single-rate | two-rate) policer-name;<br />

}<br />

Hierarchy Level<br />

[edit firewall family family-name filter filter-name term term-name then],<br />

[edit logical-systems logical-system-name firewall family family-name filter filter-name<br />

term term-name then]<br />

Release Information Statement introduced before Junos OS Release 7.4.<br />

single-rate statement added in Junos OS Release 8.2.<br />

Logical systems support introduced in Junos OS Release 9.3.<br />

Description<br />

For T Series routers and M320 routers with Enhanced II Flexible PIC Concentrators (FPCs)<br />

and the T640 Core Router with Enhanced Scaling FPC4, apply a tricolor marking policer.<br />

Options<br />

single-rate—Named tricolor policer is a single-rate policer.<br />

two-rate—Named tricolor policer is a two-rate policer.<br />

policer-name—Name of a tricolor policer.<br />

Required Privilege<br />

Level<br />

Related<br />

Documentation<br />

firewall—To view this statement in the configuration.<br />

firewall-control—To add this statement to the configuration.<br />

• Configuring Actions in Firewall Filter Terms on page 226<br />

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