QoS Scheduler Policies
Quality of Service Guide 571
A 0 (zero) cir-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 cir-level.
Values 0 to 100
Default 1
cir-level cir-level — The cir-level keyword defines the strict priority CIR level of this scheduler
in comparison to other child schedulers and queues vying for bandwidth on the parent
scheduler-name during the ‘within CIR’ distribution phase of bandwidth allocation. During
the ‘within CIR’ distribution phase, any queues or schedulers defined at a lower strict CIR
level receive no parental bandwidth until all queues and schedulers defined with a higher
(numerically larger) strict CIR level on the parent have reached their CIR bandwidth or have
satisfied their offered load requirements.
If the scheduler’s cir-level parameter retains the default (undefined) state, bandwidth is only
allocated to the scheduler during the above CIR distribution phase.
Children with the same strict cir-level are serviced according to their cir-weight.
Values Undefined, 1 to 8
Default Undefined
port-parent
Syntax port-parent [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level]
no port-parent
Context config>qos>scheduler-policy>tier>scheduler
Description The port-parent command defines a child/parent association between an egress queue and a port
based scheduler or between an intermediate service scheduler and a port based scheduler. The
command may be issued in three distinct contexts; sap-egress queue queue-id, network-queue queue
queue-id and scheduler-policy scheduler scheduler-name. The port-parent command allows for a
set of within-CIR and above-CIR parameters that define the port priority levels and weights for the
queue or scheduler. If the port-parent command is executed without any parameters, the default
parameters are assumed.
In this context, the port-parent command is mutually exclusive to the parent command (used to
create a parent/child association between a queue and an intermediate scheduler). Executing a port-
parent command when a parent definition is in place causes the current intermediate scheduler
association to be removed and replaced by the defined port-parent association. Executing a parent
command when a port-parent definition exists causes the port scheduler association to be removed and
replaced by the defined intermediate scheduler name.
To Next Page
Loading...
