Table of Contents
Advertisement
JUNOS 10.1 Network Interfaces Configuration Guide
NOTE: HDLC payload scrambling conflicts with traffic shaping configured using leaky
bucket properties. If you configure leaky bucket properties, you must disable payload
scrambling, because the JUNOS Software rejects configurations that have both features
enabled. For more information, see "Configuring SONET/SDH HDLC Payload
Scrambling" on page 906.
To configure leaky bucket properties, include one or both of the
transmit-bucket
In the
to receive or transmit packets. The percentage can be a value from 0 (none of the
interface line rate is available) to 100 (the maximum interface line rate is available).
For example, when you set the line rate to 33, the interface receives or transmits at
one third of the maximum line rate.
In the
of the leaky bucket mechanism. The larger the value, the more bursty the traffic,
which means that over a very short amount of time the interface can receive or
transmit close to line rate, but the average over a longer time is at the configured
bucket rate. The threshold can be a value from 0 through 65,535 bytes. For ease of
entry, you can enter
number followed by the abbreviation
corresponds to a threshold of 2,000 bytes.
In the
Damping Interface Transitions on SONET/SDH Interfaces
By default, when an interface changes from being up to being down, or from down
to up, this transition is advertised immediately to the hardware and the JUNOS
Software. In some situations—for example, when an interface is connected to an
add-drop multiplexer (ADM) or wavelength-division multiplexer (WDM), or to protect
against SONET/SDH framer holes—you might want to damp interface transitions.
932
Damping Interface Transitions on SONET/SDH Interfaces
statements at the
[edit interfaces interface-name]
receive-bucket {
overflow (discard | tag);
rate percentage;
threshold bytes;
}
transmit-bucket {
overflow discard;
rate percentage;
threshold bytes;
}
statement, specify the percentage of the interface line rate that is available
rate
statement, specify the bucket threshold, which controls the burstiness
threshold
number
overflow
option, specify how to handle packets that exceed the threshold:
tag
—(
receive-bucket
only) Tag, count, and process received packets that exceed
the threshold.
—Discard received packets that exceed the threshold. No counting is
discard
done.
[edit interfaces interface-name]
either as a complete decimal number or as a decimal
k
(1,000). For example, the entry
and
receive-bucket
hierarchy level:
threshold 2k
Advertisement
Table of Contents
