sap-ingress 10 create
description‟example-policy-3”
num-qos-classifiers 36
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 6 create
rate cir 11 pir 100
exit
meter 8 create
rate cir 20 pir 100
exit
meter 11 multipoint create
rate cir 1 pir 20
exit
fc "af" create
meter 3
broadcast-meter 2
multicast-meter 4
exit
fc "ef" create
meter 6
broadcast-meter 2
multicast-meter 8
exit
fc "h1" create
meter 5
broadcast-meter 4
multicast-meter 4
unknown-meter 4
exit
fc "h2" create
meter 3
broadcast-meter 2
exit
fc "l1" create
meter 3
broadcast-meter 2
exit
fc "nc" create
meter 6
broadcast-meter 2
multicast-meter 8
exit
mac-criteria
entry 1 create
match
dot1p 4 7
exit
action fc "af"
exit
entry 2 create
match
dot1p 5 7
exit
action fc "l1"
exit
entry 3 create
match
dot1p 6 7
exit
action fc "h2"
exit
entry 4 create
match
dot1p 3 7
exit
action fc "h1"
exit
entry 5 create
match
dot1p 2 7
exit
action fc "ef"
exit
entry 6 create
match
dot1p 7 7
exit
action fc "nc"
exit
exit
default-fc "be"
In example 4, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.
Because 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.
Because this FC uses unicast, broadcast, multicast and unknown-unicast meter, four entries are required to identify these traffic types explicitly.
Because 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.
Because 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.
Because 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.
Using the preceding equation, the total classification entries used = 21 and the total meters used = 8.
If the same policy were used for a SAP in an Epipe service, all traffic is classified to a unicast traffic type and only unicast meters are used, use the following computation.
Using the preceding equation, the total classification entries used = 7 and the total meters used = 4.
Using the same policy for Epipe SAP can lead to inefficient use of resources. Nokia recommends creating a different policy with the required number of resources (that is, num-qos-classifiers 16)