Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

mode (Traffic Manager)

date_range 16-Dec-24

Syntax

content_copy zoom_out_map
mode traffic-manager-mode;

Hierarchy Level

content_copy zoom_out_map
[edit chassis fpc slot-number pic pic-number traffic-manager],
[edit chassis lcc number fpc slot-number pic pic-number traffic-manager]
[edit chassis fpc slot-number pic pic-number port port-number traffic-manager], (MX80 and MX104 routers only)

Description

Enable shaping on an L2TP session.

Options

traffic-manager-mode—Configure CoS traffic manager mode of operation on this interface. This option has the following suboptions:

egress-only

Enable CoS queuing and scheduling on the egress side for the PIC that houses the interface. This is the default mode.

If ingress packet drops are observed at a high rate for a PIC, configure the traffic-manager statement to work in the egress-only mode.

ingress-and-egress

Enable CoS queuing and scheduling on both the egress and ingress sides for the PIC.

Junos does not support ingress-and-egress mode on label-switched interfaces (LSIs) configured with VPLS.

For EQ DPCs, you must configure the traffic-manager statement with ingress-and-egress mode to enable ingress CoS on the EQ DPC. EQ DPCs have 250 ms of buffering, with only egress queuing (default mode). When ingress-and-egress is configured, the buffer is partitioned as 50 ms for the ingress direction and 200 ms for the egress direction.

Required Privilege Level

interface—To view this statement in the configuration.

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

Release Information

Statement introduced in Junos OS Release 8.3.

footer-navigation