Queue Sharing and Redirection
400 Quality of Service Guide
4. Finally, the SAP ingress or SAP egress QoS policy must be applied to the SAP. The
named queue group instance that was created on the ingress forwarding plane or the
egress port must be specified at this time.
On ingress:
config>service>epipe>sap sap-id
ingress
qos sap-ingress-policy-id fp-redirect-group queue-group-name instance
instance-id
On egress:
config>service>epipe>sap sap-id
egress
qos sap-egress-policy-id port-redirect-group queue-group-name instance
instance-id
Redirection to a queue group on the HSMDA supports the SAP-based provisioning model,
only.
Ingress and Egress SAP Forwarding Class Redirection
Association Rules
Policy Based Provisioning Model
The association rules between SAP ingress and egress QoS policies and queue group
templates are simple since both the target queue group name and queue ID within the group
are explicitly stated within the access QoS policies.
The following association rules apply when the policy based provisioning model is applied
with port queue groups.
When a SAP ingress QoS policy forwarding class is redirected to a queue group queue ID:
• If the queue group name does not exist as an ingress queue group template, the
forwarding class redirection will fail.
• If a redirection queue ID does not exist within the ingress queue group template, the
forwarding class redirection will fail.
• If the SAP ingress QoS policy is currently applied to a non-Ethernet port or an
Ethernet port where the specified ingress queue group does not exist, the forwarding
class redirection will fail.
To Next Page
Loading...
