Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual page 106

JunosE 11.3.x Policy Management Configuration Guide
82
bucket for every byte of data processed. As long as tokens are still in the committed burst
bucket, the traffic is treated as committed.
When the committed burst token bucket is empty but tokens remain in the peak burst
bucket, traffic is treated as conformed. When the peak burst token bucket is empty, traffic
is treated as exceeded.
In color-blind mode, if the committed token bucket has enough tokens when a packet is
received, the packet is green and tokens are subtracted from both the committed and
the peak token buckets. If the peak bucket does not have enough tokens left, it is allowed
to go negative. Green packets are the committed traffic.
If the committed bucket does not have enough tokens for the packet, the peak bucket
is tested (and the committed bucket is not changed). If there are enough tokens in the
peak bucket, it is decremented and the packet is yellow. Yellow packets are the conformed
traffic. If the peak bucket does not have enough tokens either (because the committed
bucket did not have enough tokens), the packet is red. Red packets are the exceeded
traffic.
The two-rate rate-limit profile attributes are:
ATM cell mode—ATM cell tax accounted for in statistics and rate calculations
Color-aware—Color-aware rate action (only for hierarchical rate limits)
Committed rate—Target rate for a packet flow
Committed burst—Amount of bandwidth allocated to accommodate bursty traffic in
excess of the committed rate
Peak rate—Amount of bandwidth allocated to accommodate excess traffic flow over
the committed rate
Peak burst—Amount of bandwidth allocated to accommodate bursty traffic in excess
of the peak rate
Committed action—Drop, transmit, conditional, unconditional, final, mark (IP and IPv6),
or mark-exp (MPLS) when traffic flow does not exceed the committed rate; the mark
value is not supported for hierarchical rate limits and the transmit values conditional,
unconditional, or final are only supported on hierarchical rate limits
Conformed action—Drop, transmit, mark (IP and IPv6), or mark-exp (MPLS) when
traffic flow exceeds the committed rate but remains below the peak rate; the mark
value is not supported for hierarchical rate limits and the transmit values conditional,
unconditional, or final are only supported on hierarchical rate limits
Exceeded action—Drop, transmit, mark (IP and IPv6), or mark-exp (MPLS) when traffic
flow exceeds the peak rate; the mark value is not supported for hierarchical rate limits
and the transmit values conditional, unconditional, or final are only supported on
hierarchical rate limits
Copyright © 2010, Juniper Networks, Inc.