Alcatel-Lucent 7950 Quality Of Service Manual page 215

A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is
created. If an attempt is made to modify the command to include the multipoint keyword, an error is
generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint queue to edit
queue-id parameters.
Values
Default
queue-mode — Specifies the mode in which the queue is operating. This attribute is associated with the
queue at the time of creation and cannot be modified thereafter.
Values
Default
pool-name — The specified pool-name identifies a named pool where the policy will be applied. Each queue
created within the system is tied to a physical port. When the policy is applied and the queue is created,
the system will scan the named pools associated with the port to find the specified pool name. If the
pool is not found on the port, the system will then look at named pools defined at the ports MDA level.
If the pool name is not found on either the port or MDA, the queue will be marked as 'pool-orphaned'
and will be mapped to the appropriate default pool. If the pool comes into existence, the queue will be
moved from the default pool to the new named pool and the 'pool-orphaned' state will be cleared. The
specified name must be an ASCII name string up to 16 characters long.
Values
Default
The queue's pool association may only be removed by either re-executing the queue command without
the pool keyword or by executing the no pool command within the queue's CLI context. When the pool
name is removed, the queue will be placed on the appropriate default pool.
7950 XRS Quality of Service Guide
multipoint or not present
Present (the queue is created as non-multipoint)
profile-mode: When the queue is operating in the profile mode (or, the color aware
mode), the queue tries to provide the appropriate bandwidth to the packets with different
profiles. The profiles are assigned according to the configuration of the forwarding class
or the sub-forwarding class.
priority-mode: The queue is capable of handling traffic differently with two distinct
priorities. These priorities are assigned by the stages preceding the queueing framework in
the system. In priority mode, the queue does not have the functionality to support the
profiled traffic and in such cases the queue will have a degraded performance. However,
the converse is not valid and a queue in profile mode should be capable of supporting the
different priorities of traffic.
priority-mode
Any valid ASCII name string
None
Page 215