Example uses of the multipoint meter

Example: 1

*7210-SAS>config>qos# sap-ingress 12 create 
*7210-SAS>config>qos>sap-ingress$ info 
----------------------------------------------
            num-qos-classifiers 4
            meter 1 create
            exit
----------------------------------------------
*7210-SAS>config>qos>sap-ingress$

In example 1, all FCs in the SAP ingress policy use the default meter 1 (for all traffic types). If the configure qos sap-ingress id meter 11 multipoint create command is executed, it attaches the default meter ‟11” with all the FCs defined in the SAP ingress policy.

After this configuration, all the FCs in this policy use two meters: default meter "1" to meter unicast traffic for all the FCs, and meter ‟11” to meter BUM traffic for all the FCs. In this example, because only the default FC ‟be” is in use, the multipoint meter is used to meter BUM traffic associated with default FC ‟be”.

The following example shows the policy after the configuration is changed.

*7210-SAS>config>qos# sap-ingress 12
*7210-SAS>config>qos>sap-ingress$ info 
----------------------------------------------
             num-qos-classifiers 4
             meter 1 create
             exit
meter 11 multipoint create
----------------------------------------------
*7210-SAS>config>qos>sap-ingress$

Delete the multipoint meter ‟11” to remove all the FCs associated with the multicast-meter (assuming all the FCs are using the default multicast meter and do not have any other multicast meter explicitly configured). Execute the configure qos sap-ingress id no meter 11 command to dissociate meter ‟11” from the FCs, and the FCs use only meter ‟1” (if no other meter configured explicitly).

Example: 2

*7210-SAS>config>qos# sap-ingress 12
*7210-SAS>config>qos>sap-ingress$ info 
----------------------------------------------
configure> qos> sap-ingress 10 create
meter 1 create
exit
meter 3 create
exit
default-fc be
fc be 
meter 3
multicast-meter 3
exit
fc af
meter 3
exit
exit
----------------------------------------------

Starting with the policy in example 2, if the user executes the configure qos sap-ingress <id> meter 11 multipoint create command, the FC ‟be” continues to use meter ‟3” and the FC "af" uses meter "11" for BUM traffic. In this example, if the user executes the configure qos sap-ingress id fc be no multicast-meter command, the default meter ‟11” is used for FC "be".

Example: 3

----------------------------------------------
configure> qos> sap-ingress 10 create
meter 1 create
exit
meter 3 create
exit

default-fc be

fc be 
meter 3
unknown-meter 3
exit
exit
----------------------------------------------

On execution of the configure qos sap-ingress id meter 11 multipoint create command, the FC "be" unknown-unicast traffic type continues to use meter 3 and broadcast and multicast traffic types use meter ‟11”.

In example 3, if a broadcast-meter was initially configured in the SAP-ingress policy and then followed by execution of the configure qos sap-ingress id meter 11 multipoint create command, the FC ‟be” changes to use meter ‟11” for multicast traffi, and broadcast traffic continues to use meter ‟3” for unknown-unicast traffic and meter ‟3” for unicast traffic.

In example 3, if the user executes configure qos sap-ingress id fc be no unknown-meter command, meter "3" is used for all traffic types classified to FC ‟be”. But, if the default meter "11" is defined in the policy, FC ‟be” uses meter ‟11” for BUM traffic.