Queue Group Templates And Port Queue Groups; Queue Group Templates - Alcatel-Lucent 7450 Quality Of Service Manual

This is supported for all available transport tunnel types and is independent of the label mode
(vrf or next-hop) used within the VPRN. It is also supported for Carrier-Supporting-Carrier
VPRNs.
The ingress network interfaces on which the traffic is received must be on FP2- and higher-
based hardware. The above command is ignored on FP1-based hardware.

Queue Group Templates and Port Queue Groups

Queue Group Templates

Before a queue group with a specific name may be created on a port or an IOM/IMM/XMA
ingress forwarding plane, a queue group template with the same name must first be created.
The template is used to define each queue, scheduling attributes and its default parameters.
When a queue or policer is defined in a queue group template, that queue will exist in every
instance of a port or forwarding plane queue group with that template name. The default
queue or policer parameters (such as rate or mbs values) may be overridden with a specific
value in each queue group. This works in a similar manner to SAP ingress or SAP egress QoS
policies.
Queue sharing is also supported if the High Scale MDA (HSMDA) is used. On ingress,
HSMDA queues are bypassed, and the queue group on the IOM forwarding plane is used. On
egress, it is possible to redirect forwarding classes from multiple SAPs to an HSMDA queue
group. The HSMDA also uses the term queue group to describe a group of 8 preconfigured
hardware queues on its egress port. When queue sharing and redirection is configured on
egress, a set of 8 HSMDA queues could be configured as a part of the queue group template.
These correspond to 8 hardware queues on the HSMDA. When all eight (8) egress fcs are
mapped to the queue-group instantiated in the egress port, the per-sap hsmda queue-group
resource is freed.
Quality of Service Guide
Queue Sharing and Redirection
395