Queue Sharing and Redirection
Quality of Service Guide 427
→ Create the queues and/or policers within the queue group template.
• Queue Group Creation:
→ Identify the egress port (or ports) on which the queue group will be needed (for
LAG use the primary port member).
→ Create a queue group with the same name as the template on the port or ports.
The instance ID is optional.
• Map a Forwarding Class to the queue-id within the queue group:
→ Identify or create the network QoS policy that will be used on the egress IP
interface where queue redirection is desired.
→ Map the desired egress forwarding classes within the network QoS policy to the
specific queue IDs and/or policer IDs within the group (the group name will be
supplied when the QoS policy is applied to the IP interface).
• Apply the network QoS policy:
→ Identify or create the IP interface requiring forwarding class redirection to the
queue group.
→ Assign the QoS policy to the IP interface and specify the queue group name (and
optionally instance ID) for redirection of egress traffic.
Once a queue within a template is mapped by a forwarding class on any object, the queue may
be edited, but not deleted.
Configuring Queue Group for Network Ingress Traffic on
Forwarding Plane
The provisioning steps involved in using a queue-group for ingress traffic on a network
interface are:
• Queue Group Template Creation:
→ Create the ingress queue group template.
→ Create the policers within the queue group template.
• Queue Group Creation:
→ Identify the ingress forwarding plane on which the queue group will be needed.
→ Create a queue group with the same name as the template in the FP ingress
network configuration context. An instance ID is mandatory.
• Map a Forwarding Class to the policer-id within the queue group:
→ Identify or create the network QoS policy that will be used on the ingress IP
interface where queue redirection is desired.
To Next Page
Loading...
