sap-ingress 10 create
description‟example-policy-1”
num-qos-classifiers16
meter 1 create
exit
meter 2 create
rate cir 1 pir 20
exit
meter 3 create
rate cir 100 pir 100
exit
meter 11 multipoint create
exit
fc "af" create
meter 3
broadcast-meter 2
exit
fc "be" create
meter 3
broadcast-meter 2
exit
fc "h2" create
meter 3
broadcast-meter 2
exit
fc "l1" create
meter 3
broadcast-meter 2
exit
mac-criteria
entry 1 create
match
dot1p 7 7
exit
action fc "af"
exit
entry 2 create
match
dot1p 5 7
exit
action fc "l1"
exit
entry 3 create
match
dot1p 6 7
exit
action fc "h2"
exit
exit
default-fc "be"
In example 2, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.
FC uses unicast meter and broadcast meter, so two entries are required to identify these traffic types explicitly. Another entry is required to classify multicast and unknown-unicast traffic type to the same FC and use the default meter 11.
Using this equation, the total classification entries used = 11 (three explicit match criteria entries map to each of FC H2, L1, and AF along with a default classification rule for BE).
Meters used = 3 (FCs use only meter 2, meter 3, and meter 11).
Therefore, in this example, num-qos-classifiers 16 is used (that is, a maximum of (12, (2*3))). Note that the system internally uses 18, instead of 16.
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.
Using this equation, the total classification entries used = 4 and the total meters used = 1.