Table of Contents
Advertisement
Basic Configurations
Since this FC uses unicast meter for unicast, multicast, unknown-unicast traffic and broadcast
meter for broadcast traffic, hence two entries are needed.
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 above equation, to get the total classification entries used = 8 (since 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 = 2 (since FCs use only meter #2 and meter #3).
Hence, in this example num-qos-classifiers 8 is used (that is,maximum of (8, (2*2))).
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, 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)
Example 3
sap-ingress 10 create
description"example-policy-2"
num-qos-classifiers 16
Page 258
meter 1 create
rate cir 100 pir 100
exit
meter 2 create
rate cir 1 pir 20
exit
meter 3 create
rate cir 100 pir 100
exit
meter 4 create
rate cir 10 pir 100
exit
meter 5 create
rate cir 10 pir 10
exit
meter 11 multipoint create
7210 SAS D, E, K OS Quality of Service Guide
Advertisement
Table of Contents
