HSMDA Command Reference
808 Quality of Service Guide
The configured priority level rate limits can be overridden at the egress port or channel using
the egress-scheduler-override level priority-level command. When a scheduler instance has
an override defined for a priority level, both the rate and cir values are overridden even when
one of them is not explicitly expressed in the override command. For instance, if the CIR
kilobits-per-second portion of the override is not expressed, the scheduler instance defaults to
not having a CIR rate limit for the priority level even when the port scheduler policy has an
explicit CIR limit defined.
Values 1, 2
weight weight-in-group — Specifies the relative weight of class-id to the other scheduling classes
within the group. If group is specified without the weight keyword, a default weight is 1.
Values 1 to 100
rate rate — If the scheduling-class command is executed with the rate keyword specified, either
max or a specified megabits-per-second rate must follow. If class-id was previously mapped
into one of the two weighted scheduling groups, the class will be removed. However, if
removing the class from the group will cause the group to no longer have contiguous class
members, the command will fail with no effect on the specified class. A non-contiguous
grouping error will be returned specifying the weighted group. The lowest or highest
members within a weighted group must be removed prior to removing the middle member.
For example, if scheduling classes 3, 4 and 5 were members of weighted group 1, class 4
cannot be removed first.
The scheduling-class command using the rate keyword will also fail in the event where an
override for the group weight is in place on the scheduling class within a scheduler associated
with the policy. The override command is expecting the class to be associated with a weighted
scheduling group and the policy rate definition is attempting to remove the class from the
group. An override mismatch error will be generated specifying the scheduling object where
the override exists (such as a SAP, subscriber or ingress HSMDA).
Once a rate has been successfully defined for a scheduling class, the specified rate is
automatically updated on all HSMDA scheduler instances associated with the scheduling
policy. The exception is where the scheduler instance has a local override for the rate on the
scheduling class.
The max keyword specifies that a limit is not enforced for the specified class-id and that the
class-id is not a member of a weighted scheduling class group. The max keyword is mutually
exclusive to the kilobits-per-second parameter and when specified, must directly follow the
rate keyword. Setting the rate of the class to max will fail when the class currently has a group
weight override defined on a scheduling object (SAP, subscriber profile or ingress HSMDA).
Values 1 to 40000000, max
HSMDA Slope QoS Policy Commands
hsmda-slope-policy
Syntax hsmda-slope-policy policy-name [create]
To Next Page
Loading...
