sap-ingress 10 create
description ‟example-policy-1”
num-qos-classifiers 16
meter 1 create
rate cir 0 pir max
exit
meter 11 multipoint create
rate cir 0 pir max
exit
meter 3 create
rate cir 100 pir 100
exit
meter 4 create
rate cir 10 pir 50
exit
scope template
default-fc be
fc be create
meter 3
exit
fc af create
meter 1
exit
fc l1 create
meter 3
multicast-meter 4
exit
fc h2 create
meter 3
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
exit
In the example above, assuming the policy is attached to a SAP in a VPLS service, the following number of classification entries per FC:
Because FCl1 uses unicast meter and multicast meter, an entry is needed to identify these traffic types explicitly. Broadcast and unknown-unicast traffic is also classified using the same entry as multicast and use the same meter.
Because FCaf uses unicast meter, an entry is needed to identify these traffic types explicitly. Another entry is needed to classify broadcast, multicast and unknown-unicast traffic type to the same FC and use the default meter ‟11”.
Using the above equation, the total classification entries used = 8 and meters used = 4.
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:
Using the above equation, the total classification entries used = 4 and meters used = 2.