Example 2a (default multipoint meter 11 is not used)

sap-ingress 10 create
description  ‟example-policy-1”
num-qos-classifiers  8

meter 1 create
rate cir 0 pir max
exit
meter 3 create
rate cir  100 pir 100
exit
meter 2 create
rate cir 1 pir 20
exit
scope template
default-fc be
fc be  create
meter  3
broadcast-meter 2
exit
fc af  create
meter  3
broadcast-meter 2
exit
fc l1  create
meter  3
broadcast-meter 2
exit
fc h2  create
meter  3
broadcast-meter 2
exit
mac-criteria dot1p-only
entry  1  create
match dot1p  7
action fc af
exit
entry 2  create
match dot1p 5
action fc l1
exit
entry 3 create
match dot1p  6
action fc h2
exit
exit

In example 2a, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 1 + 0 = 2

Because this FC uses a unicast meter for unicast, multicast, unknown-unicast traffic, and broadcast meter for broadcast traffic, so two entries are needed.

FCl1 = 1 + 0 + 1 + 0 = 2

FCaf = 1 + 0 + 1 + 0 = 2

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 1 + 0 = 2

Using this equation to get the total classification, entries used = 8 (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 = 2 (FCs use only meter 2 and meter 3).

Hence, in this example num-qos-classifiers 8 is used (that is, maximum of (8, (2*2))).

If the same policy were used for a SAP in an Epipe service, all traffic is classified to a unicast traffic type and only unicast meters are used, use the following computation.

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 preceding 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. Nokia recommends creating a different policy with the required number of resources (that is, with num-qos-classifiers 4).