Alcatel-Lucent 7450 Quality Of Service Manual page 166

Network Queue QoS Policy Command Reference
The no form of this command removes the queue-id from the network-queue policy and from any
existing XMA, MDA, or port 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 XMA, MDA, or port queue created due to the definition of the queue in the policy
is discarded.
Resource Utilization
When the network-queue policy is applied on a ingress XMA or MDA, each unicast queue is created
multiple times - once for each switch fabric destination currently provisioned. Some IOM types on the
7450 ESS and 7750 SR represent one switch fabric destinations while others may represent two. XCMs
on a 7950 XRS represent two switch fabric destinations, where each XMA is one destination. At
egress, a single queue is created since the policy is applied at the port level. Queues are only created
when at least one forwarding class is mapped to the queue using the queue command within the
forwarding class context.
Parameters queue-id — The queue-id for the queue, expressed as an integer. The queue-id uniquely identifies
queue-type — The expedite, best-effort and auto-expedite queue types are mutually exclusive to
expedite — This keyword ensures that the queue is treated in an expedited manner independent
best-effort — This keyword ensures that the queue is treated in a non-expedited manner
auto-expedite — This keyword allows the system to auto-define the way the queue is serviced by
multipoint — This keyword specifies that this queue-id is for multipoint forwarded traffic only.
166
the queue within the policy. This is a required parameter each time the queue command is
executed.
Values 1 to 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 network-queue policy. If an attempt to change
the keyword after the queue is initially defined, an error is generated.
of the forwarding classes mapped to the queue.
independent of the forwarding classes mapped to the queue.
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
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.
Quality of Service Guide