EasyManua.ls Logo

Alcatel-Lucent 7450 - Page 175

Alcatel-Lucent 7450
912 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Network Queue QoS Policies
Quality of Service Guide 175
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.
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 preexisting multipoint
queue to edit queue-id parameters.
Values multipoint or not present
Default Not present (the queue is created as non-multipoint)
pool-name — The specified pool-name identifies a named pool where the policy will be applied.
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 MDA level. If the pool name is not found on either the port
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. This parameter applies only to the 7450
ESS and 7750 SR.
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.

Table of Contents

Other manuals for Alcatel-Lucent 7450

Related product manuals