Redirecting a SAP forwarding class to a queue within an egress port based or ingress
forwarding plane queue group using SAP-based redirection requires four steps:
Quality of Service Guide
fc fc-name
policer policer-id group queue-group-name instance instance-id
4. Finally, the SAP ingress or SAP egress QoS policy must be applied to the SAP.
1. Create an ingress or egress queue group template. If the forwarding class redirection
is in the ingress SAP path, an ingress queue group template must be created.
Similarly, an egress queue group template must be created for egress forwarding
class redirection. Optionally, you can create the queues in a template by using default
parameters. Individual queues must be created before they are associated with a
forwarding class. The default queue parameters may be overridden on each port
based queue group.
2. Create an ingress queue group instance on the forwarding plane of the IOM/IMM/
XMA, or an egress port queue group with the same name as the template on the port
associated with the SAP.
On ingress:
config>card>fp>ingress>access>queue-group queue-group-name instance
instance-id [create]
On egress:
config>port>ethernet>access>egress>queue-group queue-group-name [instance
instance-id]
3. Redirect the SAP ingress forwarding class policer in the SAP-ingress QoS policy
using the keyword fp-redirect-group keyword on the policer, or SAP egress
forwarding class queue or policer using the port-redirect-group keyword. (Steps 2
and 3 may be done in opposite order.)
On ingress:
config>qos>sap-ingress policy-id
fc fc-name
queue queue-id fp-redirect-group
On egress:
config>qos>sap-egress policy-id
fc fc-name
queue queue-id port-redirect-group-queue
config>qos>sap-egress policy-id
fc fc-name
policer policer-id port-redirect-group-queue
Queue Sharing and Redirection
399