Alcatel-Lucent 7950, Quality Of Service Manual

Page: 452 / 612

Egress Port-Based Schedulers
Page 452 7950 XRS Quality of Service Guide
Queue Parental Association Scope
A port-parent command in the sap-egress and network-queue QoS policy queue context defines
the direct child/parent association between an egress queue and a port scheduler priority level. The
port-parent command is mutually exclusive to the already-existing parent command, which
associates a queue with a scheduler at the SAP, multi-service site
or
profile level. It is possible to
mix local parented (parent to service
or
level scheduler) and port parented queues with schedulers
on the same egress port.
The port-parent command only accepts a child/parent association to the eight priority levels on a
port scheduler hierarchy. Similar to the local parent command, two associations are supported,
one for “within-cir” bandwidth (cir-level) and a second one for “above-cir” bandwidth (level). The
“within-cir” association is optional and can be disabled by using the default “within-cir” weight
value of 0. In the event that a queue with a defined parent port is on a port without a port scheduler
policy applied, that queue will be considered an orphaned queue. If a queue with a parent
command is defined on a port and the named scheduler is not found due a missing scheduler policy
or a missing scheduler of that name, the queue will be considered orphaned as well.
A queue can be moved from a local (on the SAP, multi-service site,
or
profile) parent to a port
parent priority level simply by executing the port-parent command. Once the port-parent
command is executed, any local parent information for the queue is lost. The queue can also be
moved back to a local parent at anytime by executing the local parent command. Lastly, the local
parent or port parent association can be removed at any time by using the no version of the
appropriate parent command.
Service or-Level Scheduler Parental Association Scope
The port-parent command in the scheduler-policy scheduler context (at all tier levels) allows a
scheduler to be associated with a port scheduler priority level. The port-parent command is
mutually exclusive to the parent command for schedulers at tiers 2 and 3 within the scheduler
policy. The port-parent command is the only parent command allowed for schedulers in tier 1.
The port-parent command only accepts a child/parent association to the eight priority levels on a
port scheduler hierarchy. Similar to the normal local parent command, two associations are
supported, one for “within-cir” bandwidth (cir-level) and a second one for “above-cir” bandwidth
(level). The “within-cir” association is optional and can be disabled by using the default “within-
cir” weight value of 0. In the event that a scheduler with a port parent defined is on a port without
a port scheduler policy applied, that scheduler will be considered an orphaned scheduler.
A scheduler in tiers 2 and 3 can be moved from a local (within the policy) parent to a port parent
priority level simply by executing the
port-parent command. Once the port-parent command is
executed, any local parent information for the scheduler is lost. The schedulers at tiers 2 and 3 can
also be moved back to a local parent at anytime by executing the local parent command. Lastly, the