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

sap-ingress 10 create
description  ‟example-policy-3”
num-qos-classifiers  20
meter 1 create
rate cir 100 pir 100
exit
meter 3 create
rate cir  100 pir 100
exit
meter 2 create
rate cir 1 pir 20
exit
meter 4 create
rate cir 10 pir 100
exit
meter 5 create
rate cir 10 pir 10
exit
meter 6 create
rate cir 11 pir 100
exit
meter 8 create
rate cir 20 pir 100
exit
scope template
default-fc  be
fc af  create
meter  3
broadcast-meter 2
multicast-meter 4
exit
fc l1  create
meter 3
broadcast-meter 2
exit
fc h2 create
meter 3
broadcast-meter 2
exit
fc h1 create
meter 5
broadcast-meter 4
multicast-meter 4
unknown-meter 4
exit
fc ef  create
meter 6
broadcast-meter 2
multicast-meter 8
exit
fc nc  create
meter 6
broadcast-meter 2
multicast-meter 8
exit
mac-criteria dot1p-only
entry  1  create
match dot1p  4
action fc af
exit
entry  2  create
match dot1p 5
action fc l1
exit
entry  3   create
match dot1p  6
action fc h2
exit
entry  4  create
match dot1p 3
action fc h1
exit
entry   5  create
match dot1p 2
action fc ef
exit
entry   6  create
match dot1p 7
action fc nc
exit
exit
exit

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

FCnc = 1 + 1 + 1 + 0 = 3

Because this FC uses unicast, broadcast, and multicast meter, three entries are needed to identify these traffic types explicitly. Unknown-unicast traffic type is classified using the same entry as multicast traffic type and uses the same meter.

FCh1 = 1 + 1 + 1 + 1 = 4

Because this FC uses unicast, broadcast, multicast, and unknown-unicast meter, four entries are needed to identify these traffic types explicitly.

FCef = 1 + 1 + 1 + 0 = 3

FCh2 = 1 + 1 + 1 + 0 = 3

Because this FC uses unicast meter and broadcast meter, two entries are needed to identify these traffic types explicitly. Multicast and unknown-unicast traffic of the same FC use the unicast resources (both meter and classification entry).

FCl1 = 1 + 1 + 1 + 0 = 3

FCaf = 1 + 1 + 1 + 0 = 3

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Because this FC uses a single meter for all traffic-types only, a single meter and single entry is needed.

Using the preceding equation, the total classification entries used = 20 and meters used = 7. Therefore, in this example num-qos-classifiers 20 is used (the minimum value).

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 = 1 + 0 + 0 + 0 = 1

FCh1 = 1 + 0 + 0 + 0 = 1

FCef = 1 + 0 + 0 + 0 = 1

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, the total classification entries used = 7 and meters used = 4.

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 8).