[an error occurred while processing this directive][an error occurred while processing this directive]

transmit-rate (Dynamic Schedulers)


transmit-rate (rate | percent percentage | remainder | percent percentage $junos-cos-scheduler-tx) <exact | rate-limit>;

Hierarchy Level

[edit dynamic-profiles profile-name class-of-service schedulers scheduler-name]

Release Information

Statement introduced in JUNOS Release 9.3.

The $junos-cos-scheduler-tx predefined variable added in JUNOS Release 9.4.


Specify the transmit rate or percentage for a scheduler in a dynamic profile.


If you do not include this statement, the default scheduler transmission rate and buffer size percentages for queues 0 through 7 are 95, 0, 0, 5, 0, 0, 0, and 0 percent.


rate—Transmission rate, in bps. You can specify a value in bits per second 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: 3200 through 160,000,000,000 bps

percent percentage—Percentage of transmission capacity. A percentage of zero drops all packets in the queue.

Range: 0 through 100 percent

remainder—Use remaining rate available.

$junos-cos-scheduler-tx—JUNOS predefined variable that is replaced with the transmission rate obtained from the RADIUS server when a subscriber authenticates over the interface to which the dynamic profile is attached.

exact—(Optional) Enforce the exact transmission rate. Under sustained congestion, a rate-controlled queue that goes into negative credit fills up and eventually drops packets. Make sure this value never exceeds the rate-controlled amount.

rate-limit—(Optional) Limit the transmission rate to the rate-controlled amount during congestion. In contrast to the exact option, when there is no congestion, the scheduler with the rate-limit option shares unused bandwidth above the rate-controlled amount.

Required Privilege Level

interface—To view this statement in the configuration.

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

Published: 2010-04-15

[an error occurred while processing this directive]