Forwarding Plane Queue Groups - Alcatel-Lucent 7950 Quality Of Service Manual

Forwarding Plane Queue Groups

Ingress forwarding plane queue groups allow groups of SAPs on one or more ports, or on a LAG
on the IOM/IMM/XMA, to be bundled together from a QoS enforcement perspective with an
aggregate rate limit to be enforced across all SAPs of a bundle. Multiple queue groups are
supported per IOM/IMM/XMA or port on access ingress. These are implemented at the
forwarding plane level on the ingress IOM so that SAPs residing on different ingress ports or
SAPs on a LAG spread across ports on a given IOM can be redirected to the same queue group
Once an ingress queue group template is defined, a forwarding plane queue group with the same
name may be created on an ingress forwarding plane of an IOM/IMM/XMA. Forwarding plane
queue groups are named objects that act as a container for a group of policers. Queues are not
supported in forwarding plane queue groups. Only hierarchical policers are supported in the
forwarding plane queue group, rather than queues. These policers may be configured to use
profile-aware behavior. The policers are created based on the defined policer IDs within the
associated queue group template. Multiple forwarding plane queue groups of the same template
name may be created on ingress if they have a different instance identifier. These are termed queue
group instances. Each instance of a named queue group created on a forwarding plane is an
independent set of policers structured as per the queue group template. Forwarding plane queue
groups are only supported with Ethernet ports and may be created on IOM/IMM/XMAs with ports
in a LAG.
7950 XRS Quality of Service Guide
Ingress and Egress Queue Group Creation and Redirection
Page 315