Policy-based redirection

About this task

Redirecting a SAP forwarding class to a queue within a port-based queue group using policy-based redirection requires four steps.

Procedure

  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, the queues in a template can be created 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. (This step and the following step can be done in the opposite order.) Create an ingress or egress queue group instance with the same name as the template on the port associated with the SAP. Examples are as follows:
    On ingress ports:
    config>port>ethernet>access>ingress>queue-group queue-group-name
    On egress ports:
    config>port>ethernet>access>egress>queue-group queue-group-name [instance instance-id]
    Queue parameter overrides can also be applied at this time.
  3. Redirect the SAP ingress or SAP egress QoS policy forwarding class policer or queue to the queue group name and wanted queue ID. Examples are as follows:
    On ingress:
    config>qos>sap-ingress policy-id
    fc fc-name
    queue queue-id group queue-group-name
    On egress:
    config>qos>sap-egress policy-id
    fc fc-name
    queue queue-id group queue-group-name instance instance-id

    config>qos>sap-egress policy-id
    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.
Parent topic: Access SAP forwarding class-based redirection