Quality of Service Guide Network Queue QoS Policies
Edition: 01 3HE 11014 AAAC TQZZA 239
The queue command with the multipoint keyword allows the creation of multipoint queues.
Only multipoint queues can receive ingress packets that need flooding to multiple
destinations. By separating the unicast traffic from multipoint traffic at network ingress and
handling the traffic on separate multipoint queues, special handling of the multipoint traffic is
possible. Each queue acts as an accounting and (optionally) shaping device, offering precise
control over potentially expensive broadcast, multicast, and unknown unicast traffic. Only the
back-end support of multipoint traffic (between the forwarding class and the queue based on
forwarding type) needs to be defined. The individual classification rules used to place traffic
into forwarding classes are not affected. Queues must be defined as multipoint at the time of
creation within the policy.
The multipoint queues are for multipoint-destined service traffic. Within non-multipoint
services, such as Epipe services, all traffic is considered unicast due to the nature of the
service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped
to a multipoint service queue.
The no form of this command removes the forwarding class-to-queue mapping, causing the
forwarding class to use the default queue instead. When a queue is removed, any pending
accounting information for each network queue created due to the definition of the queue in
the policy is discarded.
Parameters queue-id — the queue identifier for the queue, expressed as an integer. The queue-id
uniquely identifies the queue within the policy. This is a required parameter each time
the queue command is executed.
Values 1 to 8 (unicast)
9 to 16 (multipoint)
Default 1 (unicast)
9 (multipoint)
multipoint — specifies that this queue-id is for multipoint forwarded traffic only. This
queue-id can only be explicitly mapped to the forwarding class broadcast, multicast,
or unknown unicast (BMU) ingress traffic. If you attempt to map forwarding class
unicast traffic to a queue designated as multipoint, an error is generated and no
changes are made to the current unicast traffic queue mapping.
A queue that will be used for multipoint traffic 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.
Values multipoint or not present
Default not present (the queue is created as a unicast queue)
queue-type — the expedite, best-effort and auto-expedite queue types are mutually
exclusive. Each defines the method that the system uses to service the queue from
a hardware perspective. A keyword must be specified at the time the queue is
created in the network-queue policy. If an attempt is made to change the keyword
after the queue is initially defined, an error is generated.
To Next Page
Loading...
