Alcatel-Lucent 7950 Quality Of Service Manual page 434

Shared Queue QoS Commands
queue
Syntax queue queue-id [queue-type] [profile-mode | priority-mode] [multipoint]
queue queue-id [queue-type] [multipoint]
no queue queue-id
Context config>qos>shared-queue
Description
This command creates the context to configure a shared queue QoS policy queue.
Explicit definition of an ingress queue's hardware scheduler status is supported. A single ingress
queue allows support for multiple forwarding classes. The default behavior automatically chooses the
expedited or non-expedited nature of the queue based on the forwarding classes mapped to it. As long
as all forwarding classes mapped to the queue are expedited (nc, ef, h1 or h2), the queue is treated
as an expedited queue by the hardware schedulers. When any non-expedited forwarding classes are
mapped to the queue (be, af, l1 or l2), the queue is treated as best effort (be) by the hardware
schedulers. The hardware status of the queue must be defined at the time of queue creation within the
policy.
Parameters queue-id — The queue-id for the queue, expressed as an integer. The queue-id uniquely identifies the
queue-type — The expedite, best-effort and auto-expedite queue types are mutually exclusive to
multipoint — This keyword specifies that this queue-id is for multipoint forwarded traffic only. This
Page 434
queue within the policy. This is a required parameter each time the queue command is executed.
Values
1 — 32
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.
Default
auto-expedite
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.
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.
7950 XRS Quality of Service Guide