Services are configured with default QoS policies. Additional policies must be explicitly created and associated. There is one default service ingress QoS policy, one default service egress QoS policy, and one default network QoS policy. Only one ingress QoS policy and one egress QoS policy can be applied to a SAP or network port.
When you create a new QoS policy, default values are provided for most parameters with the exception of the policy ID and queue ID values, descriptions, and the default action queue assignment. Each policy has a scope, default action, a description, and at least one queue. The queue is associated with a forwarding class.
All QoS policy parameters can be configured in the CLI. QoS policies can be applied to the following service types:
Epipe — both ingress and egress policies are supported on an Epipe SAP
Apipe — both ingress and egress policies are supported on an Apipe SAP
Cpipe — only ingress policies are supported on a Cpipe SAP
Fpipe — both ingress and egress policies are supported on an Fpipe SAP
Hpipe — both ingress and egress policies are supported on an Hpipe SAP
Ipipe — both ingress and egress policies are supported on an Ipipe SAP
QoS policies can be applied to the following network entities:
network ingress interface
network egress interface
Default QoS policies treat all traffic with equal priority and allow an equal chance of transmission (Best Effort forwarding class) and an equal chance of being dropped during periods of congestion. QoS prioritizes traffic according to the forwarding class and uses congestion management to control access ingress, access egress, and network traffic with queuing according to priority.