Traffic Control Profiles; Schedulers - Juniper ACX1000 Configuration Manual

Traffic Control Profiles

Schedulers

Copyright © 2017, Juniper Networks, Inc.
NOTE: If you change the physical interface queuing mode from default to
hierarchical scheduler mode or vice-versa, the traffic flowing out of the
physical interface during the mode change results in a transient loss of traffic
data.
The traffic control profiles hold parameters for levels above the queue level of the
scheduler hierarchy. The scheduling and shaping configuration on the scheduler nodes
are configured using traffic-control-profiles CLI command and scheduler is for queue
level. The traffic control profile defines the following characteristics of a scheduler node:
Scheduler-map
Shaping rate
Guaranteed rate
Traffic control profiles can be attached at physical interface and logical interface level.
Scheduling and queuing characteristics can be defined for the scheduler node using the
shaping-rate and guaranteed-rate. The following is a sample traffic control profile
configuration:
[edit class-of-service traffic-control-profiles]
tcp-500m-shaping-rate {
shaping-rate 500m;
}
tcp-ifl0 {
shaping-rate 200m;
guaranteed-rate 100m;
scheduler-map tcp-map-ifl0; # Applies scheduler maps to customer VLANs.
}
A scheduler defines scheduling and queuing characteristics of a queue and holds the
information about the queues, the last level of the hierarchy. The following is a sample
scheduler configuration:
[edit class-of-service schedulers]
sched-ifl0-q0 {
priority low;
transmit-rate 20m;
buffer-size temporal 100ms;
drop-profile loss-priority low dp-low;
drop-profile loss-priority high dp-high;
}
sched-ifl-q1 {
priority strict-high;
shaping-rate 20m;
}
Chapter 27: Configuring Class of Service
937