Alcatel-Lucent 7450 Quality Of Service Manual page 165

Description This command overrides the default multicast 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 multicast traffic using this policy is forwarded
using the queue-id.
The multicast forwarding type includes the unknown unicast forwarding type and the broadcast
forwarding type unless each is explicitly defined to a different multipoint queue. When the unknown
and broadcast forwarding types are left as default, they will track the defined queue for the multicast
forwarding type.
The no form of the command sets the multicast forwarding type queue-id back to the default queue for
the forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to
a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
Resource Utilization
When a multipoint queue is created and at least one forwarding class is mapped to the queue using the
multipoint-queue command, a single ingress multipoint hardware queue is created per instance of the
applied network-queue policy using the queue-policy command at the ingress network XMA or MDA
level. Multipoint queues are not created at egress and the multipoint queues defined in the network-
queue policy are ignored when the policy is applied to an egress port.
Parameters queue-id — The queue-id parameter specified must be an existing, multipoint queue defined in the
queue
Syntax queue queue-id [multipoint] [queue-type] pool pool-name [create]
no queue queue-id
Context config>qos>network-queue
Description This command creates the context to configure forwarding-class to queue mappings.
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 expedited hardware schedulers are used to enforce expedited access to internal switch fabric
destinations. The hardware status of the queue must be defined at the time of queue creation within the
policy.
Quality of Service Guide
config>qos>network-queue>queue context.
Values Any valid multipoint queue-ID in the policy including 2 through
16.
Default 11
Network Queue QoS Policies
165