QoS Scheduler Policy Command Reference
570 Quality of Service Guide
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 scheduler-name that have been created using the
scheduler-policy-name.
Parameters scheduler-name — The scheduler-name must already exist within the context of the scheduler
policy in a tier that is higher (numerically lower).
Values Any valid scheduler-name existing on a higher tier within the
scheduler policy.
Default None. Each parental association must be explicitly created.
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 0 to 100
Default 1
level level — The level keyword defines the strict priority level of this scheduler in comparison to
other child schedulers and queues vying for bandwidth on the parent scheduler-name during
the ‘above CIR’ distribution phase of bandwidth allocation. During the above CIR
distribution phase, any queues or schedulers defined at a lower strict level receive no parental
bandwidth until all queues and schedulers defined with a higher (numerically larger) strict
level on the parent have reached their maximum bandwidth or have satisfied their offered load
requirements.
When the similar cir-level parameter default (undefined) are retained for the child scheduler,
bandwidth is only allocated to the scheduler during the above CIR distribution phase.
Children of the parent scheduler with a lower strict priority level will not receive bandwidth
until all children with a higher strict priority level have either reached their maximum
bandwidth or are idle. Children with the same strict level are serviced according to their
weight.
Values 1 to 8
Default 1
cir-weight cir-weight — The cir-weight keyword defines the relative weight of this scheduler in
comparison to other child schedulers and queues at the same cir-level defined by the cir-level
parameter. Within the strict cir-level, all cir-weight values from active children at that level
are summed and the ratio of each active child’s cir-weight
to the total is used to distribute the
available bandwidth at that level. A cir-weight is considered to be active when the queue or
scheduler that the cir-weight pertains to has not reached the CIR and still has packets to
transmit.
To Next Page
Loading...
