Qos Policy Entities - Alcatel-Lucent 7950 Quality Of Service Manual

QoS Policy Entities

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.
QoS policies can be applied to the following service types:
•
•
•
QoS policies can be applied to the following entities:
•
•
Default QoS policies maps 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
7950 XRS Quality of Service Guide
Epipe — Both ingress and egress policies are supported on an Epipe service access point
(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.
Network ingress interface
Network egress interface
QoS Policies
Page 67