Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

traffic-manager

Syntax (MX Series, PTX Series) Configure Queue Monitoring

Syntax (QFX Series)

Syntax (vSRX Virtual Firewall)

Hierarchy Level

Description

Enable CoS queuing, scheduling, and shaping.

Note:

Committing changes to traffic-manager automatically restarts any necessary components (PICs, DPCs, or FPCs).

Options

buffer-monitor-enable

Enable port buffer monitoring. Buffer utilization data is collected in one-second intervals and compared with the data from the previous interval. The larger value is kept to keep track of peak buffer occupancy for each queue or priority group.

queue-threshold

Enable monitoring of Fabric and WAN queues. When the fabric-queue statement is configured, an SNMP trap is generated whenever the fabric power utilization exceeds the configured threshold value.

When wan-queue is configured, an SNMP trap is generated whenever the WAN queue depth exceeds the configured threshold value.

egress-shaping-overhead number

When traffic management (queueing and scheduling) is configured on the egress side, the number of CoS shaping overhead bytes to add to the packets on the egress interface.

Replace number with a value from -63 through 192 bytes.

For vSRX Virtual Firewall, replace number with a value from -62 through 192 bytes.

Note:

The L2 headers (DA/SA + VLAN tags) are automatically a part of the shaping calculation.

ingress-shaping-overhead number

When L2TP session shaping is configured, the number of CoS shaping overhead bytes to add to the packets on the ingress side of the L2TP tunnel to determine the shaped session packet length.

When session shaping is not configured and traffic management (queueing and scheduling) is configured on the ingress side, the number of CoS shaping overhead bytes to add to the packets on the ingress interface.

Replace number with a value from —63 through 192 bytes.

mode

Configure CoS traffic manager mode of operation. 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.

    Note:

    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 queueing and scheduling on both the egress and ingress sides for the PIC.

    Note:
    • 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 queueing (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.

enhanced-priority-mode

Enable the enhanced priority mode. When you enable the enhanced priority mode, the scheduler supports four additional per-priority shaping rates and two additional excess priorities at the interface and interface set level. The four additional per-priority shaping rates are: Guaranteed Strict-high, Guaranteed Medium-low, Excess medium-high, and Excess medium-low. The two additional excess priorities are: Excess-rate Medium- high and Excess-rate Medium-low. This is the default mode for PTX Series routers.

no-enhanced-priority-mode

Disable the enhanced priority mode. This is the default mode for MX Series routers.

Note:

The line card reboots when you enable or disable the enhanced priority mode feature.

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.