Related
Documentation
Configuring Strict-Priority Scheduling
Copyright © 2010, Juniper Networks, Inc.
This shaping limits relative strict traffic to 500 Kbps, and prevents the relative strict-priority
traffic from starving out the nonstrict traffic.
The third shaper, on the nonstrict queue, is subtle. The rate is 1 Mbps, which allows the
nonstrict traffic to consume up to the full aggregate rate of the VC. But the burst size is
1, which causes the nonstrict queue to always yield to the relative strict-priority queue
after sending a packet. This burst size limits the number of nonstrict packets that can
precede a relative strict-priority packet to the minimum, one packet.
Figure 14: Tuning Latency on Strict-Priority Queues
Strict-Priority and Relative Strict-Priority Scheduling Overview on page 57
Configuring Strict-Priority Scheduling on page 63
Relative Strict-Priority Scheduling Overview on page 58
To configure strict-priority scheduling:
Configure the traffic classes.
1.
host1(config)#traffic-class Low-loss-1
host1(config-traffic-class)#exit
host1(config)#traffic-class Low-latency-1
host1(config-traffic-class)#exit
host1(config)#traffic-class Low-latency-2
host1(config-traffic-class)#exit
Configure the auto-strict-priority traffic-class group, and add the traffic classes that
2.
must receive strict-priority scheduling to the group.
host1(config)#traffic-class-group Strict-priority auto-strict-priority
host1(config-traffic-class-group)#traffic-class Low-latency-1
host1(config-traffic-class-group)#traffic-class Low-latency-2
host1(config-traffic-class-group)#exit
Create a scheduler profile for strict-priority traffic and configure the shaping rate.
3.
host1(config)#scheduler-profile strictPriorityBandwidth
host1(config-scheduler-profile)#shaping-rate 20000000
host1(config-scheduler-profile)#exit
Chapter 8: Configuring Strict-Priority Scheduling
63