Example 3

sap-ingress 10 create
description‟example-policy-2”
num-qos-classifiers 16
             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
                rate cir 1 pir 20
            exit
            fc "af" create
                meter 3
                broadcast-meter 2     
                multicast-meter 4
            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
            mac-criteria
                entry 1 create
                    match 
                        dot1p 7 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
            exit
            default-fc "be"

In example 3, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 1 + 1 + 1 + 1 = 4

Because this FC uses unicast, broadcast, multicast, and unknown-unicast meter, four entries are required to identify these traffic types explicitly.

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 1 + 1 + 0 = 3

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.

FCl1 = 1 + 1 + 1 + 0 = 3

Because this FC uses only unicast meter, an entry is required to identify this traffic type explicitly. Another entry is required to classify broadcast, multicast, and unknown-unicast traffic type to the same FC and use the default meter 11.

FCaf = 1 + 1 + 1 + 0 = 3

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.

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 1 + 0 = 2

Using the preceding equation, the total classification entries used = 15 and the total meters used = 6.

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.

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 preceding equation, the total classification entries used = 5 and the total meters used = 3 (because all FCs used only meter 1, meter 3, and meter 5).