Example 7

Example


sap-ingress 10 create
     num-qos-classifiers 8
     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 
     match entry 1
          dot1p 7 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 are:

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 = 1 + 0 + 1 + 0 = 2

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

FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 1 + 1 + 0 = 3

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 above equation, the total classification entries used = 5 and meters used = 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:

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 = 1 + 0 + 0 + 0 = 1 FCl2 = 0 + 0 + 0 + 0 = 0 FCbe = 1 + 0 + 0 + 0 = 1

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