sap-ingress 10 create
num-qos-classifiers 16
meter 1 create
exit
meter 11 multipoint create
exit
meter 3 create
exit
meter 4 create
exit
fc be create
meter 1
broadcast-meter 11
mulitcast-meter 4
exit
fc af create
meter 3
exit
default-fc be
mac-criteria dot1p-only
entry 1 create
match dot1p 7 7
action fc af
exit
dot1p 7 fc af
exit
match entry 2
dot1p 5 fc af
exit
match entry 3
dot1p 3 fc af
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 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”.
Because FCbe 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.
Using the equation, calculate the total classification entries used by this policy, as follows
The number of meters used in this policy = 4.
Hence, in this example num-qos-classifiers 16 is used (that is, maximum of (9, (2 * 4))).
If the same policy were to be used for a SAP in an Epipe service, then because all traffic is classified to a unicast traffic type and because only unicast meters are used, the following:
Using the equation, calculate the total classification entries used by this policy, as follows:
The number of meters used in this policy = 2.