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 entity.
When a new QoS policy is created, 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, description, and at least one queue. The queue is associated with a forwarding class.
Table: Service types and applicable service QoS policies lists which service QoS policies are supported for each service type.
| Service type | Qos policies |
|---|---|
|
Epipe |
Both ingress and egress policies are supported on an Epipe SAP. |
|
VPLS |
Both ingress and egress policies are supported on a VPLS SAP. |
|
IES |
Both ingress and egress policies are supported on an IES SAP. |
|
VPRN |
Both ingress and egress policies are supported on a VPRN SAP. |
Network QoS policies can be applied to the following entities:
network interfaces
Cpipe/Epipe/Ipipe and VPLS spoke-SDPs
VPLS spoke- and mesh-SDPs
IES and VPRN interface spoke-SDPs
VPRN network ingress
VXLAN network ingress
Network queue policies can be applied to:
ingress FPs
egress ports
Default QoS policies map all traffic with equal priority and allow an equal chance of transmission (Best Effort (be) 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.