Qos Policy Entities - Alcatel-Lucent 7210 SAS M OS Quality Of Service Manual

QoS Overview

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 access egress QoS
policy, two default network QoS policy (one each for network qos policy of type ip-interface and
of type port) and two default port scheduler policy. Only one ingress QoS policy and one egress
QoS policy can be applied to a SAP, IP interface, network port, or access uplink ports.
When you create a new QoS policy, default values are provided for most parameters with the
exception of the policy ID, descriptions. Each policy has a scope, default action, a description, and
meters for ingress policies and queues for egress policies. 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:
•
•
•
QoS prioritizes traffic according to the forwarding class and uses congestion management to
control access ingress, access egress, and network traffic (network port or access-uplink port) ,
enqueuing packets according to their priority (color).
Page 74
Epipe — Only SAP ingress policies are supported on an Epipe service access point (SAP).
VPLS — Only SAP ingress policies are supported on a VPLS SAP.
VPRN — Only ingress policies are supported on a VPRN SAP.
Access egress policies on access ports
Network QoS policy on access uplinknetwork port (in network mode) or access uplink
port (in access uplink mode)
Network queue policy (egress) on access uplinknetwork port (in network mode) or access
uplink port (in access uplink mode).
7210 SAS M OS Quality of Service Guide