Bandwidth Management Overview - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual

JunosE 11.3.x Policy Management Configuration Guide
Related
Documentation

Bandwidth Management Overview

92
Committed burst size—Set to 8192 if it was less than that value before the upgrade
Peak burst size—Set to 8192 if it was less than that value before the upgrade
Peak rate—Set to 0 if it was nonzero but less than the committed rate before the
upgrade
NOTE: We recommend that you do not configure a committed or peak
burst size smaller than the MTU of the interface. Doing so causes large
packets to be dropped even when they are transmitted at a very low rate.
Issue the ip rate-limit-profile command in Global Configuration mode:
host1(config)#ip rate-limit-profile hardlimit9Mb two-rate
NOTE: Commands that you issue in Rate Limit Profile Configuration mode
do not take effect until you exit from that mode.
exp-mask
rate-limit-profile
When you configure the rate-limit profile, packets are tagged with a drop preference.
The color-coded tag is added automatically when the committed and peak burst values
for an interface's rate-limit profile are exceeded. The egress forwarding controller uses
the drop preference to determine which packets are dropped when there is contention
for outbound queuing resources within the E Series router.
The queuing system uses drop eligibility to select packets for dropping when congestion
exists on an egress interface. This method is called dynamic color-based threshold
dropping. The 2-bit tag assigns a color code to the packet: red, yellow, or green. Each
packet queue has two color-based thresholds as well as a queue limit:
Red packets are dropped when congestion causes the queue to fill above the red
threshold.
Yellow packets are dropped when the yellow threshold is reached.
Green packets are dropped when the queue limit is reached.
This internal tagging is done automatically when a rate-limit profile is applied to an
interface and does not necessarily reflect the operation of the policy on an interface.
Having a committed rate and a peak rate enables you to configure two different fill rates
for the token buckets. For example, you can configure the fill rate on the peak token
bucket to be faster than the fill rate on the committed bucket. This configuration enables
Copyright © 2010, Juniper Networks, Inc.