Alcatel-Lucent 7950, Quality Of Service Manual, Page: 287 / 612

7950 XRS Quality of Service Guide Page 287
port-parent
Syntax port-parent [ weight weight ] [ level level ] [ cir-weight cir-weight ] [ cir-level cir-level ]
no port-parent
Context config>qos>sap-egress>queue
Description This command specifies whether this queue feeds off a port-level scheduler. When configured, this SAP
egress queue is parented by a port-level scheduler. This object is mutually exclusive with SAP egress queue
parent. Only one kind of parent is allowed.
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.
Changing the parent context on a SAP egress policy queue may cause a SAPor context of the queue (policy
associated with a SAP or) to enter an orphaned state. If an instance of a queue is created on a port that does
not have a port scheduler enabled and the sap-egress policy creating the queue has a port-parent association,
the queue will be allowed to run according to its own rate parameters and will not be controlled by a virtual
scheduling context. If an instance of a queue is on a port that has a port scheduler configured and the sap-
egress policy defines the queue as having a non-existent intermediate scheduler parent, the queue will be
treated as an orphan and will be handled according to the current orphan behavior on the port scheduler.
The no form of this command removes a port scheduler parent association for the queue or scheduler. If a
port scheduler is defined on the port which the queue or scheduler instance exists, the queue or scheduler
will become orphaned if an port scheduler is configured on the egress port of the queue or scheduler.
Default no port-parent
Parameters weight weight — Defines the weight the queue or scheduler will use at the above-cir port priority level
(defined by the level parameter).
Values 0 — 100
Default 1
level level — Defines the port priority the queue or scheduler will use to receive bandwidth for its above-cir
offered-load.
Values 1 — 8 (8 is the highest priority)
Default 1
cir-weight cir-weight — Defines the weight the queue or scheduler will use at the within-cir port priority
level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with