Alcatel-Lucent 7950, Quality Of Service Manual

Page: 214 / 612

Service Ingress QoS Policy Commands
Page 214 7950 XRS Quality of Service Guide
services. Buffer pool queries return zero values for actual buffers allocated and current buffer utilization.
The no form of this command removes the queue-id from the SAP ingress QoS policy and from any existing
SAPs using the policy. If any forwarding class forwarding types are mapped to the queue, they revert to their
default queues. When a queue is removed, any pending accounting information for each SAP queue created
due to the definition of the queue in the policy is discarded.
The pool keyword is a create time parameter that allows the queue to receive buffers from an explicit buffer
pool instead of the default buffer pool. The specified pool-name must have been explicitly created in a
named-pool-policy and the policy must have been applied to the MDA or port on which the queue resides.
If the specified pool-name does not exist on the MDA, the queue will be treated as ‘pool orphaned’ and will
be mapped to the appropriate default pool. Once the pool comes into existence on the MDA or port, the
queue will be mapped to the new pool.
Once the queue is created within the policy, the pool command may be used to either remove the queue from
the pool, or specify a new pool name association for the queue. The pool command does not appear in save
or show command output. Instead, the current pool name for the queue will appear (or not appear) on the
queue command output using the pool keyword.
Parameters queue-id — The queue-id for the queue, expressed as an integer. The queue-id uniquely identifies the queue
within the policy. This is a required parameter each time the queue command is executed.
Values 1 — 32
queue-type — The expedite , best-effort and auto-expedite queue types are mutually exclusive to each
other. Each defines the method that the system uses to service the queue from a hardware perspective. While
parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for
bandwidth with other queues associated with the same scheduler hierarchy. An internal mechanism that
provides access rules when the queue is vying for bandwidth with queues in other virtual schedulers is also
needed. A keyword must be specified at the time the queue is created in the SAP ingress policy. If an attempt
to change the keyword after the queue is initially defined, an error is generated.
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.
auto-expedite — This keyword allows the system to auto-define the way the queue is serviced by the
hardware. When auto-expedite is defined on the queue, the queue is treated in an expedited manner
when all forwarding classes mapped to the queue are configured as expedited types
nc
,
ef
,
h1
or
h2
.
When a single non-expedited forwarding class is mapped to the queue (
be
,
af
,
l1
and
l2
) the queue
automatically falls back to non-expedited status.
Values expedite, best-effort, auto-expedite
Default auto-expedite
multipoint — This keyword specifies that this queue-id is for multipoint forwarded traffic only. This queue-
id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast
ingress traffic. If you attempt to map forwarding class unicast traffic to a multipoint queue, an error is
generated and no changes are made to the current unicast traffic queue mapping.