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

}<br />

}<br />

}<br />

If traffic arriving on the logical interface is within the average rate of 40 Mbps (based on<br />

the token bucket formula) or within the committed burst size limit of 100 KB, the packets<br />

are “green” and are marked with an implicit loss priority of low. If traffic arriving on the<br />

logical interface is above the committed information rate and above the committed burst<br />

size but still within the peak information rate of 60 Mbps (based on the second token<br />

bucket), the packets are “yellow” and are marked with an implicit loss priority of<br />

medium-high. If traffic arriving on the logical interface is above the peak information rate<br />

of 60 Mbps, the packets are “red,” are marked with a loss priority of high, and are<br />

discarded. In the “red” case, if you omit the action statement, the packets are still marked<br />

with an implicit loss priority of high, but the packets are transmitted. As the traffic rate<br />

slows and the newly arriving traffic conforms to the configured limits, Junos OS stops<br />

marking packets with the medium-high and high loss priorities and stops dropping red<br />

packets.<br />

For two-rate, three-color policing, Junos OS uses two token buckets to manage bandwidth<br />

based on the two rates of traffic. When the policer is color-aware, it takes into account<br />

any preexisting markings that might be set for a packet by another traffic policer<br />

configured at a previous network node. At the node where color-aware policing is<br />

configured, these preexisting markings are then used in determining the appropriate<br />

policing action for the packet. For example, two-rate policing might be configured on a<br />

node upstream in the network. The two-rate policer has marked a packet as yellow (loss<br />

priority medium-low). The color-aware policer takes this yellow marking into account<br />

when determining the appropriate policing action. In color-aware policing, the yellow<br />

packet would never receive the action associated with either the green packets or red<br />

packets. This way, tokens for violating packets are never taken from the metering token<br />

buckets at the color-aware policing node. If you configure a policer to be color-blind<br />

instead of color-aware, the color-blind node ignores preexisting markings.<br />

Configuring a Two-Rate Three-Color Policer<br />

You can apply a two-rate three-color policer to the input or output interface.<br />

To configure a two-rate three-color policer:<br />

1. Configure the policer.<br />

[edit firewall three-color-policer trTCM1-ca]<br />

user@host# set two-rate color-aware<br />

user@host# set two-rate committed-information-rate 40m<br />

user@host# set two-rate committed-burst-size 100k<br />

user@host# set two-rate peak-information-rate 60m<br />

user@host# set two-rate peak-burst-size 200k<br />

2. (Optional) Configure the policer action.<br />

For three-color policers, the only configurable action is to discard red packets. Red<br />

packets are packets that have been assigned high loss priority because they exceeded<br />

the peak information rate (PIR) and the peak burst size (PBS).<br />

[edit firewall three-color-policer trTCM1-ca]<br />

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