
Service Queue QoS Policy Commands
Page 284
7950 XRS Quality of Service Guide
orphaned state must generate a log entry and a trap message. The SAP which the queue belongs to must also
depict an orphan queue status. The orphaned state of the queue is automatically cleared when the
scheduler-
name
becomes available on the egress SAP.
The parent scheduler can be made unavailable due to the removal of a scheduler policy or scheduler. When
an existing parent scheduler is removed or inoperative, the queue enters the orphaned state mentioned above
and automatically return to normal operation when the parent scheduler is available again.
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 queue attempts to operate based on its configured rate parameter.
Removing the parent association on the queue within the policy takes effect immediately on all queues using
the SAP egress QoS policy.
Parameters
scheduler-name —
The defined
scheduler-name
conforms to the same input criteria as the schedulers
defined within a scheduler policy. Scheduler names are configured in the
config>qos>scheduler-policy>tier
level
context. There are no checks performed at the
time of definition to ensure that the
scheduler-name
exists within an existing scheduler policy. For the
queue to use the defined
scheduler-name
, the scheduler exists on each egress SAP the queue is
eventually created on. For the duration where
scheduler-name
does not exist on the egress SAP, the
queue operates in an orphaned state.
Values
Any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the
string contains special characters (#, $, spaces, etc.), the entire string must be enclosed
within double quotes.
Default
None. Each parental association must be explicitly defined.
weight
weight — weight
defines the relative weight of this queue in comparison to other child schedulers
and queues while vying for bandwidth on the parent
scheduler-name
. Any queues or schedulers defined
as weighted receive no parental bandwidth until all strict queues and schedulers on the parent have
reached their maximum bandwidth or are idle. In this manner, weighted children are considered to be
the lowest priority.
All
weight
values from all weighted active queues and schedulers with a common parent scheduler are
added together. Then, each individual active weight is divided by the total, deriving the percentage of
remaining bandwidth provided to the queue or scheduler after the strict children are serviced. A weight
is considered to be active when the pertaining queue or scheduler has not reached its maximum rate and
still has packets to transmit. All child queues and schedulers with a weight of 0 are considered to have
the lowest priority level and are not serviced until all strict and non-zero weighted queues and
schedulers are operating at the maximum bandwidth or are idle.
Values
0 — 100
Default
1
level
level —
The optional
level
parameter defines the level of hierarchy when compared to other schedulers
and queues when vying for bandwidth on the parent
scheduler-name
. Any queues or schedulers defined
as
strict
receive no parental bandwidth until all strict queues and schedulers with a higher (numerically
larger) priority on the parent have reached their maximum bandwidth or are idle.
Содержание 7950
Страница 12: ...Page 12 7950 XRS Quality of Service Guide List of Figures ...
Страница 16: ...Preface Page 16 7950 XRS Quality of Service Guide ...
Страница 82: ...Editing QoS Policies Page 82 7950 XRS Quality of Service Guide ...
Страница 90: ...Applying Network Queue Policies Page 90 7950 XRS Quality of Service Guide ...
Страница 96: ...Editing QoS Policies Page 96 7950 XRS Quality of Service Guide ...
Страница 98: ...Command Hierarchies Page 98 7950 XRS Quality of Service Guide ...
Страница 108: ...Command Hierarchies Page 108 7950 XRS Quality of Service Guide ...
Страница 156: ...Basic Configurations Page 156 7950 XRS Quality of Service Guide exit exit ...
Страница 164: ...Queue Depth Monitoring Page 164 7950 XRS Quality of Service Guide ...
Страница 304: ...Service Queue QoS Policy Commands Page 304 7950 XRS Quality of Service Guide ...
Страница 343: ...Ingress and Egress Queue Group Creation and Redirection 7950 XRS Quality of Service Guide Page 343 ...
Страница 368: ...Command Hierarchies Page 368 7950 XRS Quality of Service Guide ...
Страница 430: ...Configuration Commands Page 430 7950 XRS Quality of Service Guide ...
Страница 468: ...Basic Configurations Page 468 7950 XRS Quality of Service Guide exit exit no shutdown exit A SR config service ...
Страница 532: ...Editing QoS Policies Page 532 7950 XRS Quality of Service Guide ...
Страница 552: ...Editing Advanced Policies Page 552 7950 XRS Quality of Service Guide ...
Страница 598: ...Interaction Between Profile Preferred and Profile Capped Mode Page 598 7950 XRS Quality of Service Guide ...
Страница 600: ...Command Hierarchies Page 600 7950 XRS Quality of Service Guide ...
Страница 602: ...QoS Commands Page 602 7950 XRS Quality of Service Guide ...
Страница 610: ...Standards and Protocols Page 610 7950 XRS Quality of Service Guide ...
Страница 612: ... 2015 Alcatel Lucent All rights reserved 3HE 09868 AAAA TQZZA 01 ...