Table of Contents
Advertisement
Since this FC uses unicast meter and broadcast meter, two entries are required to identify these
traffic types explicitly. Another entry is required to classify multicast and unknown-unicast traffic
type to the same FC and use the default meter #11.
FCl1 = 1 + 1 + 1 + 0 = 3
FCaf = 1 + 1 + 1 + 0 = 3
Since this FC uses unicast, broadcast and multicast meter, three entries are required 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.
FCl2 = 0 + 0 + 0 + 0 = 0
FCbe = 1 + 0 + 1 + 0 = 2
Using the above equation, the total classification entries used = 21 and the total meters used = 8
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 are used:
FCnc = 1 + 0 + 0 + 0 = 1
FCh1 = 1 + 0 + 0 + 0 = 1
FCef = 1 + 0 + 0 + 0 = 1
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 = 7 and the total meters used = 4.
As illustrated in this example, 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 (i.e. with
Example 4a (Default multipoint meter "11" is not used):
sap-ingress 10 create
description
num-qos-classifiers
meter 1 create
exit
meter 3 create
exit
meter 2 create
exit
meter 4 create
exit
meter 5 create
exit
7210 SAS D, E, K OS Quality of Service Guide
num-qos-classifiers
"example-policy-3"
20
rate cir 100 pir 100
rate cir
100 pir 100
rate cir 1 pir 20
rate cir 10 pir 100
rate cir 10 pir 10
Service Ingress QoS Policies
= 16)
Page 265
Advertisement
Table of Contents
