Example 1

Example


sap-ingress 10 create
     description ‟example-policy-1”
     num-qos-classifiers 8
     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
     scope template
     default-fc be
     fc be create
        meter 3
     exit
     fc  af create
         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
     exit
exit

In the preceding example, 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 + 1 + 0 = 2

Because FCh2 uses unicast meter, an entry is needed to identify unicast traffic type explicitly. Another entry is needed to classify broadcast, multicast and unknown-unicast traffic type to the same FC and use the default meter ‟11”.

FCl1 = 1 + 0 + 1 + 0 = 2 FCaf = 1 + 0 + 1 + 0 = 2 FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 0 + 1 + 0 = 2

Using the equation, calculate the total number of classification entries (TC) used by this policy, as follows:

TC = (0 * 0)nc + (0 * 0)h1 + (0 * 0)ef + (1 * 2)h2 + (1 * 2)l1 + (1 * 2)af + (0 * 0)l2 + (1 * 2)be = 8 (because 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 = 3 (because FCs use meter ‟1”, meter ‟3” and meter ‟11”).

In this example, num-qos-classifiers 8 is used (maximum of (8, (2 * 3))).

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 computation is made:

FCnc = 0 + 0 + 0 + 0 = 0 FCh1 = 0 + 0 + 0 + 0 = 0 FCef = 0 + 0 + 0 + 0 = 0 FCh2 = 1 + 0 + 0 + 0 = 1 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 above equation, total classification entries used = 4 and meters used = 2.

As can be seen here, using the same policy for Epipe SAP can lead to inefficient use of resources. Hence, it is recommended to create a different policy with the required number of resources (that is, with num-qos-classifiers 4)