The provisioning steps involved in using a queue-group queue on an egress access port are:
Create the queue group template.
Create the queue group template in the egress context.
Create the queue within the queue group template.
Create the queue group.
Identify the egress port (or ports) for which the queue group is needed (for LAG use the primary port member).
Create a queue group instance with the same name as the template on the port or ports.
From this point, there are two methods for regular Ethernet-based SAPs to have port access egress redirection, policy-based redirection and SAP-based redirection. For policy-based redirection:
Map a forwarding class to the queue-id within the queue group.
Identify or create the SAP egress QoS policy that is used on the egress SAP where policy-based queue redirection is needed.
Map the needed forwarding classes to the queue group name and the specific queue ID within the group with the ‟group” keyword.
Apply the SAP egress QoS policy.
Identify or create the egress SAP requiring forwarding class redirection to the queue group.
Assign the QoS policy to the SAP.
For SAP-based redirection:
Map a forwarding class to the queue-id within the queue group.
Identify or create the SAP egress QoS policy that is used on the egress SAP where SAP-based queue redirection is needed.
Map the needed forwarding classes to the queue group specific queue-id, and the keyword "port-redirect-group-queue". The actual queue-group template name is determined by the sap instance's configuration that associated the sap-egress qos policy in conjunction with the port-redirect-group's instance.
Apply the SAP egress QoS policy and the queue-group template's instance under the SAP.
Identify or create the egress SAP requiring forwarding class redirection to the queue group.
Assign the QoS policy and the egress queue-group template's instance to the SAP.