Table of Contents
Advertisement
Basic Configurations
exit
exit
In the example above, assuming the policy is attached to a SAP in a VPLS service, compute the
number of classification entries per FC as follows:
FCnc = 0 + 0 + 0 + 0 = 0
FCh1 = 0 + 0 + 0 + 0 = 0
FCef = 0 + 0 + 0 + 0 = 0
FCh2 = 1 + 0 + 0 + 0 = 1
Since this FC uses unicast meter for all traffic types, we need an entry to classify all traffic types to
this FC explicitly.
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 equation, calculate the total classification entries used by this policy, as follows:
TC = (0 * 0)nc + (0 * 0)h1 + (0 * 0)ef + (1 * 1)h2 + (1 * 1)l1 + (1 * 1)af + (0 * 0)l2 + (1 *1)be = 4
(since three explicit match criteria entries are used to map traffic to each of FC H2, FC L1, and FC
AF along with a default classification entry for FC BE).
The total number of meters used = 2 (since FCs use meter #1 and meter #3).
Hence, in this example, num-qos-classifiers 4 is used (maximum of (4, (2 * 2))). Hence, use of
unicast meter for all traffic-types allows for use QoS resources efficiently.
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:
Page 254
meter 1
exit
fc l1
create
meter 3
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
7210 SAS D, E, K OS Quality of Service Guide
Advertisement
Table of Contents
