Table of Contents
Advertisement
Since this FC uses unicast meter, an entry is needed to identify this 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, the total classification entries used by this policy is calculated as:
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 (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).
Meters used = 3 (since FCs use meter #1, meter #3 and meter #11).
Therefore, in this example,
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:
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, the total classification entries used = 4 and total meters used = 2.
Example 1a (Default multipoint meter "11" is not used):
sap-ingress 10 create
7210 SAS D, E, K OS Quality of Service Guide
num-qos-classifiers 16
description
"example-policy"
num-qos-classifiers 4
meter 1
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
Service Ingress QoS Policies
is used (i.e. maximum of (8, (2 * 3))).
Page 253
Advertisement
Table of Contents
