Alcatel-Lucent 7450 Quality Of Service Manual page 360

Ethernet service switch; service router; extensible routing system
Hide thumbs Also See for 7450:
Table of Contents

Advertisement

Service SAP QoS Policy Command Reference
containing the scheduler-name being directly or indirectly applied (through a multi-service customer
site) to the egress SAP. If the scheduler-name does not exist, the queue is placed in the orphaned
operational state. The queue will accept packets but will not be bandwidth limited by a virtual
scheduler or the scheduler hierarchy applied to the SAP. The 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
weight weight — weight defines the relative weight of this queue in comparison to other child
360
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.
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.
Quality of Service Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

79507750

Table of Contents