Alcatel-Lucent 7210 SAS M OS Quality Of Service Manual page 232

Basic Configurations
FCh2 = 1 + 1 + 1 + 0 = 3
Since this FC uses unicast meter and broadcast meter, two entries are needed to identify these
traffic types explicitly. Another entry is needed to classify multicast and unknown-unicast traffic
type to the same FC and use the default meter #11.
FCl1 = 1 + 1 + 1 + 0 = 3
FCaf = 1 + 1 + 1 + 0 = 3
FCl2 = 0 + 0 + 0 + 0 = 0
FCbe = 1 + 1 + 1 + 0 = 3
Using the above equation, to get the total classification entries used = 12 (since three explicit
match criteria entries map to each of FC H2, L1, and AF along with a default classification rule for
BE).
The number of meters used = 3 (since FCs use only meter #2, meter #3 and meter #11).
Hence, in this example
If the same policy were to be used for a SAP in an Epipe service, then since all traffic is classified
to a unicast traffic type and since only unicast meters are used, the following:
FCnc = 0 + 0 + 0 + 0 = 0
FCh1 = 0 + 0 + 0 + 0 = 0
FCef = 0 + 0 + 0 + 0 = 0
FCh2 = 1 + 0 + 0 + 0 = 1
FCl1 = 1 + 0 + 0 + 0 = 1
FCaf = 1 + 0 + 0 + 0 = 1
FCl2 = 0 + 0 + 0 + 0 = 0
FCbe = 1 + 0 + 0 + 0 = 1
Using the above equation, to get total classification entries used = 4 and Meters used = 1.
As can be seen here, using the same policy for Epipe SAP can lead to inefficient use of resources.
Hence, it is recommended to create a different policy with the required number of resources (i.e.
with
num-qos-classifiers 4
Example 2a (Default multipoint meter "11" is not used):
sap-ingress 10 create
description
num-qos-classifiers
meter 1 create
exit
meter 3 create
exit
meter 2 create
exit
scope template
default-fc be
Page 256
num-qos-classifiers 16
)
"example-policy-1"
8
rate cir 0 pir max
rate cir 100 pir 100
rate cir 1 pir 20
is used (i.e. maximum of (12, (2*3))).
7210 SAS M OS Quality of Service Guide