Alcatel-Lucent 7450 Quality Of Service Manual page 170

Network Queue QoS Policy Command Reference
slope-policy
Syntax slope-policy hsmda-slope-policy-name
no slope-policy
Context config>qos>network-queue>egress-hsmda>queue
Description This command associates an existing HSMDA slope policy to the QoS policy HSMDA queue. The
specified hsmda-slope-policy-name must exist for the command to succeed. If the policy name does
not exist, the command has no effect on the existing slope policy association. Once a slope policy is
associated with a QoS policy queue or override, the slope policy cannot be removed from the system.
Any edits to an associated slope policy are immediately applied to the queues using the slope policy.
Within the ingress and egress QoS policies, packets are classified as high priority or low-priority. For
color aware policies, packets are also potentially classified as in-profile, out-of-profile or profile-
undefined. Based on these classifications, packets are mapped to the RED slopes in the following
manner:
Ingress Slope Mapping
Egress Slope Mapping
The specified policy contains a value that defines the queue's MBS value (queue-mbs). This is the
maximum depth of the queue specified in bytes where all packets start to discard. The high and low
priority RED slopes provide congestion control mechanisms that react to the current depth of the queue
and start a random discard that increases in probability as the queue depth increases. The start point
and end point for each discard probability slope is defined as follows:
Up to 1024 HSMDA slope policies may be configured on a system.
170
• In-Profile — High Slope (priority ignored)
• Profile-Undefined, High Priority — High Slope
• Out-of-Profile Low Slope (priority ignored)
• Profile-Undefined, Low Priority — Low Slope
• In-Profile from ingress — High Slope
• Out-of-Profile from ingress — Low Slope
• Start-Utilization — This is defined as percentage of MBS and specifies where the discard
probability for the slope begins to rise above 0%. (A corresponding Start-Probability
parameter is not needed as the start probability is always 0%.
• Maximum-Utilization — This is also defined as a percentage of MBS and specifies where
(based on MBS utilized) the discard probability rises to 100%. This is the first portion of the
knee coordinates and is meaningless without the Maximum-Probability parameter.
• Maximum-Probability — This is defined as a percentage of discard probability and in
conjunction with maximum-utilization completes the knee coordinate where the discard
probability deviates from the slope and rises to 100%.
Quality of Service Guide