Basic Configurations
Page 262 7210 SAS D, E, K OS Quality of Service Guide
Since this FC uses unicast meter and broadcast meter, two entries are needed to identify these
traffic types explicitly, multicast and unknown-unicast traffic use the same resource as the unicast
traffic.
FCl1 = 1 + 0 + 1 + 0 = 2
Since this FC uses unicast meter and broadcast meter, two entries are needed to identify these
traffic types explicitly. multicast and unknown-unicast traffic use the same resource as the unicast
traffic.
FCaf = 1 + 1 + 1 + 0 = 3
Since this FC 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.
FCl2 = 0 + 0 + 0 + 0 = 0
FCbe = 1 + 0 + 0 + 0 = 1
Since no explicit meters are configured for FC be, it uses meter 1 for all traffic types and needs one
entry is needed to identify these traffic types.
Using the above equation, the total classification entries used = 12 and meters used = 5. The num-
qos-classifiers can be set to 12 (the minimum value).
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 results:
FCnc = 0 + 0 + 0 + 0 = 0
FCh1 = 1 + 0 + 0 + 0 = 1
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 = 5 and meters used = 3 (since all
FCs used only meter #1, meter #3 and meter #5). For epipe service a policy with num-qos-
resources set to 6 can be used.
Example 4
sap-ingress 10 create
description“example-policy-3”
num-qos-classifiers 36
meter 1 create
rate cir 100 pir 100
exit
To Next Page
Loading...
Need help?
General
