Example 11

Example

sap-ingress 10 create
     description ‟example-policy-1”
     num-qos-classifiers   4
     meter 1 create
          rate cir 0 pir max
     exit
     meter 11 multipoint create
          rate cir 0 pir max
     exit
     scope template
     default-fc be
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 = 0 + 0 + 0 + 0 = 0 FCl1 = 0 + 0 + 0 + 0 = 0 FCaf = 0 + 0 + 0 + 0 = 0 FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 0 + 1 + 0 = 2

Using the equation, calculate the total classification entries used by this policy, as follows:

TC = (0 * 0)nc + (0 * 0)h1 + (0 * 0)ef + (0 * 0)h2 + (0 * 0)l1 + (0 * 0)af + (1 * 2)l2 + (0* 0)be = 2

The number of meters used = 2 (because default FC uses meter ‟1” and meter ‟11”).

Hence, in this example num-qos-classifiers 4 is used (that is, maximum of (2, (2 * 2))).

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:

FCnc = 0 + 0 + 0 + 0 = 0 FCh1 = 0 + 0 + 0 + 0 = 0 FCef = 0 + 0 + 0 + 0 = 0 FCh2 = 0 + 0 + 0 + 0 = 0 FCl1 = 0 + 0 + 0 + 0 = 0 FCaf = 0 + 0 + 0 + 0 = 0 FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 0 + 0 + 0 = 1

Using the above equation, total classification entries used = 1 and meters used = 1.

As can be seen here, for Epipe SAP with the same amount of resources allocated one can have more FCs if need be.