Overview Of Qos Policies On 7210 Sas-D And 7210 Sas-E - Alcatel-Lucent 7210 SAS Series Quality Of Service Manual

Overview of QoS Policies on 7210 SAS-D and 7210 SAS-E

7210 SAS-D and 7210 SAS-E QoS policies are applied on service ingress, access ports, egress and
access uplink ports and define the following:
•
•
•
•
There are several types of QoS policies:
•
•
•
•
•
•
Service ingress QoS policies are applied to the customer-facing Service Access Points (SAPs).
Traffic that enters through the SAP is classified to map it to a Forwarding Class (FC). Forwarding
class is associated with meters on ingress. The mapping of traffic to meters can be based on
combinations of customer QoS marking (IEEE 802.1p bits), IP and MAC criteria. The
characteristics of the forwarding class meters are defined within the policy as to the number of
forwarding class meters for unicast traffic and the meter characteristics (like CIR, PIR, etc.). Each
of the forwarding classes can be associated with different unicast parameters. A service ingress
QoS policy also defines up to three (3) meters per forwarding class to be used for multipoint traffic
for multipoint services. There can be up to 32 meters in total per Service ingress QOS policies. In
the case of the VPLS, four types of forwarding are supported (which is not to be confused with
forwarding classes), unicast, multicast, broadcast, and unknown. Multicast, broadcast, and
unknown types are flooded to all destinations within the service while the unicast forwarding type
is handled in a point-to-point fashion within the service.
An access egress policy is similar to a SAP egress policy as defined in the 7750 SR, 7450 ESS,
7710 SR series of products. The difference is the point of attachment. An access egress policy is
applied on the physical port as opposed to the logical port (SAP) for SAP egress policy. An access
egress QoS policy maps the traffic egressing out on the customer facing ports into various queues
and marks the traffic accordingly. The FCs are mapped onto the queues. There are 8 queues at the
port level. FC-to-queue mapping is static and is not configurable. The number of queues are static
and there are always 8 queues at the port level. An access egress policy also defines how to remark
the forwarding class to priority bits (For example: IEEE 802.1p bits) in the customer traffic.
7210 SAS D, E, K OS Quality of Service Guide
Classification rules for how traffic is mapped to forwarding classes
Forwarding class association with meters and meter parameters used for policing (rate-
limiting).
Queuing parameters for shaping and buffer allocation
QoS marking/interpretation
Service ingress (for access SAP ingress)
Access egress (for access port egress)
Network (for access-uplink port, ingress and egress)
Network queue (for access-uplink port, egress)
Port scheduler (for access port and access-uplink port egress)
Slope Policies
QoS Policies
Page 21