Alcatel-Lucent 7950 Quality Of Service Manual page 389

Once a queue within a template is mapped by a forwarding class on any object, the queue may be edited, but
not deleted.
The no form of the command removes a template queue from the queue group template. If the queue is
specified as a forwarding class redirection target in any SAP ingress QoS policy, the command will fail.
Default
none
Parameters
queue-id — This required parameter identifies the queue that will either be created or edited within the
queue group template.
Values
multipoint — This optional keyword creates an ingress multipoint queue. Multipoint queues in a queue
group may be used by ingress VPLS for forwarding types multicast, broadcast or unknown within a for-
warding class. For ingress IES and VPRN access SAPs, only multicast is supported. Multipoint queues
are only supported on ingress queue group templates
queue-type — The queue types are mutually exclusive to each other.
Values
queue-mode — These keywords are optional and mutually exclusive when creating a new template queue.
The keywords specify how the queue manages ingress explicitly profiled packets.
Values
create — Keyword used to create the queue ID instance. The create keyword requirement can be enabled/
disabled in the environment>create context.
7950 XRS Quality of Service Guide
1 — 32
expedite — This keyword ensures that the queue is treated in an expedited manner
independent of the forwarding classes mapped to the queue.
best-effort — This keyword ensures that the queue is treated in a non-expedited manner
independent of the forwarding classes mapped to the queue.
profile-mode — Overrides the default priority mode of the queue and allows the adoption
of color-aware profiling within the queue. Forwarding classes and sub-classes may be
explicitly defined as in-profile or out-of-profile. Out-of-profile classified packets bypass
the CIR rate associated with the queue reserving it for the undefined or in-profile classi-
fied packets. If the template queue is not defined as profile-mode and the packet redirected
to the queue is explicitly out-of-profile based on the classification rules, the queues within
CIR bandwidth may be consumed by the packet.
priority-mode — Defines that the SAP ingress QoS policy priority classification result will be hon-
ored by the queue. Priority mode is the default mode of the queue. High priority packets are allowed
into the queue up to the mbs size defined for the queue. Low priority packets are discarded at the
low priority MBS threshold which is derived from applying the hi-prio-only percentage to the
queues MBS and subtracting that result from the mbs size defined.
Page 389