Alcatel-Lucent 7950 Quality Of Service Manual page 497

limit-unused-bandwidth
Syntax [no] limit-unused-bandwidth
Context config>qos>scheduler-policy>tier>scheduler
Description
This command is used to enable (or disable) aggregate rate overrun protection on the agg-rate context.
parent
Syntax parent scheduler-name [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level]
no parent
Context config>qos>scheduler-policy>tier level>scheduler
Description
This command defines an optional parent scheduler that is higher up the policy hierarchy. Only schedulers in
tier levels 2 and 3 can have a parental association. When multiple schedulers and/or queues share a child
status with the scheduler on the parent, the weight or strict parameters define how this scheduler contends
with the other children for the parent's bandwidth. The parent scheduler can be removed or changed at
anytime and is immediately reflected on the schedulers created by association of this scheduler policy.
When a parent scheduler is defined without specifying weight or strict parameters, the default bandwidth
access method is weight with a value of 1.
The no form of the command removes a child association with a parent scheduler. If a parent association
does not currently exist, the command has no effect and returns without an error. Once a parent association
has been removed, the former child scheduler attempts to operate based on its configured rate parameter.
Removing the parent association on the scheduler within the policy will take effect immediately on all
schedulers with
Parameters
scheduler-name — The
tier that is higher (numerically lower).
Values
Default
weight weight — Weight defines the relative weight of this scheduler in comparison to other child
schedulers and queues at the same strict level defined by the level parameter. Within the level, all
weight values from active children at that level are summed and the ratio of each active child's weight
to the total is used to distribute the available bandwidth at that level. A weight is considered to be active
when the queue or scheduler the weight pertains to has not reached its maximum rate and still has
packets to transmit.
A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is
distributed to all other non-zero weighted children in the strict level.
Values
Default
7950 XRS Quality of Service Guide
scheduler-name that have been created using the scheduler-policy-name.
scheduler-name
Any valid scheduler-name existing on a higher tier within the scheduler policy.
None. Each parental association must be explicitly created.
0 to 100
1
scheduler-name
must already exist within the context of the scheduler policy in a
Page 497