Ingress Criteria Classification Directly To Policer - Alcatel-Lucent 7450 Quality Of Service Manual

Service Ingress QoS Policy

Ingress Criteria Classification Directly to Policer

It is possible to classify traffic directly to a policer, independent of the policer/queue assigned
to the traffic's forwarding class. This is supported at SAP ingress when using one of the
following statements: ip-criteria, ipv6-criteria or mac-criteria.
The standard mechanisms are still used to assign a forwarding class to the related traffic, and
this forwarding class continues to be used for QOS processing at egress.
This is supported on all FP2 and higher based line cards. The use of explicitly configured
broadcast, unknown, or multicast policers is not supported. QPPB processing takes
precedence over this feature.
This could be used, for example, when it is required that ingress OAM traffic is not subject
to the same QOS control as other customer traffic on a given SAP. The OAM traffic could be
classified based on its source MAC address (for example, with an OUI of 00-xx-yy as
configured below) and directed to policer 1 while the remainder of the customer's traffic is
processed using ingress queue 1. This is shown in
OAM Traffic
Customer Traffic
The configuration would be as follows:
214
exit
exit
Figure 18: Ingress Criteria Classification Directly to Policer
Ingress SAP
Policer1
FC=BE
Queue1
sap-ingress 10 create
queue 1 create
exit
queue 11 multipoint create
exit
policer 1 create
exit
mac-criteria
entry 10 create
match
exit
Switch Fabric
OAM Traffic
Customer Traffic
src-mac 00-xx-yy-00-00-00 ff-ff-ff-00-00-00
Figure 18.
Egress SAP/Network
Queue
FC=BE
Quality of Service Guide
al_0349