Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

committed-burst-size

Syntax

Hierarchy Level

Description

For a three-color policer, configure the committed burst size (CBS) as a number of bytes.

Note:

When you include the committed-burst-size statement in the configuration, you must also include the committed-information-rate statement at the same hierarchy level.

In three-color policing, a committed information rate (CIR) defines the guaranteed bandwidth for traffic arriving at or departing from the interface under normal line conditions. A flow of traffic at an average rate that conforms to the CIR is categorized green.

During periods of average traffic rates below the CIR, any unused bandwidth capacity accumulates up to a maximum amount defined by the CBS. Short periods of bursting traffic (back-to-back traffic at averages rates that exceed the CIR) are also categorized as green provided that unused bandwidth capacity is available.

Traffic that exceeds both the CIR and the CBS is considered nonconforming.

Single-rate three-color policers use a dual token bucket algorithm to measure traffic against a single rate limit. Nonconforming traffic is categorized as yellow or red, based on the excess-burst-size statement included in the policer configuration.

Two-rate three-color policers use a dual-rate dual token bucket algorithm to measure traffic against two rate limits. Nonconforming traffic is categorized as yellow or red based on the peak-information-rate and peak-burst-rate statements included in the policer configuration.

Options

bytes—Number of bytes. You can specify a value in bytes either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000).

  • Range: 1500 through 100,000,000,000 bytes

  • Range: 125 through 266338370 bytes (ACX on Junos EVO)

Required Privilege Level

firewall—To view this statement in the configuration.

firewall-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 7.4.

Support at the [edit dynamic-profiles ... single-rate] and [edit dynamic-profiles ... two-rate] hierarchy levels introduced in Junos OS Release 11.4.