Example 2

Example


sap-ingress 10 create
     description ‟example-policy-1”
     num-qos-classifiers16
     meter 1 create
          rate cir 0 pir max
     exit
     meter 11 multipoint create
          rate cir 0 pir max
     exit
     meter 3 create
          rate cir100 pir 100
     exit
     meter 2 create
          rate cir 1 pir 20
     exit
     scope template
     default-fc be
     fc be create
        meter 3
        broadcast-meter 2
     exit
     fc af create
        meter 3
        broadcast-meter 2
     exit
     fc l1 create
        meter 3
        broadcast-meter 2
     exit
     fc h2 create
        meter 3
        broadcast-meter 2
     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, classification entries used per FC as:

FCnc = 0 + 0 + 0 + 0 = 0 FCh1 = 0 + 0 + 0 + 0 = 0 FCef = 0 + 0 + 0 + 0 = 0 FCh2 = 1 + 1 + 1 + 0 = 3

Because FCh2 uses unicast meter and broadcast meter, two entries are needed to identify these traffic types explicitly. Another entry is needed to classify multicast and unknown-unicast traffic type to FCh2 and use the default meter ‟11”.

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

Using the above equation for TC calculation, to get the total classification entries used = 12 (because three explicit match criteria entries map to each of FC H2, L1, and AF along with a default classification rule for BE).

The number of meters used = 3 (because FCs use only meter ‟2”, meter ‟3” and meter ‟11”).

Hence, in this example num-qos-classifiers 16 is used (that is, maximum of (12, (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:

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, to get total classification entries used = 4 and Meters used = 1.

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)