Service Ingress Qos Policies - Alcatel-Lucent 7210 SAS E OS Quality Of Service Manual

Service Ingress QoS Policies

Service ingress QoS policies define ingress service forwarding class meters and map flows to
those meters. When a service ingress QoS policy is created, it always has two meters defined that
cannot be deleted: one for the all traffic and one for all multipoint traffic. These meters exist within
the definition of the policy. The meters only get instantiated in hardware when the policy is applied
to a SAP. In the case where the service does not have multipoint traffic, the multipoint meters will
not be instantiated.
In the simplest service ingress QoS policy, all traffic is treated as a single flow and mapped to a
single meter, and all flooded traffic is treated with a single multipoint meter. The required elements
to define a service ingress QoS policy are:
•
•
•
•
Optional service ingress QoS policy elements include:
•
•
•
Each meter can have unique meter parameters to allow individual policing of the flow mapped to
the forwarding class.
forwarding classes.
7210 SAS-E OS Quality of Service Guide
A unique service ingress QoS policy ID.
A QoS policy scope of template or exclusive.
At least one default unicast forwarding class meter. The parameters that can be configured
for a meter are discussed in
At least one multipoint forwarding class meter.
Additional unicast queues up to a total of 17.
Additional multipoint queues up to 17.
QoS policy match criteria to map packets to a forwarding class.
Figure 2 depicts service traffic being classified into three different
Meter Parameters on page
QoS Policies
26.
Page 35