This section describes the rules for meter selection by different traffic types under various configurations for VPLS services:
In the default policy, only meter ‟1” is defined. All FC and all traffic types use meter ‟1” by default. Meter ‟11” is not created by default and is not available for use.
The following is a sample default policy configuration output.
*7210-SAS>config>qos# sap-ingress 1 create // Default policy
*7210-SAS>config>qos>sap-ingress$ info
----------------------------------------------
num-qos-classifiers 2
meter 1 create
exit
----------------------------------------------
*7210-SAS>config>qos>sap-ingress$
The following describes the use of meters in a VPLS service, when meter ‟11” is not configured in the policy:
If an FC is created without explicit meters, the default meter ‟1” is used for unicast traffic and for multipoint traffic types (such as broadcast, multicast, and unknown-unicast traffic).
If an FC is created with an explicit unicast meter, that meter is used for unicast traffic and for multipoint traffic types (such as broadcast, multicast, and unknown-unicast traffic).
If an FC is created with an explicit unicast meter and explicit broadcast meter, use these meters for unicast and broadcast traffic respectively, and use the unicast meter for all other traffic types.
If an FC is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and multicast meter for all other traffic types.
If an FC is created with an explicit unicast meter, an explicit broadcast meter, and an explicit multicast meter, use these meters for unicast, broadcast, and multicast traffic types respectively. The unknown unicast traffic types use the explicitly defined multicast meter.
If an FC is created with an explicit unicast meter, explicit broadcast meter, explicit unknown-unicast meter, and explicit multicast meter, use these meters for unicast, broadcast, unknown-unicast, and multicast traffic types respectively.
The following describes the use of meters in a VPLS service, when meter ‟11” is defined in the policy:
If an FC is created without explicit meters, use the default meter ‟1” for unicast traffic and default meter ‟11” for all other traffic types (such as broadcast, multicast, and unknown-unicast).
If an FC is created with an explicit unicast meter, use that meter for unicast traffic, and use default meter ‟11” for all other traffic types.
If an FC is created with an explicit unicast meter and explicit broadcast meter, use these meters for unicast and broadcast traffic respectively, and use meter ‟11” for all other traffic types.
If an FC is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and multicast meter for all other kinds of traffic.
If an FC is created with an explicit unicast meter, explicit broadcast meter, and explicit multicast meter, use these meters for unicast, broadcast, and multicast traffic types respectively. Unknown unicast traffic types use the explicitly defined multicast meter.
If an FC is created with an explicit unicast meter, explicit broadcast meter, explicit unknown-unicast meter, and explicit multicast meter, use these meters for unicast, broadcast, unknown-unicast, and multicast traffic types respectively.
The following are rules for meter selection for Epipe and IES services:
These rules apply to IES services when PIM, multicast is not enabled in the service.
IPv4 multicast with PIM is not supported on all 7210 SAS platforms. Check the 7210 SAS release notes to know the availability of this feature on all platforms.
A multipoint meter cannot be used. A multipoint meter configured in a policy is not used when the policy is applied to a SAP in an Epipe service.
All FCs associated with a meter always use the unicast meter.