Alcatel-Lucent 7450 Quality Of Service Manual page 660

Shared-Queue QoS Policy Command Reference
multipoint — This keyword specifies that this queue-id is for multipoint forwarded traffic only.
pool-name — The specified pool-name identifies a named pool where the policy will be applied.
unknown-queue
Syntax unknown-queue queue-id
no unknown-queue
Context config>qos>shared-queue>fc
Description This command configures the unknown unicast forwarding type queue mapping for fc fc-name. The
specified queue-id must exist within the policy as a multipoint queue before the mapping can be made.
Once the forwarding class mapping is executed, all unknown traffic on a SAP using this policy is
forwarded using the queue-id.
662
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
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.
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.
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 XMA or MDA level. If the pool name is not found on either
the port or XMA 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 Any valid ASCII name string
Default None
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.
Quality of Service Guide