Static And Hierarchical Assured Rate Overview; Configuring Rates And Weights In The Scheduler Hierarchy - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 Configuration Manual

Related
Documentation

Static and Hierarchical Assured Rate Overview

Copyright © 2010, Juniper Networks, Inc.
Configure a QoS profile, specify the node command, and reference the
2.
scheduler-profile.
host1(config)#qos-profile 80mbps
host1(config-qos-profile)#ethernet node scheduler-profile 80mbps
host1(config-qos-profile)#exit
Attach the QoS profile to the port.
3.
host1(config)#interface fastethernet 2/0
host1(config-if)#qos-profile 80mbps
The sample configuration shapes Fast Ethernet port 2/0 to a rate no higher than 80 Mbps.
Using the following configuration, you can shape the corresponding HDLC channel down
to 20 Mbps:
host1(config)#scheduler-profile 20mbps
host1(config-scheduler-profile)#shaping-rate 20000000
host1(config-scheduler-profile)#exit
host1(config)#qos-profile 20mbps
host1(config-qos-profile)#serial node scheduler-profile 20mbps
host1(config-qos-profile)#exit
host1(config)#interface serial 2/0:1/1
host1(config-if)#qos-profile 20mbps
Rate Shaping and Port Shaping Overview on page 51
Configuring a Scheduler Profile for a Scheduler Node or Queue on page 48
For more information about specifying an expression that you can reference within a
scheduler profile, see Using Expressions for Bandwidth and Burst Values in a Scheduler
Profile on page 48
node
qos-profile
scheduler-profile
shaping-rate
You can configure the effective weight of the scheduler node or queue by configuring a
static assured rate or a hierarchical assured rate (HAR). The JunosE hierarchical assured
rate (HAR) feature provides a more powerful and efficient method of configuring assured
rates than static assured rates.
When you use static assured rates, a queue is guaranteed to receive its assured rate only
when its parent node is configured with an assured rate that equals the sum of all its
child assured rates. Therefore, to ensure that a queue receives its specified assured rate,
you must frequently recalculate the assured rates on all parent nodes in the queue's
hierarchy. This recalculation is necessary because of the number of scheduler nodes and
queues that may be dynamically created or deleted through applications such as
Chapter 7: Configuring Rates and Weights in the Scheduler Hierarchy
53