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

sap-ingress 10 create
description  ‟example-policy-2”
num-qos-classifiers  12

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
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 
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
entry 4  create
match dot1p 3
action fc h1
exit
exit

In example 3a, 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 = 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 = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 1 + 0 = 2

Because this FC uses unicast meter and broadcast meter, two entries are needed to identify these traffic types explicitly, multicast and unknown-unicast traffic use the same resource as the unicast traffic.

FCl1 = 1 + 0 + 1 + 0 = 2

Because this FC uses unicast meter and broadcast meter, two entries are needed to identify these traffic types explicitly. Multicast and unknown-unicast traffic use the same resource as unicast traffic.

FCaf = 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.

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Because no explicit meters are configured for FC ‟be”, it uses meter 1 for all traffic types and needs one entry to identify these traffic types.

Using the preceding equation, the total classification entries used = 12 and meters used = 5. The num-qos-classifiers CLI command can be set to 12 (the minimum value).

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

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 1 + 0 + 0 + 0 = 1

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, the total classification entries used = 5 and meters used = 3 (because all FCs used only meter 1, meter 3, and meter 5). For Epipe service, a policy with num-qos-resources 6 can be used.