Alcatel-Lucent 7450 Quality Of Service Manual page 808

HSMDA Command Reference
Parameters policy-name — Specifies a HSMDA slope policy. Each HSMDA slope policy must be uniquely
create — The create keyword is required when the create command is enabled in the
high-slope
Syntax high-slope
Context config>qos>hsmda-slope-policy
Description This command enables the high priority RED slope context of an HSMDA slope policy. Within the
high-slope context, the high priority RED slope configuration commands defining the start of slope,
end of slope and maximum probability points may be executed.
For ingress, packets classified as priority high or profile in are mapped to the high priority RED slope
for queue congestion management.
At egress, packets received from ingress as in-profile are mapped to the high priority RED slope for
queue congestion management. In-profile is derived at ingress either from within-CIR profiling or
from explicit profile in classification.
start-depth
Syntax start-depth percent-of-queue-depth
no start-depth
Context config>qos>hsmda-slope-policy>high-slope
config>qos>hsmda-slope-policy>low-slope
Description This command defines the starting point for a slope relative to the maximum depth of the queue-mbs
value of the HSMDA slope policy. At the point the slope starts, it rises from a discard probability of
zero until it reaches the max-depth and max-prob points defining where the slope rises directly to a
discard probability of 100%.
As packets arrive at the queue, a random number is generated that is ranged from 0 to 100% discard
probability. The packet will be associated with either the high priority slope or the low priority slope.
The current queue depth plots the position where the slope will be evaluated. If the random number is
equal to or greater than the slope's discard probability at the current depth, the packet is eligible to enter
the queue. If the random number is less than the slope discard probability, the packet is discarded.
810
named within the system. Names of up to 32 ASCII characters are supported with the normal
character restrictions. An HSMDA slope policy must be exist prior to applying the policy
name to an HSMDA queue. 1024 policies are allowed per system.
environment context to create a new HSMDA scheduler policy. This keyword is not required
when the protection is disabled. The keyword is ignored when the HSMDA scheduler policy
already exists.
Quality of Service Guide