QoS Policies
7950 XRS Quality of Service Guide
Page 33
Adaptation Rule
The adaptation rule provides the QoS provisioning system with the ability to adapt specific CIR
and PIR defined administrative rates to the underlying capabilities of the hardware the queue will
be created on to derive the operational rates. The administrative CIR and PIR rates are translated to
actual operational rates enforced by the hardware queue. The rule provides a constraint used when
the exact rate is not available due to hardware implementation trade-offs.
For the CIR and PIR parameters individually, the system will attempt to find the best operational
rate depending on the defined constraint. The supported constraints are:
•
Minimum — Find the hardware supported rate that is equal to or higher than the specified
rate.
•
Maximum — Find the hardware supported rate that is equal to or lesser than the specified
rate.
•
Closest — Find the hardware supported rate that is closest to the specified rate.
Depending on the hardware upon which the queue is provisioned, the actual operational CIR and
PIR settings used by the queue will be dependant on the method the hardware uses to implement
and represent the mechanisms that enforce the CIR and PIR rates.
The adaptation rule always assumes that the PIR (shaping parameter) on the queue is the most
important rate. When multiple available hardware rates exist for a given CIR and PIR rate pair, the
PIR constraint is always evaluated before the CIR.
to define the granularity for both the CIR and PIR rates The adaptation rule controls the method
the system uses to choose the rate step based on the administrative rates defined by the
rate
command.
QoS Enhancements
The maximum rate configurable for queue PIR and CIR rates in a SAP ingress and egress policy
(when used with SAP or subscribers), and in an ingress and egress queue group, have been
increased to 2000 Gbps.
If the rates at ingress exceed the port capacity, or exceed the FP capacity with
per-fp-ing-queuing
configured, the rates are set to
max
. At egress, if the rates exceed the port capacity (including the
egress-rate
setting) they are set to
max
. As a consequence, the maximum queue rate used can
change and hence the behaviour of some existing configurations can change. This also impacts the
use of
percent-rates
with no parent or a
max-rate
parent, or the use of the
advanced-config-policy
with a
percent
percent-of-admin-pir
.
Rates greater than the above (capped) rates are only relevant when configured on a queue which is
part of a distributed or port-fair mode LAG spanning multiple FPs.
Summary of Contents for 7950
Page 12: ...Page 12 7950 XRS Quality of Service Guide List of Figures ...
Page 16: ...Preface Page 16 7950 XRS Quality of Service Guide ...
Page 82: ...Editing QoS Policies Page 82 7950 XRS Quality of Service Guide ...
Page 90: ...Applying Network Queue Policies Page 90 7950 XRS Quality of Service Guide ...
Page 96: ...Editing QoS Policies Page 96 7950 XRS Quality of Service Guide ...
Page 98: ...Command Hierarchies Page 98 7950 XRS Quality of Service Guide ...
Page 108: ...Command Hierarchies Page 108 7950 XRS Quality of Service Guide ...
Page 156: ...Basic Configurations Page 156 7950 XRS Quality of Service Guide exit exit ...
Page 164: ...Queue Depth Monitoring Page 164 7950 XRS Quality of Service Guide ...
Page 304: ...Service Queue QoS Policy Commands Page 304 7950 XRS Quality of Service Guide ...
Page 368: ...Command Hierarchies Page 368 7950 XRS Quality of Service Guide ...
Page 430: ...Configuration Commands Page 430 7950 XRS Quality of Service Guide ...
Page 532: ...Editing QoS Policies Page 532 7950 XRS Quality of Service Guide ...
Page 552: ...Editing Advanced Policies Page 552 7950 XRS Quality of Service Guide ...
Page 600: ...Command Hierarchies Page 600 7950 XRS Quality of Service Guide ...
Page 602: ...QoS Commands Page 602 7950 XRS Quality of Service Guide ...
Page 610: ...Standards and Protocols Page 610 7950 XRS Quality of Service Guide ...
Page 612: ... 2015 Alcatel Lucent All rights reserved 3HE 09868 AAAA TQZZA 01 ...