Table of Contents
Advertisement
Basic Configurations
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
meter 1 create
exit
meter11 multipoint create
exit
meter 3 create
exit
meter 2 create
exit
meter 4 create
exit
meter 5 create
exit
scope template
default-fc be
fc
exit
fc
exit
fc
Page 230
7210 SAS-X and 7210 SAS-R6 OS Quality of Service Guide
rate cir 100 pir 100
rate cir 1 pir 20
rate cir 100 pir 100
rate cir 1 pir 20
rate cir 10 pir 100
rate cir 10 pir 10
af create
meter 3
broadcast-meter 2
multicast-meter
4
l1 create
meter 3
broadcast-meter 2
h2 create
meter 3
Advertisement
Table of Contents
